What we store,
and what we don’t
Last updated 26 August 2026
FitLexx works by reading what you actually did — what you ate, how you slept, what you lifted — and rebuilding today from it. That only works if you tell it things about your body. This page says exactly what happens to those things.
ON THIS PAGE
- Who you are dealing with
- What FitLexx stores
- What you agreed to, and how to take it back
- The coach, and where your words go
- Where the data lives
- Who else can see it
- How long we keep it
- Your rights, and the two buttons
- Security
- Cookies and tracking
- Children
- Changes to this page
- Contact and complaints
1. Who you are dealing with
FitLexx is operated from India and is the data fiduciary for everything described here — meaning we are the ones who decide what is collected and why, and the ones you hold responsible for it.
Everything on this page can be asked about at support@fitlexx.com.
2. What FitLexx stores
This is the whole list. It is not a summary — it is every table in the database that has your name on it, and you can pull all of it out yourself at any time (see section 8).
| What | Which means |
|---|---|
| Your account | Your email address, and the date you signed up. There is no password unless you set one — signing in is a link in the post or a Google account. |
| Your profile | What you told the app when you set it up: age, sex, height, weight, your goal, how many days a week you can train, what equipment you have, and any injuries you flagged so the plan avoids them. |
| Your plan | The block the engine built, the sessions in it, and every exercise, set and rep it prescribed. |
| What you did | Every set you logged: the weight, the reps, and the effort you rated it. Which sessions you finished and which you skipped. |
| Your day | The daily tasks the plan set, whether you did them, and the adherence score that comes out of it. |
| Food | What you logged eating, and the calories and macros that came from it. |
| Signals | Numbers about your body that the plan reads: weight, sleep, resting heart rate, heart-rate variability. Only what you enter or connect — nothing is taken from your phone in the background. |
| Coach conversations | Both halves. Your question and the answer, exactly as they appeared on screen, so the thread is still there when you come back. |
| AI usage records | That a request was made, which model answered, what it was for, whether it succeeded, and how many tokens it cost. Not the question and not the answer — that record is deliberately built to hold no content at all. |
| Consent records | Every consent you gave or declined, which version of it, and when. This ledger can be added to but never edited or deleted, because a record of permission that can be quietly rewritten is not a record of permission. |
| Pods | If you join a pod, that you are in it — and, only if you have separately agreed to share, what the other members see. |
Some of this — your weight, your sleep, your heart rate, your injuries — is health data, and Indian law treats it as sensitive. So does FitLexx: the engine refuses to run at all until you have given health-data consent, and that is enforced in the database rather than in the app, so it holds no matter what is asking.
What FitLexx does not store
- No photographs of you. There is no body-photo feature.
- No location. The app never asks for it.
- No contacts, no calendar, no microphone, no camera roll.
- No card details. There is nothing to pay for yet, and when there is, a payment provider will hold the card and we will not.
- No advertising identifiers, and no third-party analytics.
3. What you agreed to, and how to take it back
Two consents are asked for when you set up the app, separately, with the reason written next to each:
- Terms of service — required, because it is the agreement itself.
- Health data — required for the engine to work, because the engine is entirely made of your health data. Without it there is no plan to give you.
Anything beyond those is optional and asked for at the moment it is needed — sharing inside a pod is asked for when you join one, not bundled into sign-up.
You can withdraw any consent from You → Privacy in the app. Withdrawing health-data consent stops the engine, because there is nothing left for it to read. Withdrawing an optional consent stops only the thing it was for.
4. The coach, and where your words go
When you ask the coach something, or the app asks it to explain a change, the question and the context the app builds around it — the session in question, and the recent training it refers to — are sent to DeepSeek, the company whose model writes the reply. That is a transfer of your data to a third party outside India and you should read it as one.
What we keep of it: the conversation, so the thread survives, and a record that a call happened — model, purpose, outcome, token count. Nothing in between.
What we do not control: what DeepSeek does with the text once it has it. Their terms govern that, not ours. If that matters to you, the coach is optional — the plan, the logging and the tracking all work without ever calling it.
The AI never decides anything about you on its own. Every number in your plan — sets, reps, weights, rest, calories — is produced by a deterministic solver that runs on our own servers. The model is only allowed to choose between options the solver has already approved, and to put things in words. There is no automated decision here that has a legal or similarly significant effect on you.
5. Where the data lives
On servers we run in Mumbai, India (AWS ap-south-1). The database is not shared with any other product and is not reachable from the internet — only the API in front of it is.
The one place your data leaves that machine is the coach, described above.
6. Who else can see it
Nobody, with three exceptions:
- DeepSeek, for the text you send the coach. Section 4.
- Google, if you sign in with a Google account — they tell us your email address and name, and they know you signed in here. Signing in with an emailed link involves them not at all.
- Your pod, if you join one and separately agree to share — and only the things that consent covers.
- Us, when something is broken and there is no other way to fix it. Any such access is recorded in an audit table that cannot be edited, and deleting an account does not erase the record that somebody looked at it while it existed.
We do not sell your data. We do not share it with advertisers. There is no advertising in FitLexx and no plan to put your data into any.
If we are ever legally compelled to hand something over, we will — and we will tell you unless we are forbidden from telling you.
7. How long we keep it
Until you delete it. FitLexx does not expire your training history, because a training history is the point — a plan built from two years of lifting is better than one built from two weeks.
When you delete your account, everything in the table in section 2 goes with it, in the same transaction. Two things survive, and neither names you:
- The record that an AI call was made — model, purpose, outcome, cost — with the link to you removed. It never held your words.
- The record that somebody at FitLexx accessed an account, if they ever did, with the link to you removed. Erasing a person must not erase the fact that they were looked at.
8. Your rights, and the two buttons
Under India’s Digital Personal Data Protection Act you can ask what we hold, ask for it back, ask for it corrected, and ask for it erased. Two of those are buttons rather than requests, because a right you have to email someone about is a right with a queue in front of it.
You → Your data → Export gives you every row above as a JSON file, immediately, on your device. Nothing is emailed and nothing is held for review.
You → Your data → Delete account ends the account and everything in it. It asks you to type DELETE first, and then it is done and cannot be undone.
For correction, or for anything the buttons do not cover, write to support@fitlexx.com and we will answer within 30 days.
You can also nominate someone to exercise these rights on your behalf if you die or become incapacitated. Ask us and we will set it up.
9. Security
- Everything between your device and us travels over TLS. There is no unencrypted path.
- Every table is protected by row-level security in the database itself, so a query can only ever return your own rows — not because the app remembers to filter, but because the database refuses.
- Sets logged where there is no signal are held encrypted on your own device until they can be sent.
- Signing in does not involve a password unless you choose to have one.
If we ever have a breach that puts you at risk, we will tell you and the Data Protection Board, as the law requires.
10. Cookies and tracking
These pages — the home page and the documents like this one — set no cookies, run no analytics and load nothing from anybody else. Not a font, not a script, not a pixel. That is why there is no cookie banner: there is nothing to consent to. It is checked on every deploy, which refuses to publish a page that reaches another domain.
The app, at fitlexx.com/app, loads one thing from elsewhere: Google’s sign-in script, from accounts.google.com, so that the “Continue with Google” button can work. Google sees that request. If you would rather it did not, the email link signs you in without it and the app works identically either way.
The app keeps your sign-in token in your browser’s own storage so you are not asked to sign in on every visit. It never leaves your device except to prove to our API that it is you.
11. Children
FitLexx is for adults. It is not intended for anyone under 18 and we do not knowingly create accounts for children. If you believe a child has an account, write to us and we will remove it.
12. Changes to this page
When this changes in a way that matters, the date at the top changes and we tell you in the app before the change takes effect. If a change needs your consent, you will be asked for it rather than assumed into it.
13. Contact and complaints
Write to support@fitlexx.com. That address reaches a person, and it is also the grievance channel required by the DPDP Act — if you are unhappy with how we handled something, say so there first and we will answer within 30 days.
If we do not resolve it, you can complain to the Data Protection Board of India.