AiDataCoach
HomeHow it worksPlans
HelpSign in

Privacy policy

What is stored, for how long, and how it is removed.

This policy explains what personal data we collect, why, how long we keep it, who we share it with, and how you can have it removed. It covers the website and the iOS app.

Who we are. The controller of your personal data is the operator of the AiDataCoach service — 'we', 'us' and 'our' in this policy — the service and website at aidatacoach.app. We have not confirmed, and so do not state here, whether AiDataCoach is a registered company or a trading name; nor have we named a registered address or a registration number. We have not yet appointed a data protection officer or representative either. Those details, and a data protection contact, belong in this paragraph, and we will add them when we have them; we would rather leave them unstated than assert a legal form we cannot verify. You can reach us now as described under 'Contact us' at the end.

What we collect: account details. When you sign in through Supabase, we receive and store the email address your sign-in provider gives us, together with the time zone you choose. Neither Apple nor Google will tell us the password for your account with them. Three things about that address, your name and your picture are worth stating plainly. If you sign in with Apple, the address may be a private relay address Apple creates for you, ending in privaterelay.appleid.com, and if it is, we cannot see your real address — that is Apple's Hide My Email, and it is not a fault. Apple sends your name only on the very first sign-in, so from Apple we hold a name only when that first sign-in gave us one, and Apple never supplies a profile picture. Google sends the address on the Google Account you sign in with, and the name and profile picture held there, and we store them.

What we collect: Apple Health data. The iOS app sends the Apple Health data you allow it to read: activity such as steps, distance and rings; workouts, including workouts you log by hand in the app; sleep; body measurements; mindfulness; mobility; nutrition; and vitals. We store it in our database as samples and as daily summaries. You control what the app may read in Apple Health.

What we collect: goals, profile and coach settings. The goals you set and the history of changes to them, the fitness profile you type (for example age, height, weight and body fat), and the settings you choose for the AI coach. If you connect your own AI provider, we also store the connection details and the API key you give us, encrypted (see 'Security').

What we collect: AI coach conversations. The questions you ask the coach, the answers it gives, and the health values it read to answer. Because the coach answers from your health data, a stored conversation can contain health values quoted in the text.

What we collect: billing details. Stripe is our payment provider. We store identifiers and state, not your card: the Stripe customer id, the subscription id, the subscription status, the price id, the period end, and a record of the Stripe events we have processed. We never receive your full card number.

What we collect: cookies. We use the cookies needed to keep you signed in, and one small cookie that remembers when you dismiss an upgrade note. We do not use advertising cookies, and we do not run third-party advertising or analytics trackers.

Why we use it. To provide the service and keep your account working. To receive, store and show the Apple Health data you sync. To run the AI coach you ask for. To take payment, renew and manage your subscription, and to handle refunds. To answer support requests and fix problems. To keep the service secure, prevent abuse, and meet our legal duties, including tax and accounting.

Our lawful bases (UK and EU). We process your data to perform our contract with you (providing the service, storing and showing your data, running the coach, and taking payment); for our legitimate interests (security, abuse prevention and keeping the service working, where those do not override your rights); with your consent, where access to Apple Health or an optional connection depends on it, which you may withdraw at any time; and to meet legal obligations, such as tax and accounting.

How long we keep it: Apple Health data. Basic keeps the most recent 60 days on our servers. Pro keeps up to 730 days (about two years). The window moves with the day: when a row falls outside it, it is no longer shown, and a new row outside it is not stored. 'Up to' is a ceiling, not a promise of two years of history — Pro does not create data that was never synced.

How long we keep it: older data from before the limit. Some accounts hold health rows older than the window, stored before this limit existed. We still hold those rows, and they are hidden while the account is on Basic. The window does not delete them, and moving to Pro makes them visible again. This is the one case where an account holds more than its window.

The erasure watermark. An account can carry an erasure watermark: the date and time at which health history was erased for it. Any health row dated at or before the watermark is refused on upload and hidden on read, so a later sync cannot bring the erased period back.

How long we keep it: other data. Your stored coach conversations — their messages, their list entries and their titles — are kept until you delete them or close your account. Your goals, profile, fitness profile and coach settings are kept until you close your account. We keep billing state while your account is open, and Stripe keeps invoices and payment records for as long as tax and accounting law requires. Records of the Stripe events we have processed are deleted after 90 days.

What closing your account removes. Closing your account is the one way to have the health data we hold for you removed. It removes: the Apple Health samples we hold across activity, workouts, sleep, body, mindfulness, mobility and vitals; the workouts you logged by hand, which HealthKit never recorded and no device copy can bring back; the older workout-calendar copy we kept for this account; and the copies derived from your health data — your stored coach conversations, including their messages, their list entries and their titles (a title is taken from your first question and can contain a health value), your insights, and the sync and import counts. It also removes your goals, your profile and fitness profile, your coach settings (including any AI provider connection you have set up), and your billing state. It cannot be undone.

What closing your account does not remove. Closing the account removes the account and the data tied to it. A record of the Stripe events we have processed can remain for up to 90 days, until the daily job prunes it; it holds no health data. Stripe keeps invoices and tax records for as long as tax and accounting law requires. The unused part of the period you have paid for is not refunded.

Closing your account. Closing the account is how the account itself is removed. Our server cancels your subscription at Stripe immediately — not at the end of the period — and then deletes the account, which removes the data described above, including the Apple Health history we hold for you and the stored coach conversations that were answered from it. If the cancellation at Stripe fails, we do not delete the account, so that a card cannot be left being charged with nothing to identify it. On the website, in Settings under Danger Zone, the control 'Delete my account' opens a confirmation that says what it removes and asks you to type delete to confirm; the iOS app has the same control on its Account tab, under Danger Zone. It cannot be undone. To stop paying without removing your data, cancel the subscription instead — 'Manage billing' in Settings, or the billing support page at /support/billing.

Who we share it with. We do not sell your personal data, and we do not share it for advertising. We use these providers, who process it for us:

Supabase hosts our database and handles authentication. Your account data and the health data you sync are stored in the database it runs for us.

Stripe takes payments, manages subscriptions and the Customer Portal, and calculates tax at Checkout. Stripe receives your payment details and billing address.

Apple and Google provide the sign-in you use, whichever you choose. From Apple we receive the email address Apple gives us, which may be the private relay address described under 'What we collect: account details', and your name when Apple sends it on the first sign-in; Apple supplies no profile picture. From Google we receive the email address on that Google Account, and the name and profile picture Google supplies with the sign-in.

AI providers, only when you use the AI coach. Your messages, and the health values the coach reads to answer them, are sent to the provider your coach is connected to — for example OpenRouter or Anthropic, or an endpoint you add yourself — using the key stored for that connection. That provider processes the request to produce the answer, under its own terms and privacy policy.

We may also disclose data if the law requires it, or to protect someone's safety.

Where your data is held. Our providers — Supabase, Stripe, Apple, Google and any AI provider you connect — run infrastructure in more than one country, so your data may be processed outside the country where you live. We have not yet listed the countries or regions, or the safeguards used for transfers out of the UK or the EEA, such as the UK Addendum or the EU Standard Contractual Clauses. Those details belong in this paragraph and are still to be added. Until they are, ask us through the billing support page at /support/billing or the in-app Help page and we will tell you what we can.

Your rights. Depending on where you live, you may have the right to be told what we hold and to get a copy; to have it corrected; to have it deleted; to restrict or object to some processing; to receive it in a portable form; and to withdraw consent. If you are in the UK or the EU, you also have the right to complain to your national data protection authority. If you are in California, you have rights to know, delete, correct, and to opt out of the sale or sharing of personal data; we do not sell your data and we do not share it for cross-context behavioural advertising. To exercise a right, contact us as described under 'Contact us' at the end. We do not currently offer a self-service export, so ask us and we will arrange one. We will not treat you differently for exercising a right.

Children. The service is not for children. We do not knowingly collect personal data from a child, we do not ask for a date of birth, and we do not verify age. We have not set a minimum age in this policy, because we do not offer the service to children at all. If you believe a child has given us data, contact us and we will delete it.

Security. Data is encrypted in transit, and access to the database is restricted by row-level security so that one account cannot read another's. An API key you connect for the AI coach is encrypted at rest with AES-256 through Postgres pgcrypto, and a browser session cannot read the stored key. No system is perfectly secure, and we cannot promise that a breach will never happen.

Changes to this policy. We may update this policy. If a change is material, we will tell you before it takes effect, for example by email or by a notice in the app. This version carries no date, and we will date each version from the day it is published; that date will appear here.

Contact us. For a privacy question, or to exercise a right, use the billing support page at /support/billing, linked from Settings, or the in-app Help page. No dedicated support or privacy email address is published yet, and there is no postal address for privacy notices; the support page and the Help page are how to reach us, and a person reads them.

Terms of service · Privacy policy