Privacy policy
Last updated: November 4, 2026
This policy explains which personal data AMRAPture processes, why, on which legal basis and for how long, and which rights you have. AMRAPture is a leaderboard for CrossFit and Hyrox gyms: coaches publish workouts, athletes log their results from their phone, and the results appear on a screen in the gym and on a leaderboard page.
1. Who is responsible
The controller within the meaning of the General Data Protection Regulation (GDPR) is:
Frank Tiersch
Calle Tomás Miller 13, 3
35007 Las Palmas de Gran Canaria
Spain
Email: hello@amrapture.com
Data protection officer: Not appointed (not required by law)
2. Hosting and server logs
AMRAPture runs on servers of Cloudi NextGen S.L. (Clouding.io), Ronda General Mitre 25, 08017 Barcelona, located in Spain (EU). We have concluded a data processing agreement with the provider (Art. 28 GDPR).
Every time you open a page, the server automatically records technical information that your browser sends: your IP address, the date and time, the page requested, the referring page, your browser and operating system, and the response status. We need this information to deliver the pages, to keep the service secure and stable and to detect and fend off attacks. The legal basis is our legitimate interest in a secure and working service (Art. 6 (1) (f) GDPR). Server logs are deleted after 14 days, unless a specific incident needs to be investigated.
3. Cookies and storage in your browser
We only use cookies that are strictly necessary to provide the service you request. We do not use analytics, advertising or tracking cookies, and we do not load fonts, scripts or other content from third-party servers. That is why we do not ask for cookie consent. The legal basis for storing these cookies is Article 22 (2) of Spanish Law 34/2002 (LSSI-CE); the processing of the data in them is based on Art. 6 (1) (b) and (f) GDPR.
| Cookie | Purpose | Lifetime |
|---|---|---|
| amrapture-session | Keeps you logged in during a visit, remembers a guest's logged results on this device, protects forms | 2 hours after your last request |
| XSRF-TOKEN | Protects forms against cross-site request forgery | 2 hours after your last request |
| remember_web_… | Set when you log in or create an account: keeps you logged in on this device | Up to 400 days, or until you log out |
| locale | The language you picked on a public page, or the language of the last AMRAPture page you opened (e.g. the Spanish version), so the next pages show the same | Up to 400 days |
| tv_device | Only on a TV connected to a gym's screen: tells us which screen it shows | Up to 400 days, or until the gym disconnects the TV |
Pages you are logged in to also keep a random key in your browser's session storage. It encrypts the browser history of those pages, so that after you log out, the back button can't show them again. It is deleted when you close the browser tab.
While you log a workout, your browser keeps the scores you haven't sent yet in its local storage on this device, so they survive a reload. Nothing of them reaches us before you send them; they are deleted once sent, or a day after the workout closes for logging.
In the app. The AMRAPture app for Android shows these same pages, with the same cookies and storage. In addition, it keeps two markers in its storage on your phone: whether push notifications were turned on on this phone, and whether you already answered the app's offer to turn them on there, so it doesn't ask again. Nothing of them is sent to us, and they are deleted when you uninstall the app or clear its data. The app also contains Google's Firebase Cloud Messaging; it only starts once you turn on push notifications on a phone, and stops again, its device token deleted, when you turn them off or log out there (section 5).
Visitor statistics. On our own website, meaning the home page and these legal pages (not in the app, on leaderboards or on gym screens), we count visits with Umami, an open-source statistics tool that we run ourselves at umami.sustainablyproductive.com, so the data is not passed on to anyone. Umami sets no cookies and stores nothing in your browser. It records the page you open, the page you came from, your browser, operating system, type of device and screen size, your language, and the country and region derived from your IP address. Your IP address itself is not stored: to tell visits apart, Umami derives an identifier from it that changes every month and cannot be traced back to you. We only use these statistics to see how our website is used and to improve it. The legal basis is our legitimate interest in that (Art. 6 (1) (f) GDPR).
4. Your account
To log results as a member of a gym, you create an account through your gym's join link. We process your name, email address, password (stored only as a secure hash), your language, your gender (female or male) if you give it, whether your new results start as private (section 5), the day you last saw yesterday's highlight (section 5), the day you last saw your streak message after logging (section 5), the gym you joined, whether your email address is confirmed and, if you upload one, your profile photo (stored resized and without the details a phone or camera adds to a picture, such as where it was taken). We use this data to provide your account, to log you in, to show your results and to send you emails about your account (for example to confirm your email address or reset your password). Your gender is optional and is used only to place you in the right ranking where a track ranks women and men separately; you can set, change or remove it in your profile. The legal basis is the performance of the contract of use (Art. 6 (1) (b) GDPR): it is needed to place you in the ranking you chose to take part in. It is not special-category data under Art. 9 GDPR.
If you add a passkey to log in without your password, your device creates a key pair. We only store its public key, the name you give it, the type of device or password manager that holds it (an anonymous model identifier), an anonymous user ID stored with it on your device, and when it was added and last used. Your fingerprint, face or device PIN never leave your device: we never receive them. You can remove a passkey in your profile at any time; it is also deleted with your account.
If you sign up or log in with Google, you are sent to Google, which asks you to agree and then tells us your Google account ID, your email address, whether Google has verified it, and your name. We store the Google account ID and that email address, to recognise you when you log in with Google again, and use the name only as the suggestion for your account's name. We do not receive your Google password or your profile photo. An account created with Google may have no password; you can set one in your profile. You can disconnect Google in your profile, and the connection is deleted with your account. At Google, Google's own privacy policy applies (policies.google.com/privacy). Google is not our processor: it decides itself how it handles the sign-in.
The legal basis is the performance of the contract of use with you (Art. 6 (1) (b) GDPR). We keep your account until it is deleted. You can delete it yourself at any time in your profile, and your gym's staff can remove it; we do not delete inactive accounts automatically.
5. Results and leaderboards
When you log a result, we store your score for each part of the workout, your category (Rx or Scaled), the team you joined, whether the result is private, the time you logged it and changes made later by you or by your gym's staff. A result also stores the group it was logged in (women, men, or mixed for a team): your gender if you saved one, or the group you or your team picked. On days when a track ranks women and men separately, the leaderboards and screens list your result in that group, so others can tell from the group you are listed in. On other days the group is stored with the result when you have saved a gender (so a track can switch to separate rankings later without asking you again), but it is never shown.
Showing results is the purpose of AMRAPture. Unless you keep a result private (see below), your name, your profile photo (if you uploaded one), your scores and your ranking are therefore visible:
- on the screens in your gym,
- on your gym's public leaderboard page, which anyone with the link can open,
- to the other athletes of your gym and to your gym's staff,
- and, when you log at another gym as a drop-in, in the same way at that gym.
Logging a result is voluntary. The legal basis is the performance of the contract of use (Art. 6 (1) (b) GDPR). If you do not want to appear on a leaderboard, keep your results private (team results stay public) or do not log a result; you can delete your own individual results yourself while the workout is still open for results; after that, or for a team result, ask your gym's staff or us to remove it.
Private results. When you log an individual result (not a team result), you can choose to keep it private; in your profile you choose whether new results start as private. A private result is only seen by you, on your own pages; not by the screens, the leaderboards, other athletes or your gym's staff. It gets no place, so it does not change anyone's ranking. You can change whether a result is private while its workout is still open for results; after that it stays as it is. Team results are always public, since the team shares one score. Your gym's staff can see that a part of a workout has results (its scoring can then no longer be changed), and when they delete a workout or a track they are told how many results go with it, private ones included, but never whose they are or what they are. You can delete a private result yourself while its workout is open for results; after that, ask us. The legal basis is the performance of the contract of use (Art. 6 (1) (b) GDPR).
Private notes. You can add a short note to any of your own results, for example the weights you used, how you scaled it or how it felt (at most 500 characters). Writing one is optional. Only you see your notes: not your gym's staff, not your teammates or other athletes, not the screens or the leaderboards, and they are never sent to AI services. A note may contain health details if you choose to write them, for example about an injury; we store notes encrypted. You can change or delete a note at any time, also after its workout has closed for results. A note is deleted together with its result (also when your gym's staff delete the result, or when the workout, the track or the gym is deleted) and with your account. The legal basis is the performance of the contract of use (Art. 6 (1) (b) GDPR); for any health details you write, your explicit consent (Art. 9 (2) (a) GDPR), which you withdraw by changing or deleting the note.
Fist bumps. Logged in, as a member or staff of the gym or with a result on that workout, you can give a "fist bump" to another athlete's public result on the leaderboard, or to a team's result; giving one is optional, and you can take it back. We store who gave a fist bump, to which result or team, and when. How many fist bumps a result received is shown with it on the leaderboard to everyone who can see it, also without an account; who gave them (their name and profile photo, as on the leaderboards) is only shown to people logged in with an account. On your gym's screens, if your gym turns this on, a fist briefly appears beside a result that receives a fist bump; the screens show no numbers and no names. Guests cannot give fist bumps, and a guest's own result receives none (a team they are on can). A gym can switch fist bumps off for a track: they are then hidden, not deleted. Only you see the fist bumps of a private result. The legal basis is the performance of the contract of use (Art. 6 (1) (b) GDPR).
Notifications. When your result, or your team's, receives a fist bump, we keep a notification for you in your account: which result it is about, which athletes it has already told you about, and whether you have read it; when you open it, it shows who gave the fist bumps. Only you see your notifications. They are deleted automatically 90 days after their last activity, or soon after none of their fist bumps is left, and with your account. The legal basis is the performance of the contract of use (Art. 6 (1) (b) GDPR).
Push notifications in the app. In the AMRAPture app (not on the website) you can also receive your notifications as push notifications on your phone. They are optional and off until you turn them on for a phone, in the app's settings or when the app offers it; Android asks you for permission first. When you turn them on, Google's Firebase Cloud Messaging gives the app an address for your phone (a device token), and we store it with your account, together with the type of phone (Android), the language the pushes are written in and when the app last used it. When someone gives your result or your team a new fist bump, we then send a push to that phone: it names the people who gave the fist bumps, as the leaderboard shows them, and the part of the workout. It goes from us through Google (Firebase Cloud Messaging; Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA) to your phone, and may be shown on your lock screen unless your phone hides the content of notifications. In the app's settings you choose which kinds of push notifications you want; this choice applies to all your phones and is stored with your account. If you decline the app's offer to turn them on ("Not now"), we store when, so that it isn't offered again. A phone's device token is deleted, by us and in Firebase on the phone, when you turn its push notifications off or log out on it; we also delete it when you delete your account, when Firebase tells us it is no longer valid (for example because the app was uninstalled), and after 60 days without the app being used on it. You can turn push notifications off at any time, in the app's settings or in your phone's settings.
Google processes this data for us as our processor, under its data processing terms for Firebase, only to deliver the push notifications. Google may process it in the USA; transfers are based on the EU-U.S. Data Privacy Framework, under which Google LLC is certified, and otherwise on the EU standard contractual clauses (Art. 46 (2) (c) GDPR). The legal basis is the performance of the contract of use, for this feature you choose to turn on (Art. 6 (1) (b) GDPR); storing the device token on your phone is strictly necessary for the service you request (Article 22 (2) LSSI-CE).
Yesterday's highlight. When you open the app, it may show you, once a day, something about your results of the day before at that gym. For now that is your place when it was one of the top three of its group in a part with at least four athletes, shown with the names and profile photos of the others on that podium, as on the leaderboards. It shows no scores and nothing of private results. To show it only once a day, we store on your account the day you last saw it; it is replaced each time and deleted with your account. The legal basis is the performance of the contract of use (Art. 6 (1) (b) GDPR).
Your streak. After you log a workout, the "Good work" screen may, on some days, tell you about your weekly streak: how many weeks in a row you trained on at least your gym's goal number of days. It is worked out from your own results at your gym, private ones included, and shown only to you. To show it at most once a day, we store on your account the day you last saw it; it is replaced each time and deleted with your account. The legal basis is the performance of the contract of use (Art. 6 (1) (b) GDPR).
When an account is deleted, its results stay on the leaderboards without a name or photo (shown as "Former member"), so that the rankings of the other athletes do not change; private results stay private. These results can no longer be linked to you. They keep the fist bumps they received; the fist bumps the account gave are deleted, and so are its notifications and its private notes. When a result is deleted, its fist bumps and notifications go with it; a team's go when the team's last result is deleted.
In a team workout, the teammate who logs the team's score may also enter the names of team members who don't log themselves. We then store that name with the team's score, and it is shown on the leaderboards as described above, without a photo. Until the workout closes for changes, the person named can take the result as their own, with their account or as a guest; otherwise it stays under the name entered. The legal basis is the legitimate interest of the team and the gym in showing complete team results (Art. 6 (1) (f) GDPR). To have your name removed, ask your gym's staff or us. When a member of a team changes the team's score, we keep who changed it and the score before, so your gym's staff can undo a wrong change; staff see this in the gym's admin area, never on the leaderboards.
So that teammates can add you to a team's result, members of your gym who log a team score can find you by name: they see your name and your profile photo, and whether you already logged that part and with whom. Your email address is never shown. They can then add your account to their team, with the team's score; you see on your result who added you, and you can leave the team or correct its score. If your new results start as private, you do not appear in the search and others can't add you; you can still join a team yourself. The legal basis is the legitimate interest of the team and the gym in showing complete team results (Art. 6 (1) (f) GDPR).
6. Logging as a guest
On tracks where the gym allows it, visitors can log a result without an account, from the QR code on the gym's screen or a link to the gym's workout of the day. We store the name you enter and your scores and, on tracks that rank women and men separately, the group you pick (female or male); it is stored with your result and, if you create an account afterwards, copied to it. Your name is shown on the leaderboards with a "Guest" label, in the same way as described in section 5. Your browser's session cookie remembers which guest results you logged on this device, so that you can change them during that visit, log another person's result or create an account; we do not ask for an email address. With the same QR code, guests can also only rate the workout (section 7), without entering a name.
The legal basis is the performance of the contract of use (Art. 6 (1) (b) GDPR). If you create an account afterwards, we can move your guest results to the new account. To have guest results removed, ask the gym's staff or us.
7. Workout ratings
After a workout you can rate it with 1 to 5 stars, with or without logging a result. Rating is optional. We store the rating together with your account (or, as a guest, with the guest's random identifier), only so that you can change it later and so that each person counts once. We do not store when you rated.
Your gym's staff only see how many ratings a workout received, the average and how the ratings are spread over 1 to 5 stars, and only once a workout has at least 3 ratings. Nobody, including gym staff, is shown who gave which rating. Ratings do not appear on the screens or leaderboards.
The legal basis is our and your gym's legitimate interest in improving its training programme (Art. 6 (1) (f) GDPR). Ratings are kept as long as the workout. When an account is deleted, its ratings stay in the averages but are no longer linked to it.
8. Gym staff
For coaches and gym managers we process name, email address, password hash, language, the gym they manage and their role, as well as the changes they make (workouts, result corrections). Gym staff can also see and correct the gender of their gym's athletes. When a gym manager is invited, we store the name, email address and language of the invitation and a hash of the invitation link, which is valid for 7 days. The legal basis is the performance of the contract with the gym and with the staff member (Art. 6 (1) (b) GDPR).
9. Emails
We send emails that are necessary for using the service: confirming your email address, resetting your password, invitations and, for administrators, internal summaries. These emails are sent through Mailtrap (Railsware Products Studio LLC, 117 E Colorado Blvd, Suite 600, Pasadena, CA 91105, USA), with whom we have concluded a data processing agreement. The provider is located in the USA; transfers are based on the EU-U.S. Data Privacy Framework, under which it is certified, and otherwise on the EU standard contractual clauses (Art. 46 (2) (c) GDPR). The legal basis is Art. 6 (1) (b) GDPR. We do not send newsletters or advertising.
10. Screens in the gym and live updates
A gym connects its TVs to AMRAPture with a one-time code. For each connected TV we store a random device key (only as a hash), the type of device derived from the browser identification, the screen size and when it was last online. This lets the TV show the right leaderboard and lets the gym see which screens are working. The legal basis is the performance of the contract with the gym (Art. 6 (1) (b) GDPR).
Pages update live through a connection to our own server. These updates only say that something changed; no personal data is sent over this connection.
Gyms can show QR codes on their screens. Such a code opens a short link on AMRAPture (/go/…) that counts how often it was opened per hour and then forwards you to the page the gym chose. We store only this hourly count, nothing about you or your device. The page you land on is the responsibility of its operator, and its privacy policy applies there.
11. Artificial intelligence
Coaches can let AI split a workout text into separately scored parts and recognise the exercises in it. In addition, every workout text that is saved is laid out for the gym's screens automatically: an AI says which lines are headings, movements or notes, without changing the text. For this, the workout text and the exercise names in it are sent to:
- Anthropic PBC, San Francisco, USA (text analysis and layout of the workout; the help chat, below),
- TypeSafe AI, Inc., 255 California St, Suite 1300, San Francisco, CA 94117, USA (matching exercise names to our exercise catalogue).
When a workout text is split into parts, optional notes for the AI may be sent to Anthropic along with it: hints for the gym, a track or a workout, written by the gym's staff or by us, e.g. "we use lbs". These notes are never shown to athletes.
Gym staff can ask a help chat in the gym's admin area how to do something in AMRAPture. Their question is sent to Anthropic together with our help pages, their role in the gym (owner, head coach or coach), the admin page they are on and, for a follow-up, their last few questions and answers in that chat; the answer comes back from there. We keep the questions and answers, with the gym and the staff member who asked, for 90 days, to improve the app and its help pages; only we see them. Questions are not meant to contain personal data. The legal basis is our legitimate interest and that of the gyms in helping their staff use AMRAPture (Art. 6 (1) (f) GDPR).
Workout texts and these notes describe exercises, weights and times. They are not meant to contain personal data, and coaches should not enter any. Results, private notes, athlete names and email addresses are never sent to AI services. To keep track of costs we record which gym and which staff member started an AI request; this information stays with us. The legal basis is our legitimate interest and that of the gyms in creating and showing workouts efficiently (Art. 6 (1) (f) GDPR).
Both services are located in the USA. Transfers are based on the EU-U.S. Data Privacy Framework, where the recipient is certified under it, and otherwise on the EU standard contractual clauses (Art. 46 (2) (c) GDPR).
AI is only used for workouts and for the staff's help chat. We do not use it to make decisions about people, and there is no automated decision-making or profiling within the meaning of Art. 22 GDPR. Rankings are calculated from the scores and do not have any legal effect on you.
12. Recipients
We only pass on personal data where this is necessary for the purposes described above: to our hosting provider, our email provider, the AI services named in section 11 and, if you turn on push notifications in the app, Google (Firebase Cloud Messaging; Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA) (section 5), all bound by contract. If you sign up or log in with Google, Google (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland) learns that you use AMRAPture (see section 4). Your gym's staff see the data of their gym's athletes, except private results and private notes (section 5). We do not sell personal data and do not pass it on for advertising.
13. How long we keep data
We delete personal data as soon as it is no longer needed for the purposes described here, unless statutory retention obligations apply. Backups are overwritten after 30 days; deleted data may remain in them until then.
14. Your rights
Under the GDPR you have the right to:
- access the personal data we hold about you (Art. 15),
- have incorrect data corrected (Art. 16),
- have your data deleted (Art. 17),
- restrict processing (Art. 18),
- receive your data in a common, machine-readable format (Art. 20),
- withdraw any consent you have given, with effect for the future (Art. 7 (3)).
Right to object (Art. 21 GDPR): Where we process your data on the basis of our legitimate interests (Art. 6 (1) (f) GDPR), you have the right to object at any time for reasons arising from your particular situation. We will then no longer process the data unless we can demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing serves to establish, exercise or defend legal claims.
To exercise your rights, write to hello@amrapture.com. You also have the right to lodge a complaint with a data protection supervisory authority, in particular in the member state of your residence, your place of work or the place of the alleged infringement. The authority responsible for us is: the Agencia Española de Protección de Datos (AEPD), C/ Jorge Juan 6, 28001 Madrid, Spain, www.aepd.es.
15. Security
All connections to AMRAPture are encrypted (TLS). Passwords are stored only as secure hashes, and invitation links and device keys only as hashes. Access to the data is limited to the people who need it.
16. Children
AMRAPture is meant for people aged 16 and over. Gyms that let younger athletes use it are responsible for obtaining the consent of a parent or guardian where this is required.
17. Changes to this policy
We update this policy when AMRAPture changes or the law requires it. The current version is always available on this page.