Privacy Policy
Version 2.24 — November 21, 2026
1. Who We Are
Gradescale is operated by:
Thomas Mortelmans (sole trader)
Switzerland
Email: legal@gradescale.fit
A postal contact address is available on request to any user or authority via the email above.
Thomas Mortelmans is the data controller for the personal data described in this policy, for every user wherever they are located. For users in the European Economic Area, the United Kingdom, and Switzerland, that is the controller role as those laws define it.
Gradescale is currently an invitation-only closed beta. An account can only be created with an invitation we issue, which is how we control who is admitted. Invitations are open to athletes in most countries. It is not offered to users in the United States or Canada, and we do not knowingly enrol them. It is also not available in countries whose law requires personal data about their residents to be stored inside that country, because we cannot meet that requirement on our infrastructure. The current list of excluded countries is applied at sign-up.
EEA and UK representative. We have assessed whether a representative must be appointed under Article 27 GDPR and Article 27 UK GDPR, and have documented that assessment. Opening invitations beyond Europe does not change it: the beta remains invitation-only and small-scale, which is the basis on which the Article 27(2) exception applies. We will appoint and name representatives here if and when the processing ceases to fall within that exception, and in any event before the service leaves invitation-only access.
2. What Gradescale Does
Gradescale is a training analytics platform for endurance athletes. It takes the training data you choose to connect or upload and turns it into analysis: fitness and fatigue modelling, workout insights, readiness scores, and personal records. Your data is used to run the service for you. We do not sell it, and we do not use it for advertising.
What we do with your training data. The same thing for every source you connect — Strava, Garmin, Wahoo, Suunto, COROS, Polar, Hammerhead, Withings, intervals.icu — or a file you upload yourself:
- We read the activity and the measurements recorded during it — the session itself (sport, time, duration, distance, elevation) and the series recorded through it, which can include heart rate, power, cadence, pace and position.
- We calculate things from it. Training load and how it accumulates, thresholds such as critical power and critical speed, power and pace curves, how your heart rate responds to effort, how your performance holds up under fatigue, readiness, and personal records.
- We keep those results with the activity so your history can be shown over time and so a new session can be compared against your own past ones.
- We show it back to you as charts, insights and training suggestions, and we send you notifications about your own training if you have asked for them.
- We show it to your coach only if you have one and only after you accept their invitation and give consent, which you can withdraw (Section 12).
Everything above is calculated from your own data, for you. We do not compare you against other athletes, we do not build audience segments, and we do not sell your data, share it with advertisers, or hand it to anyone not named in Section 8. Where this involves health data it happens only with your explicit consent (Section 5); the legal basis for each purpose is in Section 6, and the automated parts are described in Section 15.
3. Where Your Data Comes From
- Training accounts you connect. You can authorise Gradescale to import your activities from services such as Strava, or from other training platforms and devices we support. You control the connection: you can disconnect a provider at any time, either in Gradescale or at the provider. Disconnecting stops further imports; the data we already imported stays in your account until you ask us to delete it or delete your account (Section 11). Strava is different, because you sign in with it. On the website, "Log out everywhere" ends the Strava connection and keeps your Gradescale data. The "Disconnect Strava" button in the Gradescale mobile app signs you out of the app, asks Strava to revoke Gradescale's access and keeps your Gradescale data; the connection ends once Strava confirms. Revoking Gradescale's access in your Strava settings deletes your Gradescale account after a 5-day grace period (see Section 11). Each provider's own privacy policy governs what that provider does.
- Files you upload and information you enter directly (check-ins, goals, planned workouts, settings, your email address).
- Technical data created by using the service (see Section 4).
Connected platforms and devices
What comes in. If you connect Strava, Garmin, Wahoo, Suunto, COROS or Polar, Gradescale receives the activities that platform makes available for your account: the activity record itself (sport, start time, duration, distance, elevation) and the measurement series recorded during it, which can include heart rate, power, cadence, pace and position. This is the same for every provider. Some of it is health data, and we process it only with your explicit consent under Section 5. For Polar, Gradescale reads your training sessions and, while the sleep read described below is switched on, your sleep. It reads no other recovery or all-day data from Polar.
Hammerhead (SRAM). If you connect Hammerhead, we store your encrypted sign-in tokens and your Hammerhead account identifier. Gradescale imports each ride when Hammerhead reports it and, each time you connect or reconnect, your rides from the previous 30 days. For each ride it takes the sport from Hammerhead's record of the ride (or from the recording, when the recording marks the ride as indoor cycling or that record gives no sport Gradescale recognises) and, from the ride's recording file, the start time, the elapsed and moving time, and the distance, elevation gain, heart rate, power, cadence, speed, temperature, altitude and position recorded during it. It does not keep or use the title, description or route map that Hammerhead keeps for the ride, and names the ride after its sport and date. Gradescale does not keep a copy of the ride's file. A ride whose recording Gradescale cannot use, such as one that holds more than one sport, is not imported. If the import of a ride fails for a reason that may pass, Gradescale tries again later, for up to 14 days. It keeps a waiting list for this, on which the rides found when you connect or reconnect also wait for their import. Each entry holds Hammerhead's identifier for the ride, filed under your account, why and when the ride was put on the list, how often and when it was last tried, and when and how it ended; an entry is deleted 30 days after Gradescale stops trying it, or earlier, with the rest of your data, when you withdraw health-data consent or your account is deleted. An entry still waiting is also deleted when you connect a different Hammerhead account, or connect Hammerhead again after disconnecting it. A ride that also reaches Gradescale through another connection is kept once. Rides are imported only while your health-data consent (Section 5) is active. Besides the planned workouts described under "What goes back out", Hammerhead receives only the sign-in exchange when you connect (a signed, single-use code that carries your Gradescale account identifier), requests to renew the sign-in, requests to read your rides, and requests to end the authorisation. If you disconnect, withdraw health consent or delete your account, and for the old account when you connect a different Hammerhead account, we ask Hammerhead to end the authorisation, and we delete our stored connection whether or not that request succeeds. When two Gradescale sign-ins are joined into one account, a Hammerhead connection that is not carried into the joined account is deleted, at the join or when you delete your account, without that request. Rides already imported stay in your account until you ask us to delete them, withdraw your health-data consent or delete your account (Section 11).
Withings. If you connect Withings, we store your encrypted sign-in tokens, your Withings account identifier and the access you granted (body measurements: weight and body composition; Withings groups other measures such as blood pressure and heart rate under the same permission). Of those measures Gradescale reads only your weight and your body fat percentage. The first time it reads them, and again after you disconnect and reconnect, it asks for the previous 180 days; after that, it asks for the readings added or changed since its last completed read began and the six hours before, never sooner than six hours after that read began. It keeps one weight and one body fat value for each day, and does not keep a reading dated more than about 180 days back or one that Withings marks as possibly belonging to someone else. A reading you delete at Withings stays in Gradescale. Weight and body fat are health data (Section 5): Gradescale reads them only while your health-data consent is active in a version that covers recovery and body measurements. Gradescale keeps these values in your account, shows them to you and includes them in your data export (Section 13). Your coach can see them only if you have agreed to share your recovery and body measurements with them (Section 12). Withings gives us no way to end the authorisation, so disconnecting deletes only the connection we store and stops the reads; to revoke access fully, remove Gradescale in your Withings account. Values already read stay in your account until you ask us to delete them, withdraw your health-data consent or delete your account (Section 11).
Polar sleep. Gradescale reads your sleep from Polar only while it has this read switched on. For each night Polar sends, it keeps only when your sleep started and ended, your time asleep (the sum of your light, deep and REM sleep) and Polar's sleep score. It keeps one night for each date: when Polar sends more than one, the longest. Once a read succeeds, it waits a day before the next, and each read keeps at most the 30 most recent nights Polar lists. Nothing else from the night is kept, such as the stage-by-stage record, your heart rate during the night or the device identifier. Sleep is health data (Section 5): Gradescale reads it only while your health-data consent is active in a version that names when your sleep starts and ends. Gradescale keeps these values in your account and includes them in your data export (Section 13). Your coach can see them only if you have agreed to share your recovery and body measurements with them (Section 12). Values already read stay in your account until you ask us to delete them, withdraw your health-data consent or delete your account (Section 11).
Breathing measurements. Some breathing sensors record your breathing rate, the volume of each breath and the volume you breathe per minute in a workout's recording file. Gradescale takes these measurements from the file of a workout that Wahoo sends it, and from a file you upload to one of your activities that has no recording yet. It keeps them with the workout's other recorded measurements and shows them on the workout, to you and to a coach whose invitation you accepted (Section 12). They are health data (Section 5): Gradescale takes them only while your health-data consent is active. They are kept and deleted like the rest of your training data (Sections 10 and 11). Garmin also sends an average breathing rate with some activities, which Gradescale keeps with the rest of the activity record.
What we do with it. Exactly what Section 2 describes, with no exception made for any provider: one purpose, analysing your training. Not for advertising, not sold, not compared against other athletes, and not shown to a coach unless you accept their invitation and consent (Section 12).
What goes back out. This differs by provider, so it is set out per provider rather than in general. Where we send a planned workout, we send the workout only — as set out for each provider below, some or all of its title, date, written description, structure, duration and intensity targets. Those targets are calculated from your own threshold values (for example your functional threshold power or critical pace), so they are derived from your training data. We never send recorded activities, heart-rate or other measurement series, check-ins, analysis beyond the text saved with a workout, or anything about another athlete.
- Wahoo and Suunto — yes, and automatically. Once you connect one of these, Gradescale sends your upcoming planned cycling and running workouts to your account there, so they appear on the device (Wahoo head units; Suunto as SuuntoPlus Guides). This happens automatically when a plan is created, regenerated or edited, covering roughly the next two weeks, and you can also send a single workout on demand. Disconnecting the provider stops it.
- Garmin — yes, automatically, once it is on for your account. We are switching the sending to Garmin on step by step. Once you connect Garmin, and while the sending is on for your account, Gradescale sends your planned cycling and running workouts for roughly the next two weeks to your Garmin Connect calendar, so they reach your watch or bike computer. This happens when you connect, when you first open the website each day, shortly after you save a plan or change your threshold values or a limit; you can also send a single upcoming workout yourself. Each workout goes with its title, its sport, the date it is planned for, a reference number so that Gradescale can later change or remove it, and its steps: each step's duration, its target (a power in watts, a heart rate in beats per minute or a pace, calculated from your own threshold values and maximum heart rate, so those values can be worked out from it), and a short text with the step's name, any cadence or effort rating and any note written on the step, so anything you or your coach typed there goes too. No written description of the workout is sent, and we do not send recorded activities, measurement series, check-ins or analysis. Swimming and strength workouts, and workouts without steps, are not sent. If you have entered a limit for your workouts in Gradescale, a workout with steps above it is lowered to stay within it or is not sent, a workout with heart-rate targets is not sent, and the earlier copy of a workout that is not sent is removed at the next automatic sending instead of kept. When you change, move or delete a planned workout, Gradescale changes or removes its copy in your Garmin calendar; it changes or removes only workouts it sent itself, and keeps a list of them for that purpose, which it deletes when you withdraw health-data consent or delete your account. The sending runs only while your health-data consent (Section 5) is active. If you withdraw that consent, Gradescale asks Garmin to take the upcoming workouts it sent off your calendar before the connection ends; any it cannot take off stay there until you delete them in Garmin. When you disconnect Garmin or delete your account, workouts already sent stay in your Garmin account until you delete them there. When you disconnect Garmin in Gradescale, withdraw health-data consent or delete your account, and for the old account when you connect a different Garmin account, Gradescale asks Garmin to end the authorisation; the connection is deleted whether or not that request succeeds. Gradescale cannot make that request for a connection made with Garmin's earlier sign-in method, or for a Garmin connection that is deleted when two Gradescale sign-ins are joined into one because the joined account already has one; you can end that authorisation in your Garmin account.
- Hammerhead: only if you switch it on. If you connect Hammerhead and switch on the sending with the switch on the Hammerhead card in Settings > Integrations, Gradescale sends your upcoming planned cycling workouts made of timed steps, with a power target in watts for each step that has a target, to your Hammerhead account, so they reach your head unit. This happens when you switch the sending on, when you first open the website each day, when you connect the same Hammerhead account again while it is still connected, and shortly after you save a plan on the website or your cycling power threshold or the limit you entered for your workouts changes, covering roughly the next two weeks. Each workout goes as a workout file with its title and its steps, and the date it is planned for. The steps carry their order and repeats, each step's duration, its power target in watts if it has one, calculated from your cycling power threshold, so that threshold can be worked out from it, and whether it is a warm-up, work, rest or cool-down step. No written description is sent. While the sending is on, when you change or delete a planned workout dated today or later, Gradescale changes or removes the copy in your Hammerhead account; if a changed workout cannot be sent at that moment (for example while Gradescale has no cycling power threshold for you), the earlier copy stays as it was. If you have entered a limit for your workouts in Gradescale, a workout with steps above it is lowered to stay within it or is not sent, and the earlier copy of a workout that is not sent is removed instead of kept. Gradescale changes or removes only workouts it sent itself, and keeps a list of them for that purpose, which it deletes when you disconnect Hammerhead in Gradescale, withdraw health-data consent or delete your account. Turning the sending off removes no workout already in your Hammerhead account. Workouts already sent stay in your Hammerhead account until you delete them there, unless Hammerhead removes them when the authorisation ends. The sending runs only while your health-data consent (Section 5) is active.
- Withings: nothing. Gradescale sends no workout or other training data to Withings.
- Strava, COROS and Polar — nothing. These connections are one-way: data comes in and nothing goes back.
- intervals.icu — yes, and automatically. Once you connect it, Gradescale sends your upcoming planned cycling, running and swimming workouts to the calendar in your intervals.icu account. This happens automatically when you connect or switch the sending on, usually shortly after a plan is created, regenerated or edited on the website, and when you first open the website each day, covering roughly the next two weeks. Each workout goes with its title, date, sport and written description, a reference number so that Gradescale can later change or remove it, and, for a cycling workout whose steps are all power targets, a workout file with those steps. Any other workout (a run, a swim, or a cycling workout that cannot be sent as a file, for example because a step is not a power target) goes with its steps written out as text added after the written description: each step's duration, its target and, for cycling, its cadence. The written description is the text saved with the planned workout, whoever wrote it (you, your coach or Gradescale). For a workout made from your performance profile it gives its power or pace targets, calculated from your own threshold values, and, where known, the percentage of your threshold each one is, so your threshold can be worked out from them; for one made by the daily workout generator it names the training phase, your fitness level and the training needs it addresses, which come from our analysis of your training. In the steps written out as text, a power target is given in watts and a running or swimming pace target as a pace, calculated from your own threshold values (your cycling power threshold, your critical running pace and your critical swimming speed), so those thresholds can be worked out from them; where Gradescale does not have the threshold, the target is given as a percentage of it instead. A heart-rate target is given as a percentage of your maximum heart rate. Gradescale keeps a list of the workouts it sent, so that it can change or remove them later, and deletes that list when you disconnect intervals.icu in Gradescale or delete your account. While the sending is on, when you change or delete a planned workout on the website and it is dated today or later, the copy in your calendar is changed or removed in the same way. A workout whose date has passed is no longer looked at, so its copy stays in your calendar as it was until you delete it there. Gradescale changes or removes only workouts it sent itself. You can turn the sending off with the switch on the intervals.icu card in Settings > Integrations, and disconnecting stops it too; neither removes a workout already in your intervals.icu calendar. Besides the workouts, Gradescale sends intervals.icu only the sign-in exchange when you connect, whose signed, single-use code carries your Gradescale account identifier, requests to read your activities and your wellness values, a request to read your workout library when you import it, and, in the cases set out under "Disconnecting" below, requests to end an authorisation. It sends no check-ins, recorded activities or wellness values, and no analysis beyond what those descriptions and the steps written out as text say. intervals.icu may pass a workout on to services you have linked there; that is its own processing (Section 8).
Your control. You can disconnect any provider at any time at the provider. In Gradescale, you disconnect providers other than Strava in Settings on the website; your Strava connection ends with "Log out everywhere" on the website or "Disconnect Strava" in the mobile app (Section 10). Disconnecting stops further imports and stops anything being sent out; what happens to the data we already imported is set out in Section 11. Withdrawing your health-data consent (Section 5) stops the processing immediately. Each provider is an independent controller for what it does with your data on its own platform, under its own privacy policy.
intervals.icu
What comes in. If you connect intervals.icu, Gradescale receives the activities recorded in your intervals.icu account. For each one it takes the sport, the start time, the elapsed and moving time, and the distance, elevation, heart rate, power, cadence, speed, temperature, altitude and position recorded during it. The distance, the elevation and the measurements recorded during the activity come from the recording itself; the sport, the start time and the two durations come from the activity record at intervals.icu and from the recording, each supplying what the other lacks. The recording is read from the activity's original file when that is a FIT file, and otherwise from the FIT file intervals.icu generates for it. When you first connect, Gradescale also imports your activities from the previous 90 days. After that it imports an activity when intervals.icu reports it, whatever its date, and regularly looks for activities dated after the latest one it has already looked at; if the import of an activity dated earlier than that fails, Gradescale may not try it again. If you set a session effort rating on an activity in intervals.icu, Gradescale keeps it unless you already rated that session in Gradescale, and whenever intervals.icu reports a change to an activity, its title there replaces the title in Gradescale. Some of this is health data and is imported only while your health-data consent (Section 5) is active.
Which activities. intervals.icu collects activities from many services, and Gradescale keeps one copy of an activity that could reach it twice. If you have connected Garmin, Polar, Suunto, COROS or Wahoo to Gradescale directly, Gradescale does not import the activities intervals.icu received from that service that started at or after the moment you last connected it; activities that started earlier, and activities whose start time intervals.icu does not give, are imported through intervals.icu. Activities that intervals.icu holds from Strava are not imported through intervals.icu (connect Strava directly), and activities without a recording file, such as ones entered by hand, are not imported.
What we do with it. The same as for every other source (Section 2): analysing your training. Gradescale calculates its own training load from the recording; it does not import the load or fitness figures intervals.icu calculates, and it does not store your name from intervals.icu.
Wellness data. If you connect intervals.icu, Gradescale also reads the daily wellness values in your intervals.icu account: heart-rate variability, resting heart rate, sleep duration, sleep score and average sleeping heart rate, blood-oxygen saturation, respiration rate, body weight and body fat, daily steps, and the readiness score recorded in your intervals.icu account, whether a device or you entered it. The first time it reads your wellness data, and again after you disconnect and reconnect, it asks for the previous 180 days (about six months). After that it asks for the days since its last read and the three days before, when intervals.icu tells it your wellness data has changed and about once a day as a check. About once every seven days it asks for the previous 180 days again, to pick up a day that intervals.icu learned about later, such as when a device uploads a week late. intervals.icu sends each day as one record; Gradescale keeps one set of the values listed here for each day and discards the rest of that record on arrival, such as your other self-entered ratings, menstrual-cycle data, injury notes, calories or comments. It does not keep the stress score yet, and we will say so here before it does. This is health data (Section 5): Gradescale reads it only while your health-data consent is active in a version that covers recovery and body measurements, and if you gave an earlier version, no wellness value is read until you give the current one. Gradescale keeps these values in your account and includes them in your data export (Section 13). It keeps them for the same purposes as the device wellness data from your other connections: to show them to you and to use them in readiness and training calculations (Sections 4 and 15). A value is used for one of these purposes only from the day the screen or calculation that uses it is released; when this version took effect none was, so until then the values are only stored and included in your data export. Your coach can see them only if you have agreed to share your recovery and body measurements with them (Section 12). To stop these reads, disconnect intervals.icu in Gradescale, which also stops the activity imports and the workout sending, or withdraw your health-data consent (Section 5). There is no separate switch for the wellness values alone.
Your workout library. Gradescale reads your intervals.icu workout library only when you ask it to, by choosing to import it; it never reads it in the background. When you do, it asks intervals.icu, in one request, for the workouts saved in your own library and the folders and plans they sit in. The answer from intervals.icu can include folders that other people have shared with you; Gradescale ignores those and copies nothing from them, and it uses only folders that your intervals.icu account owns. Into your Gradescale workout library it copies the name, description and sport of each workout, its steps with their targets and durations, and the name of the folder or plan it sits in, creating a folder with that name if you do not already have one. It marks each copy as imported from intervals.icu and keeps the intervals.icu workout identifier, so that a second import does not add the same workout twice. It copies nothing else from your library. Some workouts cannot be copied exactly: a workout that cannot be turned into steps, or that is of a sport Gradescale does not have, is left out, and a workout that has to be changed slightly is copied only approximately. Gradescale tells you which, listing them by name, up to 50 of each. This needs one more permission from intervals.icu, to read your workout library. If you connected intervals.icu before Gradescale asked for it, the import is not available until you reconnect intervals.icu and approve it. The import only reads: Gradescale sends nothing back to intervals.icu. Gradescale keeps the copies in your account and includes them in your data export (Section 13); they stay until you ask us to delete them, withdraw your health-data consent or delete your account (Section 11). The import is available only while your health-data consent (Section 5) is active.
The access we ask for. When you connect, Gradescale asks intervals.icu for permission to read your activities, your wellness data and your workout library and to write to your calendar. Gradescale uses all four, and only as this section describes: it imports your activities, it imports the wellness values described above, it copies the workouts from your workout library when you ask it to (described above), and it sends the planned workouts described under "What goes back out".
Deleting an activity at intervals.icu. While your intervals.icu account is connected, intervals.icu tells Gradescale when you delete an activity there, and Gradescale then deletes its imported copy of that activity and what it stores with it: the recording, laps, nutrition entries, comments and segment results, the activity's match with a planned workout, and its share of your daily totals, which are recalculated. Gradescale does this only for a copy it holds as an intervals.icu import. A copy that is also linked to a Strava activity, or that Gradescale holds from another connection, is not deleted. intervals.icu sends this message once: if it does not reach us, or cannot be processed, the copy stays in your account until you ask us to delete it or delete your account (Section 11). Once you disconnect, deleting an activity at intervals.icu no longer reaches Gradescale.
Disconnecting. To disconnect in Gradescale, use Disconnect on the intervals.icu card in Settings > Integrations on the website. Gradescale deletes the stored connection, including the access token, your intervals.icu account identifier and the sync position, and tries to ask intervals.icu to end the authorisation; the connection is deleted whether or not that request succeeds. It does the same when you withdraw health-data consent or delete your account. It also tries to ask intervals.icu to end an authorisation when you connect a different intervals.icu account (for the old one) and when connecting fails after you approved it at intervals.icu (for the new one), in each case only if Gradescale can tell that no Gradescale account is connected to that intervals.icu account. When two Gradescale sign-ins are joined into one account, an intervals.icu connection that is not carried into the joined account is deleted, at the join or when you delete your account, without that request; you can end that authorisation in your intervals.icu account. Activities already imported stay in your account until you ask us to delete them, withdraw your health-data consent or delete your account (Section 11), unless you delete them at intervals.icu while the connection exists (see above). Wellness values already imported stay in your account until you ask us to delete them, withdraw your health-data consent or delete your account (Section 11), and workouts already sent stay in your intervals.icu calendar until you delete them there. If you instead remove Gradescale in your intervals.icu account, imports and sending stop, but the stored connection stays until you withdraw health-data consent or delete your account, or ask us to delete it.
4. What We Collect
- Account data: your athlete identifier at the connected provider, display name, profile picture, and the email address you give us. Sign-in credentials for connected providers are held as encrypted tokens and are deleted when the connection ends, as Section 10 describes, or when your account is deleted.
- Training data: activities (title, sport, time, distance, elevation) and their detailed recordings — power, heart rate, cadence, altitude, GPS location, and speed.
- Well-being check-ins you choose to submit: sleep, stress, soreness, and similar.
- Device wellness data from the platforms and devices you connect, such as heart-rate variability, resting heart rate, sleep duration, score and sleeping heart rate, stress scores, blood-oxygen saturation, respiration rate, body weight and body composition, daily steps and activity, and a readiness score where your device reports one, as far as Gradescale reads them from each. We keep these as daily values.
- Derived data we compute: training load, readiness scores, performance models, personal records.
- Consent and acknowledgement records: when we present a legal document to you we record the document and version (including a fingerprint of the exact text), the time, your IP address, browser or app details, platform, language shown, and the country it came from. We record what you actually did with each document, because they are not the same act:
- Terms of Service — accepted.
- This Privacy Policy — provided to and acknowledged by you.
- Health-data processing — explicitly consented to.
- Product analytics — consented to, or refused.
- Coach sharing — explicitly consented to.
- Newsletter — consented to.
- Feedback you send us: the text you write, the page you were on, your rating, which features you say you used, and what you tell us is missing. If you attach screenshots (up to three per report), we store the images. Location metadata is removed from them on your device before upload, but a screenshot still shows whatever was on your screen, which is usually your own training data. Feedback text is free-form, so it often contains health information — symptoms, injuries, how a session felt. Please treat it as you would any message about your health. Each report also sends an email notice to our own support mailbox, with a reference number, the page you were on (when it is a page address of the app), your rating, the last four characters of your account number, a copy of the text you wrote and of what you tell us is missing, whether you ticked the box that says it is fine to follow up, and the time. If you tick that box, the notice also carries, where we hold an account email address for you, that address as its reply address, so we can answer you. Without the tick it has no reply address and we do not follow up (the feedback itself is stored and filed as described in Sections 8 and 10). Where you tell us it is fine to reply, we keep your email address with the report; where you do not, we do not.
- Technical data: IP address and request metadata in short-lived infrastructure logs; error reports that are data-minimised before they leave your device or browser (Section 14); and, only if you opt in, product-usage events (Section 7). When you send feedback we may also attach diagnostic context from that browser session — recent in-app errors, which screens you moved through, the requests the app made and whether they succeeded, and the app version — so a report can be acted on without a conversation. The same minimisation as our error reports applies: location coordinates and the query part of web addresses (which can carry invitation links) are stripped before it leaves your browser, and we never capture your stored sign-in credentials.
- Payment data: none. Payments are switched off during the closed beta and no payment provider processes your data. Before enabling paid subscriptions we will name the provider, the data it receives, the legal bases, and the transfer safeguards in this policy.
5. Health Data and Your Explicit Consent
Heart-rate data, the recovery and body measurements your connected devices record, well-being check-ins, and the physiological metrics we derive from them say something about your body. This includes the heart rate recorded in rides imported from Hammerhead and the weight and body fat percentage read from Withings. It also includes the Polar sleep and the breathing measurements described in Section 3. Data protection law treats this as a special category of personal data, and we process it only with your explicit consent, which we ask for separately in the Health Data Processing Consent. That document — a separate, unticked checkbox at signup and a separate prompt for existing users — records the explicit consent (GDPR Art. 9(2)(a)) we rely on for all health-related processing in Gradescale.
It also explains how withdrawal works: withdrawing your health-data consent takes effect immediately — processing stops, access to the service ends, and deletion of your health and training data begins. Withdrawal cannot be cancelled, and the 30-day grace period that applies to ordinary account deletion does not apply to it. Three copies of feedback are outside that deletion; Section 11 names them. We keep a minimal record of the consent you gave and of your withdrawal, as evidence, until your account is erased (Section 10).
6. Why We Use Your Data, and On What Legal Basis
- Running the service you signed up for — importing, storing, and analysing your training data, syncing your settings between devices, and authenticating you: performance of a contract (Art. 6(1)(b)), and for health-related processing your explicit consent (Art. 9(2)(a)) as described in Section 5.
- Sending your planned workouts to intervals.icu — only if you connect it and leave the sending on: performance of a contract (Art. 6(1)(b)), because it is part of the intervals.icu connection you choose to make; you can switch the sending off at any time. A workout's written description can carry information about your training, such as targets calculated from your threshold values, your fitness level or training phase, so we send workouts only while your health-data consent (Section 5) is active, on your explicit consent (Art. 9(2)(a)). If you withdraw that consent the sending stops; workouts already in your intervals.icu calendar stay there until you delete them in intervals.icu (Section 3).
- Sending your planned workouts to Hammerhead, only if you connect it and switch the sending on: performance of a contract (Art. 6(1)(b)), because it is part of the Hammerhead connection you choose to make; you can switch the sending off at any time. A workout's power targets are calculated from your cycling power threshold, so we send workouts only while your health-data consent (Section 5) is active, on your explicit consent (Art. 9(2)(a)). If you withdraw that consent the sending stops; workouts already in your Hammerhead account stay there until you delete them there, unless Hammerhead removes them when the authorisation ends (Section 3).
- Sending your planned workouts to Garmin, once you connect it and while the sending is on for your account: performance of a contract (Art. 6(1)(b)), because it is part of the Garmin connection you choose to make. A workout's targets are calculated from your threshold values, so we send workouts only while your health-data consent (Section 5) is active, on your explicit consent (Art. 9(2)(a)). If you withdraw that consent the sending stops and we ask Garmin to take the upcoming workouts we sent off your calendar (Section 3).
- Product analytics — only with your separate opt-in consent (Art. 6(1)(a)); see Section 7.
- Transactional account emails — verification, deletion confirmations, and service notices: performance of a contract (Art. 6(1)(b)), or our legitimate interests (Art. 6(1)(f)) where the message is not strictly contractual.
- Newsletter and product marketing — your consent (Art. 6(1)(a)).
- Optional weather lookup for an activity — performance of the feature you requested (Art. 6(1)(b)); any consent required for the underlying location data is obtained separately.
- Coach relationship administration — invitations, roster, and revocation: performance of a contract (Art. 6(1)(b)).
- Disclosing health-related training data to a coach — your separate explicit consent (Art. 9(2)(a)); see Section 12.
- Support correspondence and feedback you send us — performance of a contract (Art. 6(1)(b)) and our legitimate interests (Art. 6(1)(f)) in resolving your request and improving the service. Authorised Gradescale staff may look at your account in a read-only view to find and fix problems, answer support requests and improve the service.
- Consent, withdrawal, and deletion records — compliance with a legal obligation (Art. 6(1)(c)) and our legitimate interests (Art. 6(1)(f)) in demonstrating compliance and defending legal claims. Consent and withdrawal records are kept only while your account exists, except the newsletter suppression record described in Section 10. After your account is erased, we keep some records filed under your account number, such as the records that you asked us to delete or export your data, the record of the most recent erasure of your account, and the register of any legal holds placed on your account (Section 10). We also keep the newsletter membership marker described in Section 10, which is not filed under your account number, on the basis of our legitimate interests (Art. 6(1)(f)); today we do not delete it.
- Mobile app distribution and, in future, subscription entitlements— performance of a contract (Art. 6(1)(b)) and compliance with app-store obligations.
- Security and service stability — short-lived technical logs, abuse prevention, and error reports: our legitimate interests (Art. 6(1)(f)). We rely on legitimate interests only where, after weighing the interests and risks involved, the processing is proportionate and your rights do not take precedence. The breached-password check described in Section 8 relies on this basis.
- Legal obligations (Art. 6(1)(c)) — keeping records the law requires us to keep, and responding to lawful requests.
We do not use your data for advertising or sell it to anyone.
7. Analytics, Cookies, and Similar Technologies
Strictly necessary storage. Signing in sets a session cookie (nb_session) that only authenticates you, and a short-lived cookie that protects the sign-in flow against forgery. The apps also use local storage on your device for settings and offline data. None of this tracks you across other websites.
Product analytics are off by default. Nothing analytics-related loads, runs, or sets an identifier until you choose "Accept" in the consent banner — on any page, including our public pages. If you accept, feature-usage events (for example, "a sync ran", "a page was opened") are recorded under a one-way-hashed identifier and processed for us by an EU-hosted analytics provider. These events do not contain your training values, health data, location traces, or email address. If your browser sends a Do Not Track signal, we treat that as a refusal. You can withdraw at any time in Settings or via the banner; withdrawal stops collection immediately and does not affect the service.
If you withdraw, we delete the analytics events already collected about you— both the events held by our analytics provider and the first-party events on our own systems. We do not keep them under an alternative legal basis.
How long we keep analytics events. We keep the analytics events on our own systems for as long as your account exists, so we can follow how Gradescale is used over time. We delete them when you withdraw analytics consent, when you delete your account, and when your account is deleted because you revoked Gradescale's access in your Strava settings (Section 11). Our analytics provider keeps its copy for its own retention period, currently up to 1 year, unless we delete it earlier because you withdrew or your account was deleted. Anonymous aggregate statistics that cannot identify you, such as how many athletes used a feature in a month, may be kept with no time limit.
We use no advertising cookies, no tracking pixels, and no fingerprinting.
8. Who Receives Your Data
We disclose personal data only to the recipients below, their vetted subprocessors, recipients you authorise, and otherwise where the law requires it.
Data sources (independent controllers):
- Connected training providers (Strava, Garmin, Wahoo, Suunto, COROS, Polar, Hammerhead, Withings, intervals.icu): they are the source of the data you authorise us to import and are independently responsible for their own processing. Five of them can also be recipients: see “Providers we send planned workouts to” below.
Strava API usage information. Strava may monitor and collect information about Gradescale's access to and use of the Strava API. Strava may use that information for purposes including operating and improving its API and platform, providing support, and checking compliance with its developer terms. Strava processes this information under its own privacy policy.
Providers we send planned workouts to:
- Wahoo and Suunto — if you connect them, we send your upcoming planned cycling and running workouts to your account there, so they reach your device. This happens automatically when a plan is created, regenerated or edited, and on demand for a single workout. We send the workout only: its structure, duration and intensity targets, which are calculated from your own threshold values. We do not send recorded activities, measurement series, check-ins or analysis. Each is an independent controller for what it does with the workout under its own privacy policy, and disconnecting stops it. See Section 3.
- Garmin — a recipient once the sending is on for your account. If you connect Garmin, we send your planned cycling and running workouts for roughly the next two weeks to your Garmin Connect calendar, so they reach your device (Section 3). We send the workout only: its title, sport, date, a reference number, and its steps with their durations, their targets, which are calculated from your own threshold values and maximum heart rate, and each step's name, cadence or effort rating and note. We do not send a written description of the workout, recorded activities, measurement series, check-ins or analysis. Garmin is an independent controller for what it does with the workout under its own privacy policy, and disconnecting stops the sending.
- intervals.icu — yes, a recipient. Once you connect it, we send your upcoming planned cycling, running and swimming workouts to your calendar there, automatically unless you turn that off (Section 3). We send the workout only: its title, date, sport and written description, a reference number so that we can later change or remove it, and, for a cycling workout whose steps are all power targets, those steps as a workout file. Any other workout (a run, a swim, or a cycling workout that cannot be sent as a file) goes with its steps written out as text after the written description. The written description is the text saved with the planned workout, whoever wrote it (for example you, your coach or Gradescale), so it includes anything you or your coach typed into it: for a workout made from your performance profile, power or pace targets calculated from your own threshold values and, where known, the percentage of your threshold each one is, and for one made by the daily workout generator, the training phase, your fitness level and the training needs it addresses (Section 3). In the steps written out as text, a power target is in watts and a running or swimming pace target is a pace, calculated from your own threshold values, so those thresholds can be worked out from them; where we do not have the threshold, the target is a percentage of it instead. A heart-rate target is a percentage of your maximum heart rate (Section 3). We do not send recorded activities, measurement series, wellness values or check-ins, and no analysis beyond what those descriptions and the steps written out as text say. intervals.icu is an independent controller for what it does with your data on its own platform, under its own privacy policy, including passing a workout on to services you have linked there. Disconnecting stops the sending.
- Hammerhead: a recipient only if you switch it on. If you connect Hammerhead and switch on the sending (Section 3), we send your upcoming planned cycling workouts made of timed steps, with a power target in watts for each step that has a target, to your Hammerhead account, so they reach your head unit. We send the workout only: the date it is planned for and a workout file with its title and steps. The steps carry their order and repeats, each step's duration, its power target in watts if it has one, calculated from your cycling power threshold, so that threshold can be worked out from it, and whether it is a warm-up, work, rest or cool-down step. We do not send a written description, recorded activities, measurement series, wellness values or check-ins. Hammerhead is an independent controller for what it does with the workout under its own privacy policy. Turning the sending off or disconnecting stops it.
Service providers (processors working for us):
- Cloudflare — hosting our API and database at its global edge network, storing the screenshots you attach to feedback, and keeping one copy of each activity file exactly as your provider sent it, for the providers Section 10 names (Cloudflare R2). That copy contains the same GPS track and sensor readings as the activity itself, including fields we do not read today.
- GitHub, Inc. (United States) — our issue tracker. When you send feedback, we file it as an issue in our private repository so it can be fixed and tracked. That issue quotes your feedback text as you wrote it, together with the page you were on, your rating, and a shortened reference to your account rather than your name or email. Where you attached screenshots, it carries expiring links to view them (below). Because feedback is free text, it regularly contains health information, so GitHub processes health data on our behalf when it does. GitHub is not permitted to use any of it for its own purposes. If you would rather your words were not stored in our issue tracker, please do not put anything in a feedback form you are not comfortable with us keeping there — email us instead at privacy@gradescale.fit.
- Vercel — hosting the web application.
- Sentry — error monitoring; reports are data-minimised and pseudonymised before sending (Section 14).
- PostHog (EU Cloud) — consent-based product analytics (Section 7), hosted in the EU.
- Resend — transactional email (account, deletion confirmations, beta notices) and the email notice of each feedback report sent to our support mailbox (which holds a copy of your text): receives your email address and the message content.
- Namecheap Private Email — hosts our support mailbox, so it holds the email notice of each feedback report, including the copy of your text described in Section 4 (health information you wrote in feedback can be in it).
- Ghost(Pro) — newsletter delivery for the waitlist and product updates, only where you opted in.
- Open-Meteo — historical weather lookup, only if you enable weather display. The request is made by our servers, not your browser, so Open-Meteo does not receive your IP address or any identifier for you. It receives only the activity date and a coordinate rounded to two decimal places (roughly one kilometre) — never your precise route. The response is cached at our edge for up to a year; historical weather is immutable and the cached record contains no data about you.
App distribution:
- Apple and Google — distribution of the mobile app and the related device and diagnostic information they process as independent controllers under their own policies. This applies today, even though payments are disabled.
- RevenueCat — subscription entitlement management. Not in use during the closed beta; it will process data only if and when paid subscriptions are enabled.
Breached-password check:
- Have I Been Pwned — while the check is switched on, when you create an account with an email address and a password, or choose a new password through a password reset, our servers check the password against the Pwned Passwords list of Have I Been Pwned (passwords exposed in known data breaches). They send only the first five characters of the password's SHA-1 hash, never the password, your email address or anything else about you, and compare the answer on our servers. If the password is on the list, you are asked to choose a different one. If the check gets no usable answer (for example it takes longer than 3 seconds or the service returns an error), the sign-up or password reset goes ahead without it. While the check is switched off, nothing is sent.
Recipients you authorise:
- Your coach — only after you accept a coach's invitation and give consent; see Section 12.
Payments. Payments are disabled during the closed beta and no payment provider processes your data. If we enable payments, we will name the provider, the data categories it receives, the legal bases, and the transfer safeguards in this policy before the integration goes live.
Other disclosures: professional advisers under confidentiality, authorities where legally required, and a successor if the business is transferred (your data would remain subject to this policy).
9. International Transfers
Some of the providers above process data outside the European Economic Area, the United Kingdom, and Switzerland, including in the United States. Where they do, we rely on recognised safeguards: the EU-US Data Privacy Framework (including its UK Extension and the Swiss-US framework) where the provider is certified, and otherwise the applicable standard contractual clauses with the required UK and Swiss adaptations. intervals.icu is run by intervals.icu Ltd, which gives a London address on its privacy policy page. What Gradescale sends to intervals.icu (Sections 3 and 8) is transferred to the United Kingdom on the basis of the European Commission's adequacy decision for the United Kingdom (Art. 45 GDPR). You can ask us about the safeguard applying to a specific provider at legal@gradescale.fit.
10. How Long We Keep Your Data
- Training and derived data: for as long as your account exists. Deleted through the flows in Section 11.
- Provider connections and their tokens: for as long as the connection exists. Your Strava connection belongs to your account rather than to a browser session: it survives signing out of the website on one device and periods when you do not use the app. It ends when you use "Log out everywhere", when Strava confirms a revocation you asked for with "Disconnect Strava" in the Gradescale mobile app (which also signs you out of the app), when you revoke Gradescale's access in your Strava settings, withdraw health-data consent, or delete your account. It can also end when the Gradescale mobile app cannot renew your Strava sign-in: the app then signs you out and asks Strava to revoke Gradescale's access. Its stored credentials are deleted when it ends, or at the latest 30 days after Strava tells us it has ended. Connections to other providers — recovery services, head units and watches — also belong to your account and survive signing out; they end when you disconnect the provider, revoke access at the provider (for Hammerhead, Withings and intervals.icu, see the next two sentences), withdraw health-data consent, or delete your account. For intervals.icu, the stored access token and your intervals.icu account identifier are kept while the connection exists and deleted when you disconnect in Gradescale, withdraw health-data consent or delete your account; if you only remove access at intervals.icu, they stay until you withdraw health-data consent or delete your account, or ask us to delete them. For Hammerhead and Withings, the stored sign-in tokens and your account identifier at that provider are kept while the connection exists and deleted when you disconnect in Gradescale, withdraw health-data consent or delete your account; if you only remove access at Hammerhead or Withings, they stay until you do one of those, or ask us to delete them.
- Hammerhead rides waiting to be imported: an entry on the waiting list (Section 3) is tried for up to 14 days and deleted 30 days after Gradescale stops trying it, or earlier: when you withdraw health-data consent or your account is deleted and, for an entry still waiting, when you connect a different Hammerhead account or connect Hammerhead again after disconnecting it.
- Sign-in sessions: deleted after 30 days without activity on your account. When you end a session (for example when you sign out, use "Log out everywhere" or reset your password) it stops working immediately. We then keep its record for up to 92 days, so that its sign-in cookie or token cannot be used again, and delete it after that. The record includes your display name, your profile picture link and, if you connected Strava and did not use "Log out everywhere", a copy of your encrypted Strava credentials, deleted when the record is. While the record exists we can still use those credentials to keep your Strava connection working and to check with Strava that it is still valid. Erasing your account or withdrawing health-data consent deletes your session records. We also keep a one-way fingerprint of each earlier sign-in token of a session, with the session it belonged to, so that we can tell which session an old token came from. These fingerprints are kept until your account is erased.
- Product analytics events: for as long as your account exists, so usage can be followed over time. Deleted when you withdraw analytics consent or your account is deleted (Section 7). Events collected before version 2.9 of this policy took effect are deleted within 90 days of collection, as version 2.8 said. Our analytics provider keeps its copy for up to 1 year unless it is deleted earlier. Anonymous aggregate statistics that cannot identify you: no time limit.
- Records of what you agreed to (consent records and signed-document receipts): kept no longer than your account, and deleted when your account is erased (Section 11). They contain no training or health measurements.
- Records that you asked us to delete or export your data: the date, the type of request and its outcome, filed under your account number, with no training or health measurements. These stay after your account is erased, and today we do not delete them automatically. We also keep the record of the most recent erasure of your account, filed under your account number. The erasure may start with your request, a withdrawal of health-data consent, or a revocation of our access in Strava. Today we do not delete this record automatically, but if the same account number is scheduled for deletion again, the new entry replaces it. A second record of each erasure, in our audit log, is deleted after 12 months.
- Breach-awareness record: if we ever notice a personal-data breach, we keep one internal record of when we became aware of it, under an incident code and without the account numbers of the athletes affected or any health data, for 10 years.
- Records of a deletion paused by a legal hold: kept for 12 months, or for as long as the hold lasts if that is longer.
- Register of legal holds: for each hold placed on your account, the account number, the case reference, the reason, who placed and released it, the release reason and the dates. It stays after the hold ends and after your account is erased, and today we do not delete it automatically.
- Accounts left undecided on health consent: suspended until you decide; the data already stored is kept. We do not delete an account because no decision was made: it is deleted only when you decline or withdraw health-data consent, delete your account, or revoke our access in Strava (Section 11).
- Coach access audit log: 12 months. Administrative audit log: 12 months.
- Coach notes and comments about you: for as long as the coaching relationship exists; deleted with your account.
- Feedback you send us, and any screenshots attached to it: deleted automatically 24 months after you sent it, or earlier, along with everything else, when your data is erased (Section 11), which includes revoking Gradescale's access in your Strava settings. The issue we file in our tracker is kept for the life of that tracker; ask us and we will delete or redact it. The email notices in our mailbox (Section 4), which hold the copy of your text, are not part of the automatic deletion above or of the erase in Section 11; they stay until we delete them. Ask us at legal@gradescale.fit and we delete them from the mailbox. Tell us roughly when you sent the report and which page you were on, so we can find them.
- The original file your provider sent for each activity: kept until you delete your account, or until its activity is erased in one of the other ways below. When Strava, Garmin, Wahoo, Suunto, COROS, Polar or intervals.icu hands us an activity, we keep one copy of it exactly as it arrived, next to the measurements we read out of it. We do this so that a feature built later can work something out from the history you already have — the file carries fields we do not read today, and without a copy the only way to recover them would be to ask your provider for your whole history again. It contains nothing about you beyond what the activity itself contains. It is erased exactly when the activity it belongs to is erased: when you delete your account (Section 11), when you revoke Gradescale's access in your Strava settings (which removes your Gradescale data), and, for a single activity, when you delete that activity on Strava. Disconnecting a watch or head unit ends the connection but keeps your training history, so the copies stay for as long as those activities do.
- Links to view a feedback screenshot: the links placed in our issue tracker are signed and stop working after 90 days. This is the link, not the image: the image itself is kept as described above. Anyone holding a working link can view that one image, so we only put them in the private tracker.
- Support correspondence by email: 24 months from the close of your request (the feedback email notices described above are the exception).
- Transactional email delivery logs: 30 days.
- Newsletter records: until you unsubscribe or your entry is deleted. A minimal suppression record (your email address and the fact you unsubscribed) is kept indefinitely so we cannot accidentally re-subscribe you; it is separate from newsletter engagement history, which is deleted.
- Newsletter membership marker: if our invitations for newsletter members are set up, when your data is erased (Section 11) we keep a marker for each newsletter membership linked to your account through your waitlist entry or an invitation you claimed. The marker is a one-way code made from the membership number with a secret key, with the fact that the membership was erased and two dates. Where an invitation record existed, that record is kept with only the same code, its own random record number, the campaign, the fact that it was erased, a counter, a flag and two dates. Neither holds a name, email address, membership number or account number, and the code cannot be turned back into the membership number. When the newsletter provider tells us a membership was deleted, we also keep a marker for it, whether or not any data is erased here: the same one-way code, the fact that the membership was deleted at the provider and two dates, and nothing else. We use it only to recognise that membership if it reaches us again, so that it is not offered an invitation again and cannot claim one twice. We keep it on the basis of our legitimate interests (Art. 6(1)(f)). Today we delete neither. The provider's message that a membership was deleted also leaves a record, kept on the same basis so that we recognise the message if it is sent again: a one-way code made from the message, the same one-way code of the membership, the fact that the message reported a deletion and the date it arrived, and nothing else. If that membership's data is erased here after the message arrived, the erasure deletes the record; today nothing else deletes it.
- Waitlist entries: 12 months from signup.
- Security and abuse records: rate-limit windows 24 hours; sign-in state records 30 minutes.
- Error reports: deleted automatically after at most 90 days.
- Records we are legally required to keep (for example accounting records once payments exist): the period the applicable law requires — currently 10 years under Swiss law.
Residual copies in operational backups expire within 30 days and are never restored into active processing.
11. Deleting Your Data and Disconnecting
Three self-service routes. Every deletion they start is confirmed in writing by email where we have your address:
- Disconnect a training provider (in Gradescale, or by revoking access at the provider): imports stop immediately and the stored connection is removed (for Hammerhead, Withings and intervals.icu, revoking access there leaves it stored: see Sections 3 and 10). The data we imported from it stays in your account; you can ask us to delete it at any time, or delete your account (below). Workouts already sent to your intervals.icu calendar stay there until you delete them in intervals.icu. Workouts already sent to your Hammerhead account stay there until you delete them there, unless Hammerhead removes them when the authorisation ends. Workouts already sent to your Garmin calendar stay there until you delete them in Garmin. Strava is different, because you sign in with it. On the website, "Log out everywhere" ends the Strava connection and keeps your Gradescale data. The "Disconnect Strava" button in the Gradescale mobile app signs you out of the app, asks Strava to revoke Gradescale's access and keeps your Gradescale data; the connection ends once Strava confirms. If Strava cannot be reached (for example while your phone is offline), only that phone is signed out and the connection continues; use "Log out everywhere" on the website to end it. To delete your Gradescale data, delete your account (below). If you revoke Gradescale's access in your Strava settings, we delete your Gradescale account and all its data after a 5-day grace period. Signing in with Strava again within those 5 days cancels the deletion. Three copies of feedback and the newsletter membership marker are exceptions to the deletion, as the next bullet says.
- Delete your account (Settings > Delete My Account): your sessions are ended immediately and a 30-day grace period starts, during which you can cancel from Settings. We confirm the request by email, and again when deletion completes. After the grace period, your personal data is deleted from active systems within 7 days; only records we must keep as legal evidence (such as the records that you asked us to delete or export your data, the record of the most recent erasure of your account, and the register of any legal holds placed on your account, all filed under your account number) remain. We also keep the newsletter membership marker described in Section 10, which is not filed under your account number. An erasure also does not reach three copies of feedback: the issue we file in our tracker and the email notices in our support mailbox (Section 10 says we delete both on request), and Resend's 30-day delivery log of those emails, which expires on its own. Workouts already sent to your intervals.icu calendar are held by intervals.icu and stay there until you delete them in intervals.icu (Section 3). Workouts already sent to your Hammerhead account are held by Hammerhead and stay there until you delete them there, unless Hammerhead removes them when the authorisation ends (Section 3). Workouts already sent to your Garmin calendar are held by Garmin and stay there until you delete them in Garmin (Section 3).
- Withdraw your health-data consent (Settings > Health data consent): takes effect immediately — processing stops, connected-provider access is revoked, coach access ends, and deletion of your health and training data begins at once, with no grace period. It cannot be cancelled. Your health and training data are deleted from active systems within 7 days. Residual copies in operational backups expire within 30 days and are never restored into active processing. Where a processor holds affected health data, we instruct it to delete that data as part of the same process, except for three copies of feedback: the issue we file in our tracker and the email notices in our support mailbox (Section 10 says we delete both on request), and Resend's 30-day delivery log of those emails, which expires on its own. Workouts already sent to your intervals.icu calendar are held by intervals.icu and stay there until you delete them in intervals.icu (Section 3). Workouts already sent to your Hammerhead account are held by Hammerhead and stay there until you delete them there, unless Hammerhead removes them when the authorisation ends (Section 3). Gradescale asks Garmin to take the upcoming workouts it sent off your Garmin calendar before the connection ends; any it cannot take off, and workouts on past days, stay there until you delete them in Garmin (Section 3). See the Health Data Processing Consent for details.
12. Coaches
If you accept a coach's invitation, you give separate, explicit consent under Article 9(2)(a) GDPR for that named coach to receive health-related training data about you. The invitation names the coach and lists what they will be able to see before you decide:
- Heart-rate data
- Sleep, stress, and soreness check-ins
- Recovery and body measurements recorded by your connected devices (for example heart-rate variability, resting heart rate, sleep, stress scores, blood-oxygen saturation, respiration, body weight and composition, daily steps)
- Readiness scores
- GPS routes
- Power data
- Physiological models and performance estimates
- Notes and comments from other coaches on your account
- Planned and completed workouts
A coach also sees the breathing measurements recorded during your workouts (breathing rate, the volume of each breath and the volume you breathe per minute; Section 3). They are part of each workout's recording, and a coach sees the whole recording, so every coach whose invitation you accepted sees them, including a coach you connected before this policy described them.
Recovery and body measurements are different: a coach you connected before they were added to the invitation sees them only after you disconnect that coach in Settings > Coach and connect again under the updated consent.
Your coach can also add comments and notes and plan workouts for you. You can revoke this consent at any time in Settings > Coach, which ends the coach's access immediately. Revoking coach consent does not delete your account or withdraw your general health-data consent. We keep an internal log of coach access to your data (what was viewed, when, from where) for 12 months, for accountability; it is not shared externally.
13. Your Rights
To exercise any right, email legal@gradescale.fit. We answer within one month and may ask you to verify your identity in a proportionate way. Most requests can also be handled directly in the app (export in Settings > Export My Data, deletion per Section 11).
- EEA: you have the rights in the GDPR — access, rectification, erasure, restriction, portability, objection to legitimate-interest processing, withdrawal of consent, and complaint to your supervisory authority.
- United Kingdom: the equivalent rights under the UK GDPR and Data Protection Act 2018, with complaints to the ICO.
- Switzerland: the rights provided by the Federal Act on Data Protection, with complaints to the FDPIC.
Gradescale is not offered in the United States or Canada during the closed beta, so US state privacy laws and Canadian federal and provincial privacy laws are not addressed here. If we open the service to users in either country we will publish the additional notices those laws require before doing so.
If you are outside the European Economic Area, the United Kingdom, and Switzerland, your own country may give you similar rights, and it may give you a supervisory authority to complain to. We apply the access, correction, deletion, export and consent-withdrawal rights described above to every user, wherever you live, rather than only where a law compels them. Contact us the same way and we will handle your request the same way.
Data portability covers the data you provided; our export additionally includes the analysis we computed for you. Data imported from a connected provider is also available from that provider directly.
14. Security
- All traffic between your devices and Gradescale is encrypted in transit.
- Sessions are integrity-protected with signed tokens; provider credentials are stored encrypted, with keys held separately from the data.
- Error reports are data-minimised and pseudonymised before transmission: identifying fields are stripped or hashed, and location data is removed. Server logs pass through automatic redaction of credentials and secrets.
- Access to systems and data is restricted to what each component needs, and we monitor our dependencies for known vulnerabilities.
No system is perfectly secure. If you find a vulnerability, please report it to legal@gradescale.fit (see also our security.txt).
15. Automated Analysis
Gradescale evaluates your training data to produce scores, models, and suggestions — this is profiling in the legal sense, limited to your athletic training. It is informational: no Gradescale output produces legal or similarly significant effects about you, and every training decision remains yours (or your coach's). Scores respond mainly to your recent and longer-term training load, the intensity and duration of your activities, and the check-ins you submit. Missing or incomplete data may reduce the completeness or reliability of a score or recommendation.
Where the same activity could arrive from more than one connection, fixed rules decide which copy Gradescale keeps (Section 3). They do not score or rank you and have no legal or similarly significant effect. The scores and models described above are applied to activities imported from intervals.icu in the same way as to every other source. Wellness values imported from intervals.icu are kept for the same scores and recommendations as device wellness data from your other connections. A score or recommendation uses them only from the day it is released with them; when this version took effect none did, so they were only stored (Section 3). What is said above applies to them in the same way as soon as one does.
16. Age Requirement
Gradescale is for adults. You must be 18 or older, and account creation requires an explicit confirmation of this. If you believe someone under 18 has an account, contact legal@gradescale.fit and we will delete the data.
17. Changes to This Policy
The version number above always identifies the current text. We record which version of this policy was provided to and acknowledged by you and, separately, the exact text of each consent you gave. How we handle changes depends on what changes:
- Editorial clarifications: we publish the new version.
- New or changed processing described in this notice: we inform you in the app or by email before it takes effect.
- New optional processing based on consent (and any new special-category processing): we ask for that consent separately — continued use alone is never treated as consent.
Previous versions are available on request.
18. Contact
Thomas Mortelmans — Switzerland — legal@gradescale.fit (postal contact available on request).
We aim to acknowledge enquiries within 5 business days and resolve them within one month. If you are unsatisfied, you can complain to your data protection authority (Section 13).