Last updated
Privacy policy
Who we are
One Rep Closer is run by Graham Bond, a sole trader in the United Kingdom, trading as One Rep Closer. For UK GDPR, we are the controller of the personal data described on this page. The publisher named on both app stores is Graham Bond, trading as One Rep Closer.
Write to privacy@onerepcloser.fit. Email is how we work; we do not publish a postal address.
The short version
We collect the little the app needs to do its job and nothing beyond it. We do not sell your data, we do not share it so that somebody else can market to you, we do not show ads, and we do not build a profile of you. This website sets no cookies, except one that holds a random number if you vote on the roadmap. That one only lets your vote count once, which is why you were not asked about cookies.
This website
No cookies, unless you vote. The site sets no cookies, with one exception: voting on the roadmap sets a single cookie, described under Feedback below. The fonts are served from our own domain, so loading a page sends no request to Google Fonts or any other font service.
If you arrive through a tagged link, such as one of our ads, your browser keeps that short tag for the visit so we can tell which link led to an app store tap. It is not sent to anyone until you tap a store badge, and it is cleared when you close the tab.
Page counts. We use Umami to see how many people read each page, which site or link brought them here, and whether they joined the waitlist, used one of our timers or tapped a link to an app store. Umami sets no cookies and stores nothing in your browser. It uses your IP address only to work out your country and does not store it. It records the page, the site you came from, your browser, operating system, device type, screen size and language. It cannot follow you to other sites, and we get counts, not people. If your browser sends a Do Not Track signal, nothing is counted.
Our ads. We advertise on Google Search. Our ads link to this site with a short campaign tag
in the address, such as ?utm_source=gads-hyrox, so our page counts can tell which ad brought a
visit. There is no Google code on this site; Google sees only that its ad was clicked, as it would
for any ad.
Server logs. The site is hosted by Cloudflare. Like any web server, Cloudflare records the requests it serves — the IP address the request came from, the time, the page, the browser’s user-agent — to deliver the site and keep it from being abused. We do not use those records to work out who you are.
The waitlist. If you give us your email address, it goes to Buttondown, who run the list for us. The IP address the form was submitted from goes with it: Buttondown uses it to filter out bot sign-ups. Buttondown then emails you to confirm you meant it, and you are only added if you click that link. We use the list for one thing, telling you the app is out. Every email has an unsubscribe link, and you can ask us to remove you at any time.
The app
When you are signed out
Everything you log is written to a database on the phone itself. Your templates, your sessions, your sets, your records, your settings — all of it is on the device, and none of it is sent to us. The app works with the phone in aeroplane mode, and it works if we disappear.
Three things still use the network, and none of them carries your training with it:
- Checking whether Premium has been bought on this device. That check goes to RevenueCat, who run subscriptions for us, under an anonymous identifier they generate for the install. It carries your purchase history and basic device information, set out under Subscriptions below.
- Opening a template somebody shared with you. The code you type goes to our server, which sends back the template it stands for. No account and nothing about your training goes with it.
- Usage statistics, unless you turn them off. They are described under Usage statistics below, and they never carry your training.
The app asks for no device permissions. It does not use the camera, your photos, your location, your contacts or your microphone, and it does not connect to Apple Health or Google Fit. It has no fields for medical information — notes are free text, so please keep anything medical out of them.
When you sign in
You sign in with Apple or with Google. There is no password to create and none for us to lose. From the provider we receive your email address and, if your account has one to give, your name. Apple sends a name on the first sign-in only, so that is the moment we keep it. If you use Apple’s Hide My Email, the relay address is the only address we ever see. The sign-in token that keeps you signed in is held in the phone’s own keychain.
Signing in makes the workouts already on the phone part of your account, and they are included in the backup from then on.
The backup
Backup is why an account exists, and it is free. Once you are signed in, the app copies to our server: your templates, the sessions you have logged and the sets inside them, your personal records, the exercises you created yourself, your app settings, and your account row — which holds your email address, your display name, your unit preferences (kilograms today) and whether Premium is active. It runs on its own when you finish a workout and when you leave the app. There is no button to press and nothing to remember.
The database is hosted by Supabase and is configured so that only your own account can read your own rows. Like any server, it also records the requests the app makes to it, including the IP address they come from. The first time you sign in on a new phone, the restore runs by itself.
Sharing a template
If you send somebody a template, the app publishes that template under an eight-character code: its name, its notes, its blocks and targets, and any exercises you created that it uses. The name on your account at that moment is published with it, so the person opening it can see who sent it. Your email address is never published.
Anyone holding the code can open it, including people with no account at all. Treat a shared template as public, and keep anything private out of one. There is not yet a way to withdraw a code from inside the app — email us and we will remove it.
Subscriptions
Premium is sold by Apple and Google, not by us. RevenueCat sits between the stores and the app and tells it whether Premium is active, which plan it is, and when the period ends. When you are signed in, your account id is what RevenueCat knows you by, so Premium follows you to a new phone. When you are signed out, they know the install by an anonymous identifier instead.
RevenueCat’s own privacy notice sets out what it receives from an app like ours, and it is more than the answer it gives back. It gets your purchase history in the form the store provides it — an Apple receipt file or a Google purchase token — the last time the app was used, and technical information about the device, which their notice describes as device type and operating system. Their guidance for the App Store privacy label adds your locale and currency code, and says they do not collect health or fitness data, precise location, or device diagnostics.
We never see your card, your bank or your store account.
Feedback
Send feedback in the Profile tab opens a form hosted by Tally. It carries your platform and the app’s version number with it, so we know which build you are on. The message is what you type. The email address on that form is optional, and we only use it to reply. Because the form opens in a web browser, Tally also receives the ordinary details of that request, including the IP address it comes from.
The roadmap. The roadmap page on this website lets you vote for the features you want. When you vote, the site sets one cookie holding a random number, so that you can vote once and take the vote back later. It is only sent back to the voting service, never to anyone else, and it is not used for anything else. What we keep is an unreadable hash of that number and which items it voted for: not your name, not your email, and not your IP address. Your IP address is used for a moment to slow down abuse, and is not stored. Cloudflare Turnstile checks that the vote comes from a person rather than a script. Suggest an idea opens the same Tally form as the app.
Usage statistics
The app tells us which of its features are used, so we know what to improve. For example, it tells us that a workout was started or finished, which kinds of block it had and roughly how long it took, that a template was saved, that the Premium screen was opened and whether a purchase went through, that the Progress tab was viewed, or that the app was opened. Numbers are sent as ranges, such as “2 to 4 blocks”, never exact values.
Each of these events carries a random number the app creates when it is installed, the app’s version, your phone’s make, model and operating system, and whether you are signed in and on the free or Premium plan. It never carries your name, your email address, your account, your exercises, weights, reps, notes or template names, and we never connect it to your account.
PostHog processes these events for us in the EU. Your IP address reaches PostHog with each request, as it would for any server, but PostHog is set to discard it, and it is not used to work out where you are. The events are kept for one year.
They are on by default. You can turn them off at any time in Profile → Share anonymous usage stats, and nothing more is sent. That choice stays on the phone. Turning it off, signing out and deleting your account each give the app a new random number, so nothing links what came before with what comes after.
Who processes data for us
| Service | What it receives | Why |
|---|---|---|
| Buttondown | Your waitlist email address, and the IP address the sign-up came from | Runs the waitlist and its confirmation and unsubscribe emails |
| Supabase | Your account and everything in your backup; a shared template and the sender name on it; and the technical details of the requests the app makes, including your IP address | Hosts the database behind accounts, backup and sharing |
| RevenueCat | Your account id, or an anonymous identifier when you are signed out; your purchase history as an Apple receipt or Google purchase token; the last time the app was used; and basic device information — device type, operating system, locale and currency | Tells the app whether Premium is active |
| Apple | Your sign-in, and everything to do with paying on iOS | Sign in with Apple, and App Store billing |
| Your sign-in, and everything to do with paying on Android | Sign in with Google, and Google Play billing | |
| Tally | What you write in the feedback form, your platform and app version, an email address if you give one, and the details of the browser request that opens the form, including your IP address | Hosts the in-app feedback form |
| Cloudflare | The requests this website serves, the email you send to our addresses, votes on the roadmap, and the Turnstile check that comes with them | Hosts and protects the website, stores roadmap votes, and forwards our email to us |
| PostHog | Anonymous usage events: what was used, a random number for the install, the app version, and your phone’s make, model and operating system. Your IP address arrives with the request and is discarded | Tells us which features of the app are used, so we can improve them |
| Umami | Cookieless page counts: the page, the site you came from, your browser, operating system, device type, screen size, language and country. Your IP address is used to find the country and is not stored | Counts visits to this website |
Some of these providers are outside the United Kingdom and process data abroad. Where your personal data leaves the UK, we rely on the safeguards each of them publishes for international transfers; their privacy notices, linked above, set out what those safeguards are.
Our legal bases
- Performing a contract with you — your account, your backup, sharing a template you chose to share, and your subscription.
- Your consent — the waitlist. You give it by confirming the email Buttondown sends, and you withdraw it by unsubscribing or by asking us.
- Our legitimate interests — keeping the service working and secure, counting page views without cookies, counting which app features are used without knowing who uses them, counting interest in features on the roadmap, and answering the messages you send us.
How long we keep things
- Your account and your backup: until you delete your account. Deleting it removes them.
- A shared template: until you ask us to remove the code. We have no automatic expiry yet.
- The waitlist: until you unsubscribe, or until we have finished announcing the launch.
- Feedback, and email you send us: while we still need it to deal with what you wrote, and to keep a record of any request you made about your own data.
- Roadmap votes: deleted when the item is taken off the roadmap, or 12 months after it ships. The cookie in your browser expires after a year, and you can clear it at any time.
- Website logs: held by Cloudflare under their own retention periods. We keep no copy.
- Page counts: held by Umami for six months, then deleted.
- Usage statistics from the app: held by PostHog for one year, then deleted.
Nothing here is kept “just in case”. If a rule above does not cover something, the answer is that we hold it until you ask us to delete it.
Your rights
Under UK GDPR you can ask us for a copy of the personal data we hold about you, ask us to correct it, ask us to delete it, ask us to restrict or stop a particular use of it, ask for it in a portable form, and withdraw consent you have given. Email privacy@onerepcloser.fit and we will answer within one month.
You do not have to ask us to delete your account: Profile → Delete account in the app does it directly. It erases your account and everything we hold on our server, and it leaves every workout on the phone, where the app carries on working signed out.
If you think we have handled your data badly, please tell us first so we can put it right. You also have the right to complain to the Information Commissioner’s Office, the UK’s data protection regulator, at ico.org.uk.
Children
One Rep Closer is not aimed at children. It is a training log for adults, and we do not knowingly collect personal data from anyone under 13. If you believe a child has given us data, email privacy@onerepcloser.fit and we will delete it.
Changes to this policy
When something changes, we update this page and the date at the top of it. If a change matters to you, we will say so here rather than leave you to spot it.