About this policy
This policy applies to telo.health, the telo iPhone app and the telo MCP connector. telo lets you query your health history through assistants you authorize.
Information we receive
We receive your email address for authentication and, if you join the waitlist, your email and preferred language. Connecting an iPhone creates account and device identifiers, a device name and access credentials.
With your Apple Health permission, your iPhone sends daily metric summaries and sleep and workout records. Available categories and dates depend on your permissions, Health records and completed syncs. This information is stored on telo servers, not only on your iPhone.
We also process sync information, connector authorizations and query logs: assistant, tool, time, query scope and result count. Technical request information, such as IP addresses, may be used for operations, security and abuse prevention.
How we use information
We use this information to authenticate your account, sync and display your history, answer queries from authorized connectors, show access activity and protect the service. Waitlist information is used to organize access and invitations.
We do not sell your information. We do not use Apple Health data for advertising, marketing or data mining, and we do not share it with data brokers.
AI assistants and sharing
When you authorize an assistant, such as ChatGPT or Claude, it can request synced records through telo tools. Responses can contain sensitive health information. Connector tools are read-only and do not change your Apple Health records.
The assistant provider receives query results and processes them under its own policies and your account settings, including its rules for storing and using conversations. Review those rules before authorizing a connector.
We use Cloudflare to host the service and store data, and Resend to send sign-in codes by email. Sending a code does not require your health history. These providers may process information in other countries.
Usage analytics
We use PostHog, with processing in the United States, to understand product usage. On iPhone, we send only app-open and login-completed events, SDK-generated installation and session identifiers, and technical information such as app version, operating system and device model. These identifiers can connect events from the same installation; we do not send your email or telo account identifier to PostHog.
On the website, we record navigation on allowed pages, without URL parameters or dashboard content. Navigation identifiers are kept only in browser memory. We do not record screens or sessions in the app or on the website, and do not send health records, login codes, conversations or typed text for analytics. Analytics is configured without IP-based geolocation and is not used for advertising.
Storage and retention
Synced health records remain stored to support historical queries. There is currently no automatic expiration configured for these records, accounts or waitlist registrations.
Connector query logs are cleaned daily to remove entries older than 90 days. This period applies to access history, not health records.
Permissions and deletion
You can stop new reads by changing telo permissions in Apple Health or iPhone settings, or pause sending in the telo app. To stop an assistant’s queries, disconnect it in the telo app or remove the connection in that assistant’s settings.
You can delete your telo account in the app, under Account, after confirming a code sent to your email. This permanently deletes your synced health records, devices, sync history, query logs and connector records, and revokes every assistant authorization. You can also request deletion at contact@telo.health.
Deleting your telo account does not delete copies an assistant already received. For those, use that provider’s controls and support.
Cookies and preferences
The dashboard uses a session cookie to keep you signed in for up to one year. Your browser may also store language and appearance preferences. Signing out ends that browser’s session.
Security
telo uses HTTPS connections, authentication and account-specific access checks. Only authorize assistants you trust and keep sign-in codes and credentials private.
Changes to this policy
Updates will be published on this page with the revision date. Review this policy when connecting a new assistant or using new features.
Contact
For privacy questions or deletion requests, write to contact@telo.health.