Privacy
What is collected, where it lives, who can see it, and how to remove it.
Last updated 17 November 2026
This describes the software as actually built, checked against the database schema rather than adapted from a template. It has not been reviewed by a lawyer, and it is not legal advice. If anything here matters to you, ask at [email protected] and you will get a straight answer.
What is collected
Only what the app needs to plan and record training.
- Account
- Your email address, and a password — unless you sign in with Google or Apple, in which case there is no password here at all. Nothing else is required.
- Your plan
- Age, sex, current and goal weight, units, the days you can train, and the goals derived from them.
- What you told the coach
- Injuries, equipment, training history, family situation and how you feel about where you are — in your own words, because the coach plans around them. This is the most sensitive text in the system.
- Training records
- Sessions with sets, reps and weights; cardio minutes; meals with calories and protein; weekly check-ins including your written reflections and any weigh-in. If you save a workout to repeat, the list of exercises you chose for that day.
- Progress photographs
- Only if you take them. Front, side and back, stored as images against your account.
- Leaderboard name
- Only if you join the weekly leaderboard. The name you pick for it, which is shown to the other people in it — so pick one you are happy for them to see. Your real name is never used, and leaving puts the name back into circulation.
- Challenge entries
- Only while a challenge is running and only if you are in the leaderboard. Which of your three weekly goals you met, one row each, so a prize draw can be checked afterwards rather than taken on trust. Numbers about goals you set yourself — nothing about what you lifted, ate or wrote. Kept for as long as your account exists, and deleted with it.
- Strava connection
- Only if you connect Strava. The keys that let us post on your behalf, your Strava athlete number, and a record of which workouts have been sent, or declined because there was nothing in them to post — so the same one is never sent twice, and one we have declined is not tried again. The keys are stored where nothing in the app can read them, not even your own sign-in. Nothing is ever read back from Strava. Deleted when you disconnect, and with your account.
- Feedback you send
- Only if you use “Send feedback”, or ask a connected app to send some. What you wrote, which of the three kinds it was, and — only if you fill them in — a name and an email address to reply to, which do not have to be the ones on your account. From the app, with it: the build you were running, the screen you were on and the kind of device, because that is the part of a bug report nobody can be expected to supply. Sent through a connected app instead, it records which app sent it and none of those three, because that app cannot see them either. This is the one thing you write that a person at Vytality does read, because you sent it to us on purpose. Deleted with your account.
- Push notifications
- Only if you turn them on. One record per device you allow them on: the address your browser or phone gives us to deliver to, and the key material that lets the message be encrypted so only that device can read it. We also keep which of the weekly messages has already been sent to you, so the same one is never sent twice. The address is held where nothing in the app can read it, not even your own sign-in, and no message we send contains anything you wrote. Deleted when you turn notifications off, and with your account.
- How the app is used
- Which features you use and when — opened the app, opened a notification we sent you, started a workout, logged a set, swapped or added an exercise — with the rough size of the screen. Where a movement is named it is the one you picked from our exercise library, never the words you typed into the search box, which are not recorded at all. Names and counts only, never what you wrote. Deleted after 180 days.
- Website visits
- Everybody who opens vytalityfitness.com, signed in or not. A random number is made when the tab opens and thrown away when it closes — so a visit can be measured and the same person on another day cannot be recognised. Against it: which pages were opened, which site you arrived from (the site, never the full address and never a search you typed), which films were played and which buttons pressed, roughly how long the visit lasted and how far down the page it got, and the rough size of the screen. No cookie, no account, no IP address and no city — and there is deliberately no column anywhere to attach a visit to an account, so even for somebody signed in this cannot be turned into a record of what they read. Names and counts only, never what you wrote. Deleted after 400 days. Separately we keep Cloudflare's own daily count of how many pages were served, which identifies nobody at all.
- Country
- The country your connection comes from, as Cloudflare works it out when the app opens — checked at most once a day, keeping the first and the latest. The country only: not your IP address, not your city. It is also what decides which currency prices are shown to you; Stripe settles the one you are actually charged in at checkout. If you subscribe, the billing country from your payment details as well.
- Connected apps
- Only if you connect another app to Vytality — an AI assistant, say. Which app you authorised and when; which of Vytality’s own tools it asked for, and at what time; and whether a coach request came through it rather than through Vytality itself. Never what you asked that app and never what it answered — and never what you asked it about either: the tool’s name is kept, the exercise or the date you named is not. The record of which tools were used is deleted after 180 days. It all ends when you disconnect the app, under Connected apps on your profile, or when your account goes.
- Operational
- How many coach requests you have made in the last day, so a runaway client hits a limit rather than a bill; and how many coach requests the app makes and what they cost.
There is no address book access and no location tracking beyond the country above — no GPS, no city. Everything in the two rows above is first-party and goes nowhere else. Two measurements are not our own: Cloudflare's page counter, which sets no cookie and builds no profile, and the Meta Pixel, which does both — it is on every page of vytalityfitness.com, the app included, and is described under Meta below. The Meta Pixel is the one advertising identifier here.
Where it lives
Everything is written to your device first, in the browser's own storage, and synced to a Supabase project hosted on AWS in Canada (ca-central-1). Photographs are held in that project's storage.
Who can see it
You, with one exception you switch on yourself. Every table enforces owner-only access at the database level — row-level security keyed to your account — and there are deliberately no administrator read policies anywhere in the schema.
There is one exception, and it is off until you turn it on. If you join the weekly leaderboard, the other people in it see the name you chose for it and four percentages — how much of your own weights, cardio and nutrition goal you met that week, and the average of the three. Not your weights, not your weigh-ins, not your meals, not your check-ins, not your photographs, and not your email address or your real name. You see the same four things about them. Nobody who has not joined sees any of it, and leaving stops you appearing to anyone.
While a challenge is running they also see two more things, and only two: how many entries are in the draw altogether, as one number with nobody's name on it, and — once it has been drawn — the name of whoever won. How many entries each person has is never shown to anybody but them. And if you are the one who wins, your name goes no further than the app unless you tell us it can: not onto the challenge page, not onto social media, and not into an email to anyone else.
Strava is the one place your training leaves Vytality on purpose, and only if you connect it. Everything above is about who can see your data inside this app; a Strava activity is on Strava, under your name, visible to whoever your Strava settings let see it. What goes is the day and what it trained, how long it took, how many exercises and sets, and the name of the one movement you started with — or, for cardio, the minutes and what kind it was. What does not go is the rest: no weights and no reps, no list of everything you lifted, nothing from your check-ins, nothing you told the coach, none of your session feedback, no photographs and nothing about your nutrition. Nothing is ever read back the other way — Strava makes every connected app able to see your public profile and does not offer a way to decline it, and we never ask it for anything. Disconnecting stops it, and an activity already on Strava stays there until you delete it on Strava — we cannot reach back and remove it.
Underneath, nothing was loosened to do that: there is still no policy anywhere letting one account read another's rows. The standings are assembled by a single server function that returns those fields and no others, and it answers only to someone who has joined.
Vytality has an operator dashboard, and it is built so that it cannot show what you wrote. It sits behind two separate sign-ins, is open only to named people at Vytality, and every visit to it is logged. It reads through one server function that returns counts, dates, account and subscription status, country, and how much each feature is used — how many accounts, who has not finished onboarding, how many workouts were logged this week. It returns no check-in reflections, no notes, no meal descriptions and no photographs, because the queries behind it do not select them. Nobody at Vytality reads your check-ins, your notes or your photographs.
Who else is involved
- Anthropic
- Processes your coach conversations, meal descriptions and meal photographs to produce a reply. It does not train models on them.
- Supabase
- Database, authentication and photograph storage. The data processor for everything above.
- Your browser or phone's push service
- Only if you turn notifications on. Apple, Google or Mozilla, depending on the device — whoever made the browser or phone operates the service that actually delivers a notification to it. They carry the message; it is encrypted so that only your own device can read it.
- Cloudflare
- Serves the site, works out which country a connection comes from (the country is all that is kept), and counts the pages it serves — no cookie, no per-person profile. We read those daily totals back and keep them, so the traffic history outlives Cloudflare's own window; they are counts of pages, with nobody identified in them.
- Meta
- The Meta Pixel runs on every page of vytalityfitness.com, signed in or not, including the app. Each time a page loads it tells Meta the address of the page, your IP address and browser, and sets a Meta cookie (_fbp) so Meta can recognise the same browser again. Meta can match that to a Facebook or Instagram account you are signed in to, and uses it to measure and target our adverts. It is also told about what you do on the way in: how far down the front page you scrolled and which sections you reached, how long the page was in front of you, which film you played and how much of it you watched, which social link you tapped, whether you read to the end of the challenge rules, that you tapped sign up, sign in, Google, Apple or forgot your password, that you started, filled in, left or sent the sign-up form (that a field was filled, never what you typed) and what kind of error it gave if any, that you pressed an email link to us, opened a page such as pricing or the FAQ, confirmed a new account, opened the app from your home screen, finished setting up, joined Ranks, opened the share sheet, and started or completed a subscription (the plan's name, never a price or card). It is never sent any training, food, weight, photograph or check-in data, and no name or email from your account. Blocking Meta's scripts or cookies in your browser stops it and nothing in the app depends on it.
- PostHog
- Product analytics on the public pages of vytalityfitness.com, and only while you are signed out. It is told which page you opened, the site you came from (the site, not the page), your browser, screen size and IP address, which links and buttons you pressed and what they are labelled, and the same steps our own visit counter records: that you scrolled past the top of the front page, which film you played, that you tapped sign up or sign in, opened the sign-up form and sent it, and how long you stayed. It sets no cookie and keeps nothing in your browser, so a visit tomorrow is a new visitor. It is never told your name, your email or anything you type, it records no video of your screen, and it stops the moment you sign in, so nothing from inside the app reaches it. PostHog stores this in the United States. Blocking it in your browser breaks nothing.
- Stripe
- Only if you subscribe. Takes your payment; your card details go to Stripe and never reach our database. We keep the subscription, its status, the amounts charged and your billing country.
- Account email — invitations, password resets, the weekly check-in reminder if you leave it on, and once in a while a one-off note about something happening in the app — is sent over SMTP from our own domain. We keep a record of which one-offs have been sent to you, so nobody gets the same thing twice: a short name for it and the date, never a copy of the message or of your address. It goes when your account does.
- Strava
- Only if you connect it. We send the workouts you finish to your own Strava account, where Strava's own privacy settings decide who can see them. A workout carries its duration, its exercise and set counts and the name of the movement you started with — never a load, a rep count, or the rest of what you lifted. Strava also grants every connected app the ability to see your public profile — it is not optional and we never use it. Disconnecting ends it, and hands the permission back to Strava at the same time.
- Only if you choose to sign in with Google. Google tells us your name, your email address and that the address is verified; we never receive your Google password and we ask for nothing else from your account. Google will know you use Vytality. Signing in with an email address and password instead avoids this entirely.
- Apple
- Only if you choose to sign in with Apple. Apple tells us your name and an email address, and lets you hide the real one behind a relay address it forwards — if you do, that relay is the only address we ever hold, and it is what the weekly check-in goes to. We never receive your Apple password. Apple will know you use Vytality. Signing in with an email address and password instead avoids this entirely.
- An AI you connect yourself
- Only if you connect one. Vytality does not choose it and has no agreement with it: you authorise an app — Claude or ChatGPT, say — and from then on it can read your training, your food goals and a re-planned week on your behalf, under whatever terms that app has. The one thing it can write is feedback you ask it to send us, which arrives here the same way the form in the app does. It cannot change or delete anything you have logged, read what you wrote at a check-in or any feedback you sent us, or see your progress photographs — the database refuses those to a connected app, rather than our code choosing not to send them. Deleting your account ends it.
- Kit
- Only if you enter your address in the updates form on the front page. Separate from your account, and you can unsubscribe from any of those emails.
Email you can turn off
One a week at most: a note that the previous week has closed and is waiting for a check-in. It stops as soon as you check in, and you can switch it off entirely under Settings on your profile. Account email — invitations, password resets — cannot be switched off, because without it you would be locked out.
Cookies and storage
Our own servers set no cookies. The only cookies on vytalityfitness.com come from the Meta Pixel, which runs on every page, the app included, as soon as the page loads.
- _fbp (Meta)
- Set on this site by the Meta Pixel. A random identifier that lets Meta recognise this browser on later visits, so it can measure our adverts. Lasts 90 days from your last visit.
- _fbc (Meta)
- Set only if you arrived by clicking one of our adverts on Facebook or Instagram. It records that click so Meta can tell whether the advert led to a visit. Lasts 90 days.
- Meta's own cookies
- If you are signed in to Facebook or Instagram in the same browser, your browser sends Meta's cookies with each request the pixel makes to Meta. That is how Meta can link a visit here to your account. We cannot see or read those cookies.
Separately from cookies, the app keeps things in your browser's own storage so it works offline and remembers small choices: your sign-in session, a local copy of your training data, settings such as whether you have dismissed a prompt or prefer the list or card view, short coach lines cached for the day, a draft you have not finished, and feedback waiting to be sent. The website visit counter described above keeps a random number for the length of a tab and then forgets it; while you are signed out that number is also what PostHog knows your visit by. Nothing else here is sent to anyone else. Clearing your browser data signs you out and removes the local copy, not the synced one, and blocking Meta's cookies or scripts in your browser stops the pixel without breaking anything in the app.
Removing it
Profile, then delete my account. It removes the account, every row attached to it and every photograph — immediately, permanently, and without a recovery window. Any subscription is cancelled in the same moment and your customer record at Stripe is deleted with it, so nothing is charged again. You are free to sign up again afterwards, and nothing will be waiting.
Three things outlive an account, and none has you in it. If you ever paid, the record of each payment and subscription change is kept — no longer linked to an account here, and holding no name or email — because the books have to add up; Stripe keeps its own payment records under its own policy. The daily totals — how many accounts, how many on a trial, how many subscribed — are numbers with nobody in them. And a deletion itself leaves one line: the date it happened, the date that account was opened, and whether its email had ever been confirmed. No name, no address, no identifier of any kind — nothing that could say whose account it was, or bring any of it back. It exists so we can tell that accounts were removed at all, which is otherwise the one thing here that leaves no trace.
To ask anything, or to request a copy of your data, write to [email protected].