1. Overview
HealthAPI is provided by Overarch.ai LLC ("we", "us"). It lets you sync your own health data, from Apple Health on iPhone or Health Connect on Android, and access it through a REST API. This policy explains what we collect, how we use it, and the controls you have. You stay in control of your data: you can export or delete it at any time.
2. Data we collect
Health & fitness data you choose to sync. Only the metric types you enable in the app (spanning activity & energy, cardiovascular and other vitals (including sensitive readings such as blood pressure, blood glucose, and blood oxygen, and, if you sync them, blood alcohol, insulin, and heart-rhythm data), mobility, hearing (audio exposure), nutrition, body composition, sleep, and workouts) are read from Apple Health (HealthKit) on iPhone or from Health Connect on Android, and stored on your account. Blood alcohol, insulin, heart-rhythm and hearing data are available on iPhone only. For each sample we also store its value, unit, timestamps, and the source app and device it came from. We never read health data you haven't granted. (These are ordinary health and fitness metrics; we do not access Apple Health clinical records or Health Connect medical records.)
Health Connect (Android). The Android app reads only the Health Connect data types you allow on Health Connect's own permission screen, and you can change them there at any time. If you also allow it, the app reads data older than the 30 days before you first gave it access, to import your history, and reads in the background, to keep your sync up to date while the app is closed. The use of information received from Health Connect adheres to Google's Health Connect Permissions policy, including the Limited Use requirements: it is used only to provide the service described here, never for advertising, never sold, and never shared except as section 4 sets out.
Account & identity. A device identifier and your device's name (which on iOS often contains your name; on Android it is the phone's make and model), the platform, and your time zone, used to create and operate your account. If you use Sign in with Apple, the identifier Apple provides, the email address Apple shares (which may be an Apple private-relay address), and your name. If you use Sign in with Google on Android, the identifier Google provides, your email address, and your name. You may also set a display name, which is stored on our servers. Your account is secured by an API key we issue to you. On Android, so that a reinstall can restore your account, the app saves your API key and account identifier with Google Block Store, in Google's end-to-end encrypted backup when your phone supports it and otherwise only on the phone; this never includes health data.
AI apps you connect. If you connect an AI app such as Claude or ChatGPT (section 3), we keep a record of the connection: the app's name and the site it returns to, when you connected it, when it last read your data, and the browser, device and IP address that started the sign-in. Its access tokens are stored only as one-way hashes.
Subscriptions. If you subscribe on iPhone, Apple sends us a signed App Store transaction so we can confirm your plan tier and status. If you subscribe on Android, the app sends us the Google Play purchase token, which we check with Google to confirm your plan tier and status. Payments are handled entirely by Apple or Google: we never receive or store your card or payment details.
Diagnostic telemetry. To help us debug sync and other issues, the app may send diagnostic events tied to your account: an event type, an optional free-text message, and a metadata object (for example, sync durations and outcomes, the number of samples or workouts uploaded, and error messages when something fails). We strip emails, tokens, and credential hashes from these events before storing them.
App usage. To see which parts of the app help people and where they get stuck, the app (on iPhone from version 1.0.7, and on Android) also records how it is used, tied to your account: when it is opened and for how long, which screens you view, the steps of the first-run setup, when a plans screen is shown, and taps on a few buttons (for example copying your API key, connecting an AI app, or answering a permission prompt), with the app version. It also sends the crash and performance reports that iOS gives the app (MetricKit) or, on Android, reports of crashes, freezes and performance that the app collects itself; these go only to our server. These events never contain your health values. You can turn them off in the app, in Settings, Data & Privacy, Share app usage.
Operational data. Basic request metadata (method, endpoint, status, timing, and IP address) is written to our short-lived operational logs to run, secure, and debug the API, and a per-day counter is used to enforce rate limits.
Website analytics. This website counts visits with Umami, an open-source analytics tool we run on our own server, so this visit data is not sent to anyone else. For each page view it records the page, the site that linked to it, campaign tags in the link (such as utm_source), your browser, operating system, device type, screen size, language and approximate location (country, region and city), plus a few clicks on the site (for example on the App Store button, a link to Claude or ChatGPT, or a Copy button). It sets no cookies and does not store your IP address: the address is used only to look up the approximate location and, together with your browser details and a value that changes every month, to tell one visit from another. If your browser sends Do Not Track or Global Privacy Control, nothing is recorded. Umami runs only on these web pages, never in the iOS or Android app, and never sees your health data or your API key. Visit records are deleted after 25 months.
This website (but not the iOS or Android app) also uses Statcounter, a third-party analytics service, to count visits. It records standard visit information (the pages viewed, referring site, browser and device, screen size, approximate location derived from your IP address, and the IP address itself) and stores a cookie in your browser so repeat visits can be told apart. It runs only on these web pages and never has access to your health data or your API key. See Statcounter's legal and privacy terms for how they handle it.
This website (but not the iOS or Android app) also uses Google Analytics, a service from Google, to understand how visitors find and use it. It records the pages viewed, the referring site, browser and device, screen size and approximate location, and stores cookies in your browser so repeat visits can be told apart. Google Analytics does not store IP addresses. We have turned off Google signals and ad personalization, so this visit data is not used for advertising. If your browser sends Do Not Track or Global Privacy Control, Google Analytics does not load. It runs only on these web pages and never has access to your health data or your API key. See how Google uses information from sites that use its services.
Website chat. This website (but not the iOS or Android app) offers an optional live chat run by Tidio, a third-party chat service. Its script loads only when you tap “Chat with us”, so nothing is sent to Tidio unless you open the chat. Once you do, Tidio receives the messages you type, any name or email you give, and standard visit information (browser, device, the page you're on, and approximate location derived from your IP address), and stores data in your browser so the conversation can continue. The chat never has access to the health data you sync or your API key. Please don't type health details into the chat; for questions about your data or account, use the contact form or email us. See Tidio's privacy policy for how they handle it.
How you found the app. If you installed the iOS app after tapping an Apple Search Ads advert, Apple tells us which campaign, ad group and search term brought you here, along with the country of the App Store you installed from. We use it to see which adverts are worth running. It uses no advertising identifier, it does not follow you across other apps or websites, and it is never used to target adverts at you. Apple provides this without the App Tracking Transparency prompt, and we deliberately do not request the one part of it that would require that prompt: the time you tapped the advert. Your health data plays no part in it.
If you installed the Android app from Google Play, Google Play tells us the campaign tags the install link carried (such as utm_source, utm_medium and utm_campaign) and when the install began. We use it the same way and for the same purpose. It uses no advertising identifier, it does not follow you across other apps or websites, it is never used to target adverts at you, and your health data plays no part in it.
3. How we use it
We use your data only to provide and operate the service: to sync and store your health data, serve it back to you over the API, enforce plan limits, secure the service, and respond to your support requests.
We do not sell your data, show you ads, or use your health data to train machine-learning models. The app itself never sends your health data to any AI provider.
Connecting an AI app
You can connect an AI app, such as Claude or ChatGPT, to your HealthAPI account. You start it in the AI app and approve it in the HealthAPI app on your phone, which shows you which app is asking and where the request came from before you approve. Nothing is connected until you do.
Once connected, the AI app can read the health data you've synced (it can't change or delete anything), and it reads only when you ask it something: it fetches what it needs to answer, and what it receives is then handled under that AI provider's own terms and privacy policy, which we encourage you to review. Each request counts toward your plan's daily limit.
You can disconnect an AI app at any time in the app (Settings, Connected apps); its access ends immediately. Regenerating your API key or deleting your account disconnects every AI app.
You can also give your personal API key to a tool or script you use (for example, an automation or your own code). That tool reads your data directly from our API at your request and under its own terms. Regenerate your key in the app to revoke it.
4. How it's shared
Your health data comes from Apple HealthKit on your iPhone or Health Connect on your Android phone. It is stored on infrastructure we operate through a hosting provider acting on our behalf. Apart from Statcounter and Google Analytics, the third-party website counters, and Tidio, the optional website chat, all described above (none of them sees the health data you sync), we don't share your personal data with any other third party, except with the AI apps and tools you connect yourself (section 3), where required by law, or to protect the rights and safety of users and the service.
5. Security
All traffic to the API is encrypted in transit with TLS. Access to your data requires your secret API key or a connection you approved in the HealthAPI app. Your API key acts as your identity, so keep it private, and rotate it from the Console if it's ever exposed. Internal access is limited to what's needed to operate the service. No system is ever perfectly secure, but we take reasonable measures to protect your data and will continue to strengthen them.
6. Your controls & rights
Export. Download a complete copy of your account and health data at any time via GET /gdpr/export.
Delete. Deleting your account (in the app, from any browser at healthapi.app/delete-account, or via DELETE /account/delete) deactivates it immediately (your API key stops working) and schedules permanent deletion after a 30-day grace period, during which you can recover it by reopening the app. After the grace period a daily job permanently and irreversibly erases your health samples, workouts, subscription records, diagnostic telemetry, and your entire user record: all identity fields (device identifier and name, Apple or Google identifier, email, display name, and credential hashes) are deleted, not merely anonymized. For immediate, irreversible erasure, use DELETE /gdpr/account with the confirmation body. We keep a limited security audit log of sensitive actions for fraud and abuse prevention. Encrypted database backups that still hold erased data expire on their own within 30 days. Health data stored locally in Apple Health or Health Connect on your device is not affected.
Disconnect. End any connected AI app's access in the app (Settings, Connected apps).
Rotate. Regenerate your API key at any time to revoke prior access, including every connected AI app.
Depending on where you live, you may have additional rights to access, correct, or restrict processing of your data. Contact us and we'll help.
7. Data retention
We keep your health data, workouts, account information, and subscription records for as long as your account is active. Diagnostic telemetry and app usage events are automatically deleted after 90 days. Website visit records (Umami) are deleted after 25 months. Per-day rate-limit counters expire automatically within 24 hours, and operational request logs are short-lived and kept only for debugging and security. A connected AI app's record is kept while it's connected; its access tokens expire within an hour unless it renews them, and sign-in requests (with the browser and IP address that started them) are deleted after 30 days. When you delete your account, your data is erased as described above: immediately for GDPR erasure, or after the 30-day grace window for a standard deletion.
8. Children
HealthAPI isn't directed to children under 16, and we don't knowingly collect their data. If you believe a child has used the service, contact us and we'll remove the account.
9. Not medical advice
HealthAPI is not a medical device and does not provide medical advice, diagnosis, or treatment. Always consult a qualified professional for health decisions.
10. Changes
We'll update this policy as the service changes and revise the date above. Significant changes will be communicated in the app or by email where appropriate.
11. Contact
Questions about your privacy or this policy? Reach us through our contact form.