Isoletics
Privacy policy
Last updated 5 October 2026.
Isoletics holds almost nothing about you, and this page is written from the actual database rather than from a template. If you want the short version: your email address, the numbers you record in training, and nothing else.
Who is responsible
Isoletics is operated by Gilvara Ltd, a private limited company registered in Scotland, company number SC854313, registered office 5 5/4 Nova Scotia Place, Edinburgh, Scotland, EH12 9FU. Gilvara Ltd is the data controller for the purposes of UK GDPR and the Data Protection Act 2018.
Questions, requests or complaints: privacy@isoletics.app.
What is stored, and why
Everything below is what the app's database actually contains. There is no hidden table.
| What | Why it exists | Where |
|---|---|---|
| Your email address | It is how you sign in. Isoletics uses a sign-in link rather than a password, so the address is the account. | Supabase (authentication) |
| Your kit and schedule — which equipment you have, how many days a week you train, how long a session is, and which body area you tapped when the app asked where you felt the limit | The plan is built from these. Without them the app cannot prescribe a session. | Supabase |
| Your test results — the seconds or repetitions you recorded for each exercise | This is what produces your level and your ladder. It is the product. | Supabase |
| Your enrolments — which skill you are working toward, when you started, how many sessions you have done | Progress toward the goal, and the autoregulation that decides when to advance you. | Supabase |
| Your last session's numbers per exercise | So the logger can show you what you did last time. | Supabase |
| Anonymous usage events — which screens were reached, which steps of the assessment were completed or abandoned | To find out where the app loses people. Most people who abandon do so before signing in, which is why this is collected separately and anonymously. | Supabase, and PostHog (EU) |
| A report you choose to send — which of the four kinds you picked, what you typed, the screen you came from, the app version, your platform and your phone's model name (for example "iPhone 15"), and an email address only if you type one in | So a bug can be found and fixed, and answered if you asked for an answer. Nothing here is sent unless you fill the form in and tap Send. | Supabase |
| Crashes — the error message, the technical stack trace, the screen you were on, the app version and your phone's model name | To find out what broke. Sent automatically when the app fails, because a crash nobody hears about is a crash that stays in the next version. | Supabase |
| Subscription status | To know whether to unlock the plan. | RevenueCat, Apple, Google |
The usage events are not linked to you
That table has no account column and no link to your account, by design. It is tagged with a random identifier generated on your device, which exists only to group one person's journey through the app into a sequence. It cannot be turned back into you, and the app itself has no way to read that table at all — it can only write to it.
Before any event leaves your phone it is filtered against a fixed list of permitted fields, and every piece of text in it is scanned and stripped of anything that looks like an email address, a phone number or a token. Nothing you type is sent.
Where you felt the limit
Once during the assessment the app asks where you felt the limit and offers nine choices: wrists, shoulders, chest, upper back, triceps, core, grip, legs, or just tired. You tap one, or you skip it.
There is no box to type in, anywhere in the app. The database will only accept those nine values and rejects anything else outright, so it is not possible for a medical detail to be stored here — not by you, not by a modified copy of the app. That is a constraint on the database itself rather than a promise about how we behave.
It is used for one thing: naming which area the plan should prioritise.
The one place you can type a sentence
After a session the app asks whether it was right for you and offers a box to say what was off about it. That box is optional and it is the only free text anywhere in the app — the only other things you can type are your email address and the numbers you hit on a set.
What you write is sent with the anonymous usage events, not with your account: it has no name and no account attached and we cannot tell who wrote it. Before it leaves your phone it is scanned and anything that looks like an email address, a phone number or a token is removed, and it is cut off at a fixed length.
Please don't put medical detail in it. It goes into a pile that decides what gets fixed next, read by us and nobody else, but it is free text and we cannot constrain what it holds the way we can constrain everything else. If you have written something there you would rather we did not have, email us and we will find it and remove it.
What is not stored
- No date of birth, no height, no bodyweight tied to your identity.
- No photographs or video of you. The app never asks for camera or photo access.
- No location of any kind.
- No contacts, no address book, no social accounts.
- No card or payment details — those go to Apple or Google and are never seen by Isoletics.
- No advertising identifiers. There is no advertising SDK in the app and no tracking across other apps or websites.
- No password, because there isn't one.
If this database were taken in full tomorrow, an attacker would learn an account's email address, how long that person can hold a tuck planche, and which days they train. That is the whole blast radius, and it is small on purpose.
What stays on your phone only
Some things never leave the device: the session you are part-way through, your sign-in token (held in the phone's secure storage), a cached copy of your subscription status so the app works without signal, and a referral code if you arrived through a creator's link. Deleting the app removes all of it.
Why we are allowed to hold it
- Performance of a contract — your account, your results, your plan and your subscription status. The app cannot do its job without them.
- Legitimate interests — the anonymous usage events, so the app can be improved. The interest is balanced against a near-zero impact on you: the data is not linked to you and cannot be read back out.
- Consent — the optional feedback note after a session. You give it by choosing to write something and tapping send, and you can simply not.
There is no special-category data in this app. The limiter question is a choice from nine body areas and nothing in the database can hold more than that, so the higher bar UK law sets for health data does not come into it.
Who else sees it
Isoletics does not sell data, does not share it with advertisers, and does not use it to train any machine-learning model. It is handled by a small number of suppliers who process it on our instructions:
- Supabase — the database and sign-in. Hosting region: [REGION — set this to your Supabase project's region, e.g. London (eu-west-2)].
- PostHog — the charts built from the anonymous usage events above, on PostHog's EU instance, so that data stays in the EU. It receives the same events the app already records and nothing else: no email, no account, no advertising identifier. Location lookup from your IP address is explicitly switched off in the request, and no personal profile is created. Nothing you type in a report and no crash is sent there.
- RevenueCat — subscription status. Receives an anonymous subscriber identifier and what Apple or Google report about the purchase.
- Apple and Google — they take the payment and tell us only whether a subscription is active. We never see your card.
Where a supplier processes data outside the UK, the transfer is covered by the UK International Data Transfer Addendum to the EU Standard Contractual Clauses.
We would also disclose data where the law requires it, and we would tell you unless we were forbidden to.
How long it is kept
- Your account and training data — until you delete your account. There is no silent expiry; your history is the point of the app.
- Deletion — immediate and complete. Every table is tied to your account and removed with it.
- Anonymous usage events — kept for up to 24 months. They contain no link to you, so they are not affected by deleting your account and cannot be retrieved for you.
- Subscription records — Apple, Google and RevenueCat keep their own records under their own policies, and we cannot delete those on your behalf.
Deleting everything
In the app: Account → Delete my account. It takes one confirmation and happens straight away. Your account and every row attached to it are removed, on our side and on your phone. There is no support ticket, no waiting period and no email to send.
If you cannot reach the app, email privacy@isoletics.app from the address on the account.
Your rights
Under UK GDPR you can ask for a copy of your data, ask for it to be corrected, ask for it to be erased, object to or restrict how it is used, withdraw consent, and ask for it in a portable form. Email privacy@isoletics.app and we will respond within one month. There is no charge.
If you are not satisfied, you can complain to the Information Commissioner's Office at ico.org.uk/make-a-complaint, or by calling 0303 123 1113. We would rather you came to us first, but you do not have to.
Children
Isoletics is not intended for anyone under 16 and we do not knowingly hold data about anyone under 16. If you believe a child has created an account, email us and it will be deleted.
Security
Every table enforces row-level security at the database, scoped to the signed-in account, on reads and on writes — so one account cannot reach another's rows even if the app were modified. Sign-in tokens are kept in the phone's own secure storage. The key that ships inside the app is a public one by design and grants no access on its own.
Changes
If this policy changes in a way that affects you, the app will tell you before the change takes effect. The date at the top always reflects the current version.