Privacy

Updated 19 September 2026

The short version. We collect what the app needs to do its job and nothing else. We do not sell your data. We do not use it for advertising. Health and fitness data is never used for anything but showing you your own training. You can export everything or have it deleted, at any time, by asking. One thing we would rather you read than discover: several features work by sending material to a company outside this app to be read — a meal photo, an InBody sheet, an injury document, a question you ask the in-app coach. Each one is named in What the AI features send, with the exact list of what goes.

What this covers

The three Repple apps — Repple, Repple Coach and Repple Studio — and this website. They share one account system and one database, so this policy covers all of them together.

Who we are

Repple is operated by Washateria LLC. For anything in this policy, write to support@repplefitness.com.

What we collect

What we collect, why we collect it, and when
What	Why	When
Email and password	To create and secure your account.	Always. Passwords are stored hashed; we never see them.
Name and profile photo	So your coach knows who you are.	If you enter them.
Date of birth, sex, height, weight	Heart-rate zones and calorie estimates are calculated from these.	If you enter them.
Workouts — exercises, sets, reps, weight, perceived effort, cardio, calories, time in heart-rate zone	Your training history, progress and personal records.	When you log a workout or import one.
Apple Health data — heart rate, active energy, steps, resting heart rate, workouts	Live heart rate and calories during a session, and importing workouts you recorded on your watch.	Only if you grant Health permission. You can revoke it at any time.
Blood glucose — readings a continuous glucose monitor wrote into Apple Health or Health Connect	Shown beside your own food log, so you can see what happened around a meal. Repple does not interpret them and does not tell you what to eat.	Only if you ask for it on the Blood Sugar screen and grant that permission separately. Your coach sees none of it unless you turn sharing on yourself.
Sleep — hours slept and how many nights a device actually measured, from Apple Health, Health Connect or a wearable you connected	Shown in your own record, and used as one input to the readiness figure.	Only if you grant Health permission or connect a device that reports it. Nights you typed in yourself are kept apart from nights a device measured, because a guess and a measurement are not the same fact.
Body measurements and InBody scans	To show change over time.	If you record them.
Photographs of a meal, or of a scan printout	Only to read them — the food in a meal photo, the figures on an InBody or DEXA sheet — so you do not type them in by hand.	Only when you ask Repple to read one, and we ask before the first time. The picture is sent to be read and is not kept: what is stored afterwards is the figures, not the photograph. A scan sheet often carries your name and date of birth, so this is asked per sheet rather than once.
Progress photographs	To compare two of them side by side. Held in a private store, reachable only through a temporary link you ask for.	If you take them. A coach cannot see one unless you share that specific photo with them, and you can withdraw it.
Injuries, and any document you upload about one	So the training plan works around the area until you mark it recovered. Your coach sees the area and the severity, never the document.	If you record an injury. Uploading a document is a separate step, and sending one to be read as text is a separate question we ask you per document.
Food and meal logs	Nutrition tracking, and sharing with your coach if you have one.	If you use the nutrition features.
Check-ins and habits	Weekly progress and consistency.	If you use them.
Messages between you and your coach	To deliver them.	When you send one.
Device push token	To send notifications you have asked for.	If you allow notifications.
Connected device tokens (WHOOP, Oura, Spotify)	To read the data you connected them for.	Only if you connect that service. Fitbit and Garmin are listed in the app but cannot be connected yet, so there is no token for either.
Agreements you sign — Repple’s own liability waiver, and any paperwork your gym asks for	To hold the record of what you agreed to, as it was worded at the time. Repple’s waiver is the release and physician acknowledgement that opens the client app. A gym can additionally ask you to sign membership terms, a contract, a pre-exercise health questionnaire (PAR-Q), permission to photograph you in the building, or — for a member under 18 — a guardian’s agreement.	When you sign one. These are evidence, so a signed agreement cannot be edited or withdrawn afterwards; re-wording one later creates a new record rather than changing the old. Repple’s own waiver is readable by you and by nobody else — not your coach and not your gym. A gym’s paperwork is readable by that gym, which is the point of it.
Crash and error reports	To find and fix faults.	When the app hits an error.
Payment records	For trainers and gyms taking payment through Repple.	Card details are handled by Stripe and never reach our servers.

We do not collect location, contacts, browsing history, or advertising identifiers.

Apple Health and Health Connect, specifically

Health data gets stricter treatment than everything else, because it should. This applies to Apple Health on iPhone and to Health Connect on Android, which are the same arrangement on the two platforms — your monitor or watch writes into the phone’s own health store, and Repple reads from there:

It is read only after you grant permission, and only the types listed above.
It is used solely to show you your own training, recovery and readings.
It is never used for advertising or marketing, and never sold or shared with data brokers.
It is not shared with anyone other than a coach you have deliberately linked to your account.
It is not sold, and it is not used to train any model.
One qualification, because “it never leaves” would be too strong. Repple turns your recent sleep into a readiness score, and if you switch on health sharing for the in-app coach chat, that score is sent to Anthropic along with your other body figures — as a number and a short phrase, such as “68/100 (fair), from three nights”. Your heart rate, steps, energy and workouts are not sent anywhere; they are read to draw your own charts and stay in your own record. Leave health sharing off and none of it goes.
Revoke it whenever you like — on iPhone in Settings → Privacy & Security → Health → Repple, on Android in Health Connect → App permissions → Repple. The app keeps working without it.

Blood glucose is asked for separately. It is not part of the permission Repple asks for when you connect a watch, because most people do not wear a monitor and a permission screen listing things an app will not use is a screen nobody reads. Repple asks for it once, when you first open the Blood Sugar screen, and never again on its own. Readings are shown to you beside your own food log. They are not visible to your coach unless you switch that on yourself, and switching it off again hides the history as well as the next reading. Repple does not diagnose, does not set targets, and does not tell anybody what to eat — the range it shows is the one commonly quoted for adults, and your own targets come from your clinician.

If you turn it on, Repple also writes the workouts you log back to Apple Health, so your rings and history include training you did in the gym. It is off unless you switch it on, and only sessions with a recorded length are written — we do not estimate a duration in order to fill one in.

Who can see your data

You. Always.
Your coach, if you accept a coaching link — they can see your training, and your nutrition and check-ins where those features are used together. You can end the link.
Your gym, if you are a member of one, sees membership and attendance information for running the gym. Owners do not get your private messages.
Nobody else is shown your record. We do not sell data, we do not share it for advertising, and we do not hand anything to a third party for their own purposes. The companies that process data so the app can function are a different thing from an audience, and they are listed by name in Services we rely on rather than left to the phrase “our partners”.

Services we rely on

These process data on our behalf so the app can work. They are bound to use it only for that. The first four run for everyone; the rest only start when you use the feature beside them:

Supabase — database, sign-in and file storage.
Expo — delivering push notifications. A push carries the sender’s name and the first 180 characters of the message, because that is what a notification has to show on a locked screen.
Resend — sending account emails such as password resets.
Cloudflare — serving this website.
Anthropic — reading the things Repple asks a model to read. This is set out in full under What the AI features send, and where below, because it is the part of this list most worth knowing about.
OCR.space — turning a photographed or uploaded document into text. Also covered below.
Cheaper Inference — a second, alternative route to the same model reading, which Repple can be switched to instead of contacting Anthropic directly. It is not in use unless we switch it on, and it is set out beside Anthropic under What the AI features send, and where below, because what it receives and what it retains are not the same as Anthropic’s.
Stripe — payments, where a trainer or gym takes them. Stripe handles card details directly; we never receive them.
Open Food Facts — barcode and food-name lookups. Your phone asks them directly, so they see the barcode you scanned and your IP address, but nothing that identifies your account.
Spoonacular — the recipe library behind the Meals list, and only when you search it. Our server asks on your behalf, and what it sends is the search and nothing about who is searching: the diet you have set, the allergens you have asked to avoid, the kind of meal, a calorie range, and any words you typed into the search box. Not your name, your email, your account or your IP address — to Spoonacular every Repple member is the same one caller. Two things do reach them from your phone rather than from us. A recipe’s photograph is loaded from Spoonacular’s image server, so that server sees your IP address and which photograph was asked for, as any website hosting an image would. And each recipe credits the website it came from with a link; if you tap it, you are on that website and under its policy, not ours. Spoonacular’s terms do not let us keep its recipes, so we do not: a recipe you add to your plan is remembered as its title, its photograph’s address and its number in their library, and is asked for again when you open it.
WHOOP, Oura, Spotify — only if you connect them, and only for what you connected them for. Spotify is the one that goes outwards rather than inwards: it creates a playlist in your own Spotify account.
Google, Meta and TikTok — inside the apps, for coaches only, and only for a coach’s own accounts: putting a coach’s own sessions on their own calendar, and reading back what a coach’s own advertising cost them. A client’s name is never sent to any of the three. A calendar event Repple writes says “Coaching session” and nothing else. Google separately receives a request from this website, from everybody, and that is set out immediately below rather than folded into this line.

This website, separately from the apps

Everything above is about the Repple apps. This page you are reading is a plain static site with no analytics, no tracking pixels, no advertising tags, no cookie banner and no cookies at all — we set none, and we measure nothing about your visit. There is no banner because there is nothing to ask you about. The one thing that does get written to your browser is a sign-in session, on the pages where you sign in, kept in your browser’s own storage so you stay signed in; it is not a cookie and it is not sent to anybody but Supabase. That is worth stating because it is unusual, and because it makes the two exceptions easy to name honestly:

Google Fonts (fonts.googleapis.com and fonts.gstatic.com). The typefaces on this site are fetched from Google when the page loads. To serve them Google receives your IP address, your browser’s user-agent string and the address of the page you are on. This happens on every page of this site, including this one, before you have agreed to anything — so it is not covered by the “coaches only” line above, and we would rather say so than let that line read as though Google hears nothing about an ordinary visitor. Nothing is sent that identifies your Repple account, because at that moment you do not have one loaded.
jsDelivr (cdn.jsdelivr.net). The pages that talk to your account — creating one, confirming it, resetting a password, joining a gym by invitation — load the Supabase browser library from this public code CDN. It receives your IP address and user-agent when it serves that file. It receives none of what you then type: your email and password go from your browser straight to Supabase.

Both are ordinary practice on the web and both are avoidable, which is the reason for naming them: serving the fonts and that one library from our own domain would remove both requests, and we would rather record the gap than describe a site that does not make them.

What the AI features send, and where

Several things in Repple are done by a model that does not run on your phone, which means the material it reads leaves this app. That is worth a section of its own rather than a line in a list.

Anthropic processes the following, each only when you use that feature:

The in-app coach chat. What you type, plus a fixed list of facts about your training: your goal, your program, your calorie and macro targets, what you have eaten today, your streak and when you last trained. Your name is not sent.
Your body and health figures, but only if you switch that on. Weight, body fat, skeletal muscle, your readiness score, and the area and severity of any injury you have recorded. This is a separate switch from the chat itself, it is off until you turn it on, and the note you wrote against an injury is never sent — only the area and how bad it is.
Photographs. A meal photo, a physique photo, an InBody result sheet or a photo of a gym machine is sent as an image when you ask Repple to read one. It is the image itself, not a description of it.
A meal you describe in words — the text you typed, up to 500 characters, and nothing else about you.

OCR.space receives the whole of any document you ask Repple to read: an InBody printout, or an injury document such as a physiotherapy report or a scan result. It is sent as an image, page by page, to be turned back into text.

Two things about that are worth saying plainly rather than leaving you to assume them. Repple asks you before sending an injury document, names OCR.space when it asks, and keeps a record of your answer — so an injury document is only ever sent because you said yes to that document. But Repple does not currently ask OCR.space to avoid retaining the upload, so we cannot tell you how long a copy sits on their side. If you would rather not send a document at all, decline and type the detail in by hand; the injury feature works either way.

The alternative route, and why it is described separately

Repple can be configured to send all of the above through Cheaper Inference rather than to Anthropic directly. It is off unless we switch it on, and this section is here so that the page describes what the app is capable of doing rather than only what it happens to be doing today. If we do switch it on, everything listed above goes to them instead, in the same detail.

Three things about that arrangement are different from the one above, and worth stating plainly rather than leaving inside the phrase “a service we rely on”:

It is a reseller, not the company that runs the model. It receives the request and forwards it to whichever company operates the model we have asked for — which may be Anthropic, and may be another company entirely. So it sees everything Anthropic would see, and it is not the last party to see it.
Its requests are answered by further companies again. A reply Repple received while this route was being tested recorded that it had been served by a separate compute provider. The chain is therefore at least three companies long, and which companies are in it depends on the model we name.
It does not offer zero retention. Its own published catalogue of models records, for every one of the sixty-five it offers, that zero data retention is not available, and lists no route that would provide it. That is a weaker guarantee than the direct arrangement described above, and it is the reason this route is off rather than on.

We have not verified their retention practices beyond what that catalogue states, and we would rather record the limit of what we know than describe a guarantee we have not seen.

Repple does not use anything you record to train a model, and does not give any of these services permission to use it for their own purposes. Where that rests on a retention guarantee rather than on our own instruction, the paragraph above says which route carries one and which does not.

Keeping it safe

Every connection is encrypted in transit, and Supabase encrypts the disks underneath the database and the file store. Access is enforced at the database itself: every table carries row-level rules, so one person's records are not reachable by another account even if the app asked. No individual column carries a second layer of encryption on top of that, so what protects your row from another account is the rule rather than a key. Nobody at Repple browses your training data as a matter of routine. Security & data sets out the mechanism in detail — who can read what, and why a progress photo reaches a coach only when you share that photo.

How long we keep it

For as long as your account exists, because a training history is only useful over time. When you delete your account we remove your personal data within 30 days, except anything we are legally required to keep — payment records for tax purposes being the usual case.

Your records and your files are two different things in two different places. Deleting the account deletes the records outright; the files go on a queue, and a scheduled job sends a delete for each one within minutes. That covers progress photographs, injury documents, message attachments, your profile photo, and on the coaching side a logo, a published document or an exercise clip. An entry is closed only when the file store confirms the object is no longer there — a file that has been asked for is not yet a file that has gone, and we record the second of those. One store is deliberately not on that queue: a document a gym filed about a member is stored under the gym rather than under the person, and how long a gym must keep it is a legal question with a different answer in each country. That decision has not been made, so those files stay. The full position is set out on Deleting your account rather than summarised into something more comfortable here.

Deleting your account sets out exactly what is removed, what survives, and how to ask.

Your rights

Get a copy. Ask and we will export everything we hold about you. There is also an export in the app, under Me → Settings → Your data — it is not quite everything, and Deleting your account lists what the in-app one leaves out. Ask us and you get the rest.
Correct it. Most of it you can edit in the app; ask us for the rest.
Delete it. Request account deletion in Me → Settings, or email us. Worth knowing which of those two is the reliable one: the in-app request records that you asked, and a person then has to carry it out — if you are not a member of a gym there is nobody on the other end of it, so a request made that way can sit unseen. Emailing us always reaches a person. Deleting your account explains why it is built that way.
Withdraw consent. Turn off Health access or disconnect a device whenever you like. The same goes for the narrower permissions: a progress photo you shared with a coach can be withdrawn one photo at a time, and the switch that lets the in-app coach read your health figures can be turned back off. An answer you gave about one injury document or one scan sheet applies only to that document; the next one asks again.
Object or complain. If you are in the UK or EU you may also complain to your data protection authority.

Email support@repplefitness.com for any of these. We will respond within 30 days.

Children

Repple is not intended for children under 16. We do not knowingly collect data from them. If you believe a child has an account, tell us and we will remove it.

Where data is held

Our database and file storage are operated by Supabase and may be processed outside your country. Where data leaves the UK or EEA, it is transferred under the safeguards those rules require.

Changes

If this policy changes in a way that matters, we will say so in the app before the change takes effect. The date at the top always reflects the current version.

Contact

Questions, requests or complaints. Support covers the practical side — exporting, deleting, connected devices — and this address reaches a person:

support@repplefitness.com