Privacy
Last updated 19 November 2026
What REPPIN stores
Your workouts, schedules, training history and reminders live on your device. If you sign in, a copy is backed up to your REPPIN account so it follows you between devices. Signing in uses your email address and a one-time code, or your Google account; there is no password.
Continue with Google. If you sign in with Google, Google tells REPPIN the email address of the Google account you choose, that Google has verified it, and the account’s Google ID. REPPIN keeps the ID and that address with your REPPIN account, so the same Google account finds the same REPPIN account next time even if its address changes. Google also passes on your name and profile picture; REPPIN does not keep them. Your REPPIN account is the one for that email address. When Google does not provide the address itself (anything other than a Gmail or Google Workspace address), REPPIN first sends the usual one-time code to it, once, before linking the Google account. While the sign-in screen is open, Google’s button is loaded from Google, so Google receives the ordinary details of that request, such as your IP address and browser, and may show the name of a Google account you are signed in to in this browser.
AI Coach
Photos for Coach. You can choose or take a photo — of your equipment, or of a workout or programme — and review or remove it before tapping Send. Sending shares a resized copy with Anthropic through REPPIN's server (directly with Anthropic if you use your own API key). Coach says what it sees and asks you to confirm or correct it before it builds anything. While that request is open, the photo is shared again with each message you send, so Coach can check it as it builds: until Coach has made what you asked for or says it can't, you send another photo, 30 minutes pass, you clear the chat, you switch Coach off, your account changes or the app closes. Until then the app holds it in memory on this device; it is not saved. Photo analysis uses Coach credits or your own API billing. The original file metadata is removed before sending. REPPIN does not store uploaded photos on its server or include them in account backups or Workout Links. An interrupted request can temporarily keep its photo on your device, under your account, so the request can resume. That copy is cleared when the request finishes; the chat keeps a text attachment label and Coach's reply, not the photo.
When you use Coach, your messages and the workout, calendar, history or reminder details Coach needs are sent to REPPIN's server and on to Anthropic to generate a reply. If you have saved details about yourself in Coach's “About you” card (age, sex, height, bodyweight — all optional), the fields you filled in are included with your Coach messages so it can personalise your training; saving them is your choice to allow that, and you can edit or remove them at any time. They are stored per account on your device and removed with the account, and are never used to compare you against other people. Nothing is used to train models. You control what Coach may read and change under Settings › AI Coach › Coach access.
Your conversation is kept on your device, not in your account backup. REPPIN's server keeps a copy of each reply for 7 days so that a turn interrupted mid-way can be recovered; a housekeeping job that runs every 6 hours clears replies older than that, and keeps only the accounting record (credits charged, no message content). On a shared device, each account's conversation is kept separately.
Reports. If you report a Coach reply, a shared workout or an invitation, REPPIN keeps the report so it can be reviewed: the kind of content, your reason, a short excerpt of what was reported, anything you wrote about it, and a one-way code derived from your IP address to prevent abuse. Ninety days after a report is closed, the excerpt, your words and that code are removed, leaving only the outcome; a report is deleted entirely a year after it is closed, or a year after it was made if it was never resolved. If you delete your account, your link to any report you made is removed at once along with your written detail, and reports you made about your own Coach conversations are deleted outright. A report about someone else's content may be kept, anonymised, for the periods above so that content can still be moderated.
Wearables
Connecting a wearable is optional. You authorise it with the provider (OAuth); REPPIN never sees your provider password. Access and refresh tokens are held only on REPPIN's server, are never shown in the app, and are never included in backups or Workout Links. REPPIN also stores the provider's stable account identifier for your account so provider notifications can be matched to you. Each provider's data is stored separately and is never merged with another provider's.
WHOOP
REPPIN obtains and stores a daily summary — recovery score, heart-rate variability, resting heart rate, sleep duration and performance, day strain — and your recorded activities. It is kept with your REPPIN account until you delete the account. Disconnecting WHOOP revokes REPPIN's access with WHOOP and deletes the tokens; the stored summaries remain until account deletion.
WHOOP data may be used by the AI Coach only if you separately turn on Coach access (Wearables, or Settings › AI Coach › Coach access — off by default). When on, Coach receives the daily summary compared with your own recent averages, never raw provider data, and it is not used to train models.
Notifications
Optional. If you switch notifications on, REPPIN stores with your account the browser's push subscription for that device (the push endpoint and its encryption keys), the device's time zone (so reminders arrive at the right local time), your notification preferences, and short-lived delivery records (a seven-day log used to prevent duplicate sends, and the time of the last successful or failed delivery, cleared on the same seven-day horizon). Notifications are delivered through your browser or phone's push service (for example Google or Apple) and may contain the name and time of a booked workout, the title, time and the first line of the note of a reminder you set, a summary of today's plan, a readiness line from a connected wearable, or — if you use Chat and messages and keep their switches on — who sent you a message and how it begins (a message request says only who wants to message you). Turn them off any time in Settings → Notifications; signing out everywhere also stops them, and deleting your account removes the subscription records.
Your reminders. The reminders you set in REPPIN — their titles, notes, times, how they repeat and where they open — are part of your training data: on your device, and in your account's backup when you are signed in. With notifications on, REPPIN's server reads them from that backup to send each alert at its time. It keeps a record of each alert it plans for the day ahead (which reminder, which day, how long before, when it is due) and, once it is sent, when it was sent and a digest of the token the notification carries, so that Snooze and Done on the notification work without signing in, for two days; a day you answer Done is kept for 14 days, so that its later alerts are not sent. Quiet hours, if you set them, are kept with your notification preferences, and reminders come silently in them. Signing out everywhere removes the alerts planned or sent, and deleting your account removes them all. A reminder during a workout is rung by the app alone and leaves your device only in your backup.
Fitbit (Google Health)
Fitbit and Pixel Watch data is obtained through Google's Health API with your Google account's consent. REPPIN obtains and stores a daily summary — sleep duration of your main sleep, nightly heart-rate variability and daily resting heart rate (if you grant the health-metrics permission), steps and active minutes — and your recorded exercises, plus Google's stable health user identifier for your account. Retention is the 45-day product window; older records are removed automatically. Disconnecting revokes REPPIN's access with Google and deletes the tokens and all Fitbit-derived data from REPPIN immediately; revoking REPPIN from your Google account has the same effect. If you separately turn on Coach access, a daily summary of this data (never raw readings) may be sent to Anthropic, REPPIN's AI provider, solely to produce your personalised Coach response; it is not used for advertising or to train models. REPPIN's use of information received from the Google Health API adheres to the Google Health API Developer and User Data Policy, including the Limited Use requirements. You can request deletion at any time at [email protected]; requests are actioned within 72 hours.
Oura
REPPIN obtains and stores a daily summary — readiness score, average heart-rate variability and lowest heart rate during sleep, sleep duration and sleep score, steps and active minutes, and, where your Oura account provides them, the daily stress summary and resilience level — and your recorded workouts. Oura-derived data is used only for REPPIN's own displays (the Wearables page and today's readiness card) and REPPIN's deterministic readiness suggestions.
Oura data is never sent to the AI Coach or to any AI model, regardless of the Coach access switch. Any future use of Oura data with AI would use an Oura-authorised method and ask for your consent first.
Retention: Oura-derived summaries and workouts are kept for the 45-day product window and older records are removed automatically. Disconnecting Oura revokes REPPIN's access with Oura and deletes the tokens and all Oura-derived data from REPPIN immediately. You can also request deletion of Oura-derived data at any time at [email protected]; requests are actioned within 72 hours.
Strava
Connecting Strava is optional (in Runs or Wearables). REPPIN reads your list of activities and keeps your runs from the last 90 days (runs, trail runs and virtual runs; other sports are not kept): each run's sport, name, start and end, the time it started where you ran it, distance, moving and elapsed time, pace, climb, heart rate, cadence, calories, the route as Strava recorded it, the splits a kilometre, Strava's best efforts and the device that recorded it — plus Strava's identifier for your athlete account. It is shown to you only, in Runs, and never in Community. Older records are removed automatically, and Strava's limit on how long its data may be kept is kept too: what REPPIN has of a run is read from Strava again within seven days, or removed until it can be (your choice of how much of a run's start and finish its card leaves out is REPPIN's, and stays). Disconnecting Strava, or removing REPPIN in Strava's settings, revokes REPPIN's access and deletes the tokens and all Strava-derived data from REPPIN.
Strava data is never given to the AI Coach, or to any AI: Strava's terms keep its data, and anything worked out from it, out of AI models, so there is no setting that sends it. Not a run, not its figures, and not whether a run Strava recorded did one of your planned runs.
A run's share card is made on your device. What it shows — the route with as much of the start and finish left off as you choose, and the figures — leaves your device only if you share or save the image.
Planned runs and maps
The runs you plan in REPPIN — their day, kind, targets and notes, and whether you marked them done and with what — are kept with your account and deleted with it. Coach reads them only while "Schedule" is on in Settings › AI Coach › Coach access, and changes them (plans new ones, moves, edits, deletes or marks them done) only while "Adjust schedule" is on, each time after you approve what it shows you. Maps on your screen in Runs — a run's, a planned route's, the planner's and Coach's — use Stadia Maps' map tiles, which your device asks for from Stadia's servers in the European Union: Stadia receives which squares of the map are drawn (and so the area of a run) and, as any server you contact does, your device's IP address — never your account, your name or the route. The map on a run's share card uses OpenStreetMap's tiles instead, which REPPIN's server fetches for your device: OpenStreetMap receives which squares of the map are drawn, never your account or the route.
A planned run can have a route. When you plan one, the places you type are looked up, and routes found between the points you choose, by REPPIN's server at openrouteservice (run by HeiGIT, from OpenStreetMap's data): it receives the words you type, the point a place is looked up near (to about a kilometre) and the points of the route, never your account, your name or your email address. "Use my location" asks your browser where your device is only when you tap it; that point is used as the route's start and kept only as part of the route you choose. The route's heights come from the Copernicus elevation model, read by REPPIN's server by the area of the map the route crosses. The route you keep — its line, its heights, the names of its start and finish — is kept with the plan and your account, and deleted with them. Coach is told a planned route's name, distance, climb and how much of it is on main roads (with "Schedule" on), never its line; when you ask Coach to find a route, the place names you give are looked up the same way, and the routes it finds stay on your device until you approve one.
Usage analytics
Usage analytics are off until you turn them on — REPPIN asks once, and the choice is yours to change in Settings at any time. When on, REPPIN sends Google Analytics app-usage events — screens opened and feature actions such as finishing a workout, starting a plan, using Coach or sharing a card — plus the app version and any campaign or source labels from the link that opened REPPIN. Events carry no training content. As with any web request, Google Analytics also receives your IP-derived approximate location, browser and device. It never receives your workouts, classes, exercises, weights, reps, notes, history, Coach messages, share links, sign-in codes or payment details.
Payments
Coach credits are bought through PayPal. REPPIN records the order, the amount, PayPal's transaction identifiers and which of REPPIN's pages the order was started on; it never sees or stores your card or bank details.
Low-credits email. This is off unless you turn it on (Settings › AI Coach: “Email me when my credits run low”). While it is on, REPPIN keeps that choice with your account and sends one email to your account's address when a Coach answer leaves you with 2 credits or fewer; it is not sent again until your balance has been above that. Every one of these emails has a link that turns it off, and you can turn it off where you turned it on. The choice is removed when you turn it off or delete your account.
Sharing
Workout Links contain only the workout you chose to share. Short links store that workout on REPPIN's server under a random code until you delete them (Settings › Your data & privacy › Workout links) or delete your account. Deleting a link stops it working; it cannot take back a copy someone has already added to their own workouts. A full-length link — made when a short link cannot be (signed out, offline, past the daily number of short links, or when REPPIN's server cannot make one) — carries the workout inside the link itself and is not stored on REPPIN's server.
Invites
When you invite someone to a workout, REPPIN stores the workout with the invite (in the same form as a Workout Link; it is removed with the invite, and is not listed under Workout links), the date and time, and any name or note you choose to type, under a short code that anyone with the link can open. Guests who tap “I’m in” send the name they type and a random token their device keeps so a repeat tap edits rather than duplicates; those names are shown to everyone with the link. Invites stop working after the day following the workout and are automatically deleted about a week later, or sooner if the host removes them.
Community
Community is optional, for adults, and off until you join it. Joining shares nothing from your history. What REPPIN keeps on its server when you take part:
- Your profile: your handle, display name, bio, link and picture if you add them, whether the profile is private or public, whether it can be found in search, shown in Discover or shown on the web, the version of the Community terms you last accepted, when you joined, and that you confirmed you are 18 or over.
- Who you follow: your follows, follow requests, followers, and the people you blocked or muted.
- What you share: each workout, routine, folder of routines, goal milestone or progress recap you choose to publish, as the preview showed it — for a workout its name and date, the exercises, sets, weights, reps and times you performed, and its result if it was a race or benchmark; for a goal milestone only its title, whether it is achieved and, if you chose, its progress; for a progress recap its period and the figures it showed, with the records and workout names if you chose them — and each post of your own: the words you write, with the date you posted it. Each is kept with your caption, the audience you picked, whether you put it on the web, the topics you filed it under and any photos or video you added. Your private notes, effort ratings, wearable data, calendar, Coach conversations and progress photos are never included.
- Figures for comparisons: from each workout you share, REPPIN works out the figures comparisons and friend leaderboards use (for example, the heaviest set of a catalogue exercise, or a benchmark's score), and keeps them with the post.
- What you do in Community: your likes and comments, the people you mention, the posts you hid from Discover, the topics you chose for it, whether you turned on comparisons and friend leaderboards, the notifications Community sends you and your notification choices, and a short record of each change you make (kept so that a change sent twice, for example on a poor connection, is made only once).
- Chat and messages: what you send in Chat and in direct and group conversations — the words, photos, voice notes, videos, polls and GIF links, with when each was sent and edited — your reactions and poll votes; the conversations you are in, how far you have read each, what you cleared or muted, and the message requests you sent or answered; when you were last active (unless you turn that off in Community settings); and, if REPPIN made you staff, that you are, and any time you were kept out of Chat or messages.
- Reports, moderation and appeals: as described under AI Coach for reports; when REPPIN moderates something, a record of what was done and why; and any appeal you make. A moderator reviewing a report or an appeal sees the profile, post, comment or message it is about as it is at that time, including its photos, voice note and video, and nothing else of yours. A direct or group conversation is private: a moderator sees a message from one only when someone in it reports that message. REPPIN's moderators and staff can see Chat.
Who sees it. What you share is shown only to the audience you choose: your approved followers, or, on a public profile, every signed-in Community member. A private profile shows only your picture, name and handle to members you have not approved. If you turn on Discover, your public posts can be shown to members who chose a topic you filed them under. If you turn on comparisons or friend leaderboards, members who turned them on too can see your shared results beside theirs or ranked with them, only from posts they can already see. Nothing in Community is shown to people who are not signed in or to search engines unless you show your public profile on the web: then your name, picture, bio and link, and only the posts you chose to put on the web, can be seen by anyone with the link, by search engines and by link previews, which may keep copies REPPIN cannot recall. People who can see a post can copy a shared workout into their own workouts, and can save or screenshot what they see; removing a post cannot take those back.
Chat and messages. What you send in Chat is shown to everyone in Community who can use Chat; what you send in a direct or group conversation, to the people in it. When you have seen a message, the person who sent it can see that you have, and — unless either of you turns it off — the people you have direct conversations with (ones you started or accepted) see when you were last active. Blocking someone closes your direct conversation and hides each of you from the other in Chat and in groups. Photos in messages are handled as photos in posts (below); a voice note is recorded on your device only while you hold the microphone button, stored as the sound file it is, never transcribed, and played only to the people in the conversation; a video in a message goes to Cloudflare Stream, as one in a post does. When you look for a GIF, the words you search with go to KLIPY through REPPIN's server, with a code that stays the same for your account but does not name you (KLIPY uses it to tailor and count its results); the GIFs it suggests, and a GIF someone sends, are shown from KLIPY's servers, which then receive the ordinary details of loading an image — your device's IP address and browser — as any website you load an image from does. While a conversation is open, the app keeps a connection to REPPIN's server that says only when something in it changed, never what. Messages are never sent to the AI Coach or any AI model, and never used for advertising.
Photos and videos. A photo you add is resized and re-encoded on your device and again on REPPIN's server, which removes its location and other hidden details. It is stored privately with Cloudflare and shown only through REPPIN to people allowed to see it. A video you add goes from your device straight to Cloudflare Stream, which stores it for REPPIN and plays it only through a link REPPIN gives, for an hour at a time, to people allowed to see the post; a link already given cannot be withdrawn before its hour is up. Your progress photos stay on your device and are never part of Community.
Not used for anything else. Community content is never sent to the AI Coach or any AI model, with one exception you start yourself: Adapt with Coach puts a routine you are looking at, and what you ask for, into Coach's message box, and it is sent to Coach only when you send it, as any Coach question is. It is never used for advertising, and never added to your training backup. Usage analytics, if you turned them on, record that a Community screen was opened, never who or what was on it.
How long it is kept. Your profile and posts are kept until you remove them, leave Community or delete your account. Something you remove stops being shown at once, and its photos are deleted from storage within a day. Something a moderator removes also stops being shown at once; it is kept, unseen, for 90 days so that an appeal can restore it, and then deleted. A photo or video you uploaded but never posted is deleted after 24 hours; a video you remove, or that goes with its post, is deleted from Cloudflare Stream within a day. The record of each change is kept for 30 days and notifications for 90 days. A message is kept until you delete it, leave Community or delete your account; one you delete is gone at once, and the marker that it was deleted goes after 30 days. A group conversation closes for everyone in it, with every message in it, when the person who started it deletes it, leaves Community or deletes their account. A message a moderator removes stops being shown at once and loses its words, photo, voice note or video after 90 days unless an appeal is waiting. A photo or voice note you uploaded but never sent is deleted after 24 hours, a direct conversation started but never used after a week, and when you were last active after 30 days. Reports follow the periods given under AI Coach; an appeal's words are removed 90 days after it is decided, and moderation records a year after they close. When you leave Community or change your handle, your old handle is held for you for 90 days so nobody else can take it. To stop old requests from bringing anything back, REPPIN keeps a record without any content — that a post was removed, or the state of a follow or block — for as long as your account exists.
Your choices. You can pause Community, which hides your profile, posts and messages, or leave it, which removes your profile, posts, comments, likes, photos and videos, the words of your messages and everything they carried, and your reactions and votes; in conversations you are then shown as having left. You can turn off showing when you were last active in Community settings, and switch each kind of message notification off in Settings › Notifications. You can download a copy of your Community data, the messages you wrote among it, at any time from Community settings. The Community terms say what you agree to when you join.
Deleting your account
Settings › Account › Delete account removes your backups, credits, shared links, invites, wearable data, Strava runs and planned runs, the Google sign-in linked to it and everything you have in Community from REPPIN's servers. On the device you delete from, your training stays; that account’s Coach conversation, Coach settings and progress photos are removed from it, and the app first offers to export the photos it shows. If you no longer have the app, you can delete your account here with a code sent to your email address; that leaves your devices as they are. Settings › Your data & privacy lets you clear history separately. Records of past payments are kept, under an opaque identifier, as required for refunds and accounting. Deletion is refused while a payment on the account has not finished.
Who else sees your data
REPPIN does not sell your data and does not share it for advertising. It is passed to these services only to do the thing you asked for:
- Anthropic — your AI Coach messages, and the workout, calendar or history details Coach needs to answer them. Only when you use Coach.
- PayPal — payment details, when you buy Coach credits. REPPIN never sees your card number.
- Your wearable provider (WHOOP, Oura, or Fitbit and Pixel Watch through Google Health) — only after you connect one, to authorise access and retrieve the daily summaries and recorded workouts or activities described above. REPPIN also receives the provider account identifier needed to maintain that connection.
- Strava — only after you connect it, to authorise access and retrieve your activities and runs as described above, with the athlete identifier needed to maintain the connection.
- Stadia Maps — the map squares drawn on your screen in Runs, asked for by your device from Stadia's servers in the European Union, so Stadia sees your device's IP address; nothing that names you is sent, and not the route.
- OpenStreetMap — requests for the map squares of a run's share card, made by REPPIN's server; your device does not contact OpenStreetMap, and nothing that names you is sent.
- openrouteservice (HeiGIT) — the places you type and the points of a route, when you plan a route for a run, sent by REPPIN's server with nothing that names you.
- Copernicus elevation data (held openly on Amazon Web Services) — the parts of the elevation map a planned route crosses, read by REPPIN's server; nothing about you is sent.
- Google sign-in — only if you use Continue with Google: Google shows its own sign-in, learns that you are signing in to REPPIN, and gives REPPIN the details described under What REPPIN stores. Google’s own privacy policy applies to your Google account. While the sign-in screen is open, Google’s button is loaded from Google.
- Resend — receives your email address and the sign-in code email so it can deliver the code you requested, including when you use email verification to delete your account; and the low-credits email, if you have turned it on.
- Your browser or phone's push service (for example Google or Apple) — delivers notifications when you enable them, as described in the Notifications section above.
- Cloudflare — hosts REPPIN's server and database, in the ordinary way a website is hosted, stores and resizes the photos you add in Community, stores the voice notes you send, keeps the live connection of an open conversation, and (Cloudflare Stream) stores and plays the videos you add.
- KLIPY — the words you search for GIFs with, sent by REPPIN's server with a code that does not name you, and, when a GIF is shown on your device, the ordinary details of loading an image from KLIPY's servers. Only if you use GIFs in Chat and messages.
- Other Community members — what you choose to share in Community, and what you send in Chat and messages, as described under Community above.
- Google Analytics — the app-usage events described under Usage analytics, only if you turn them on.
All traffic between the app and REPPIN's server is encrypted in transit (HTTPS).
How long it is kept
Your account's training backup and credit balance are kept with your account and removed when it is deleted; shared workout links are kept until you delete them or the account. Invites expire and are automatically removed on the schedule described above. Wearable data and connection records follow the retention and disconnection rules given for each provider above. A sign-in code expires 10 minutes after it is sent. The ID and address of a Google account you sign in with are kept with your account and removed when it is deleted. Your Coach conversation is kept on your device until you clear it or delete the account; REPPIN's server keeps its own copy of each reply for 7 days only, as described under AI Coach. Records of past payments are kept, under an opaque identifier with no email or name, because refunds, disputes and accounting require them. Community data is kept as described under Community.
You can delete your account at any time: in the app under Settings › Account › Delete account, or without the app at reppin.app/delete-account.html.
Terms
See the Terms of Service.