This is a placeholder. The final text is being written and reviewed. Replace everything
below this line, set draft: false in the front matter, and update updatedAt.
Until then this page carries noindex and says out loud that it is not final — a policy that
looks finished but is not is worse than an obvious placeholder, because it ships, passes a
glance, and fails in front of a reviewer.
What the final text has to cover
The App Store requires this document under Review Guidelines 3.1.2 and 5.1.1(i), and
LegalLinks.privacyPolicy in the iOS app stays nil until this URL is live. Whoever writes
it needs to describe, at minimum:
- Who the data controller is — legal name, status, country, and a contact address.
- What is collected: the Apple account identifier from Sign in with Apple, the training profile, generated workouts, session ratings, and body weight.
- What Apple Health is used for: finished workouts written as boxing sessions, body mass read and written — only after the user switches the sync on, and revocable from the Health app at any time.
- Who processes it: Supabase (database and authentication), Anthropic (workout generation, called from Edge Functions — never from the device), RevenueCat (subscription state), Apple (sign-in and payment). Where each one stores data.
- How long it is kept, and what account deletion actually deletes.
- The user's rights and how to exercise them.
- That there is no advertising or analytics SDK in the app, and that nothing is sold or shared for marketing. This is true today and is worth stating plainly.