Data controller
FredCoach is a cycling training web app with artificial intelligence, owned and operated by Salvaje Bike S.L. (Fred's Cycling Obsession brand), tax ID B87761391, registered office at C/ Valdemorillo 50-A, 28925 Alcorcón (Madrid, Spain), registered in the Madrid Commercial Registry, Volume 35675, Folio 125, Sheet M-641138. Contact: support@freds.cc.
FredCoach accesses your activity and recovery data through the devices and services you connect, always with your explicit permission.
Data we process
FredCoach only accesses the data needed to provide your personalised training service:
Purpose of processing
- Work out your training load, your form (CTL, ATL and TSB) and your attributes from your real training history.
- Personalise the AI coach's recommendations to your current state, history and goals.
- Remember the context between sessions so the coach does not ask you the same thing every day.
- Fit what we suggest to your schedule: the hours you usually train (from your quality sessions or from what you tell us) and the time you usually fall asleep (from your recovery source), so we never suggest a hard session too late. You can set or change it in My profile → personal details.
- Calculate and show your power and heart rate training zones.
- Measure how the app is used, in aggregate, to improve it: how long you have it open and in which part (Today, Sessions, Progress or My profile), added up per day. We do not store what you read or tap, and we use no third-party analytics; it is deleted with your account and, in any case, after 400 days.
- Let you follow how your fitness evolves over time.
- Resolve incidents and improve the service: to understand a bug, a question or an idea you send us, or to check that the coach works well, a member of the team may review your account data, including your history with the coach. They do so with restricted access, only for that purpose and without sharing it with anyone. The screenshots you attach to a feedback message (up to 3) are kept with that message in private storage; only the team sees them, they reach us attached to the internal support notice, the AI does not read them, and they are deleted with your account.
- Use your health data for your training and nothing else: sleep, HRV, resting heart rate and weight are only used to work out your recovery and adapt your load. They are not used for advertising, commercial profiling or decisions about you outside FredCoach.
- The data we receive from each source is used only for the purpose for which you authorised it.
- Show where each improvement comes from: when an idea you sent us becomes part of the app, other athletes see it in My profile → News. Only if you allow it (we ask you in the app) they also see your first name and the time you suggested it; you can take your name off at any time with «Quitar mi nombre». Without your permission it shows as an idea from «a beta cyclist», with the day only. Never your surname, your email or the text you wrote.
- Your rating of FredCoach: if the app asks you to rate it and you do, we keep your 1–5 rating, your comment (required: a few words about your rating), the date, the app version and how many days you had used it, as proof that the rating comes from someone who uses the service. We publish only the average of all ratings and how many there are, without your name or comment; the team reads the comment to improve and, if your rating is low, to write to you if we can help. You can change it at any time in My profile → Account → Your rating. If your rating is low and we fix the issue, we ask you once in the app whether you want to update it: you decide, we never change it for you. If you delete your account, your rating and its comment are kept without your name or any link to your account (as on other review platforms); if your comment includes something that identifies you and you want it removed, write to support@freds.cc.
Consent and access to your sources
FredCoach accesses each source (Garmin, COROS, Suunto, Polar or Zepp through Stridee; Hammerhead; Polar; Wahoo; WHOOP; intervals.icu) only through its official authorisation flow: you give permission when you connect it and can revoke it at any time from that service's settings or by disconnecting it in My profile. We ask for the permissions we need to read your data and, only for the features you use, to write to your account: sending the sessions of your plan to your device or to your calendar (for example to your Karoo, your Garmin, your Wahoo or your intervals.icu calendar, from where Zwift or MyWhoosh pick them up). FredCoach never posts anything on your behalf and never deletes your activities.
FredCoach no longer connects to Strava. If you connected it before October 2026, we keep the activities imported at that time as part of your history until you delete them or your account.
The legal basis is your explicit consent (Article 6.1.a of the General Data Protection Regulation, GDPR) and, for health data —heart rate, HRV, sleep, recovery, weight, perceived effort, the injuries or limitations you tell your coach—, your explicit consent under Article 9.2.a GDPR. You give it separately for each source, when you connect it and before we read anything, on that brand's permission screen; we keep which permissions you granted to each source and when, and which version of these terms you accepted. It is not a box that quietly takes the service away: if you do not authorise a data type, the feature that needs it does not use it and we tell you. You can withdraw each consent at any time, as easily as you gave it, by disconnecting the source in My profile → Connections, from that brand's settings or by email to support@freds.cc. When you withdraw it we stop reading that source or data type at once and, if you ask, we delete what we had already read from it; withdrawal does not affect what was processed before. If we offer you something new to authorise (another source, another data type) we ask you then, not before.
How FredCoach uses artificial intelligence with your data. What the AI does. FredCoach uses a language model (Claude, by Anthropic) for two things: holding the conversation with your coach and writing text about your training (the analysis of a ride, your cyclist profile, the internal analysis of a feedback message). The calculations that decide your plan —load, form, recovery, zones, sessions— are made by our own system with rules, not by an AI model. What data it receives. To reply, the model receives your messages, a summary of your training state (figures from your rides, your recovery if you authorised it, your goals and what the coach has noted about you) and the documents or images you attach. Data that comes from Garmin is treated like the rest of your training data. What it does NOT do. Data that reaches us from Garmin or from any other source is never used to train, fine-tune, improve or evaluate any AI model, ours or a third party's; it is not sold or shared with anyone other than the technical providers in this policy. Who and where. The AI provider is Anthropic. Under its commercial terms, what is sent through its API is not used to train its models and is deleted from its systems within 30 days (longer only if a safety system flags possible misuse, or where the law requires it). The database is in the EU (Supabase) and the application's functions run in Dublin (Vercel). Your consent. For the AI to use your training and health data, you accept it when you accept these terms and this policy. You can withdraw it at any time by emailing support@freds.cc: we handle it by hand and confirm it to you by email; you can still see your figures, your calculated plan and your history. When we add a separate AI consent in the app, we will ask you for it there. You can ask at any time for access, rectification, erasure and export of your data (section 06). The AI's recommendations are not medical advice.
Garmin Connect data
This section gathers, in one place, everything that applies to the data that comes from Garmin. The controller is Salvaje Bike S.L. (see section 01).
- What we receive. Only what Garmin sends us after your authorisation: the file of each activity (power, heart rate, cadence, altitude, duration and distance) and, only if you authorise it separately, your daily health data (sleep, HRV, resting heart rate and body composition). Through Stridee, when you connect we also receive the history of your previous Garmin activities; through the direct connection, only what you record from the moment you connect.
- How it reaches us. Directly through the Garmin Connect Developer Program (Garmin International), once that connection is available, or, if you connected Garmin earlier, through Stridee, an intermediary that delivers your activity files to us with your consent.
- What we use it for. To analyse your rides, to adapt your training sessions, to send the sessions of your plan to your Garmin device if you ask us to, and so that your coach —which uses artificial intelligence— can explain to you, and only to you, what the data says.
- What we never do. We never sell your Garmin data, never use it for advertising and never share it with anyone other than the technical providers listed in this policy. It is never used to train, fine-tune, improve or evaluate any AI model, ours or a third party's. Anthropic, the AI provider, processes it on our behalf only to answer you and does not use it for its own purposes.
- How we protect it. Through Stridee we do not hold any Garmin access token. With the direct connection, the access tokens that let us read your Garmin data are stored encrypted and are only used by our server; they are never sent to your browser.
- How long we keep it. For as long as your Garmin connection is active.
- When you disconnect Garmin (in My profile → Connections, in Garmin Connect or in Stridee) we stop reading it and we delete what we received from Garmin: the activities whose only source is Garmin and your Garmin health data; anything you also have from another source stays. The only exception is data we are legally required to keep.
- Withdrawing your consent or asking for deletion. Disconnect Garmin as described above, or write to support@freds.cc (also to withdraw the use of the AI or to delete your account and all your data). More about your rights in section 06.
Garmin's own privacy policy: garmin.com/privacy.
Who we share data with
To run FredCoach we use the following trusted providers, each under its own privacy policy and data processing agreements:
- Supabase — Database where we store your profile, wellness and conversations. Infrastructure in the EU. supabase.com/privacy
- Anthropic — AI provider (Claude). Your messages, a summary of your training state and the screenshots or reports you attach (such as an effort test) are sent to its servers to generate the coach's replies, the written text of your cyclist profile and, when you send us feedback, an internal analysis of your message for the team (with your message, a summary of your training state and what your coach has noted about you, including limitations you told it about; never your chat; the analysis is kept with your message and deleted with it or with your account). Under its commercial terms, data sent through the API is not used to train its models. If you attach a document or an image in the chat, we read it once with this provider to understand what it contains; we do not keep the file, only what we read from it, which is deleted with your chat history. Anthropic deletes what it receives through its API within 30 days (longer only if its safety systems flag possible misuse, or where the law requires it). anthropic.com/privacy
- Vercel — Web app hosting. vercel.com/legal/privacy-policy
- Garmin — Only if you connect it directly: source of your activities and, if you authorise it, of your daily health data (sleep, HRV, resting heart rate, body composition), through the Garmin Connect Developer Program of Garmin International. garmin.com/privacy. You can withdraw access from your Garmin account or in My profile. When you disconnect Garmin we delete what we received from Garmin: the activities whose only source is Garmin and your Garmin health data (sleep, HRV, resting heart rate, body composition); anything you also have from another source stays. If you connected Garmin through Stridee, your history is read again if you reconnect it; if you connect it directly, Garmin does not send the earlier history again, only new activities.
- Stridee — Only if you connect (or connected earlier) Garmin, COROS, Wahoo, Suunto, Polar or Zepp through it: intermediary that delivers your activity files to us with your consent. stridee.com
- Wahoo — Only if you connect it directly: source of the activities recorded with your ELEMNT or in the Wahoo app, through its official Cloud API (OAuth); with your permission we also leave the training sessions you send from FredCoach in your Wahoo library and calendar. Wahoo does not share with us the activities you record with other apps. Access tokens are stored encrypted and only used by our server. You can withdraw access from your Wahoo account or in My profile. wahoofitness.com/privacy
- Hammerhead (SRAM) — Only if you connect your Karoo: source of your activities, through its official OAuth. sram.com/en/company/legal/global-privacy-policy
- Stripe — Only if you support the project: processes the payment of your contribution. FredCoach never sees or stores your card details; only the amount, the date and the receipt email. stripe.com/privacy
- Resend — Sends FredCoach's emails (request confirmation, invitation, sign-in links, and the acknowledgement and our reply when you send us feedback, which include the text you wrote; any screenshots you attach go only in the internal notice that reaches our support team). It receives only your email address and the content of the message. resend.com/legal/privacy-policy
- WHOOP — Only if you connect it: source of your recovery, sleep and body composition data, and of your non-cycling workouts. whoop.com/privacy
- Polar — Only if you connect it directly: source of your activities and, if your watch provides them, your daily activity, physical information (such as weight or resting heart rate) and nightly recovery, through its official AccessLink OAuth. polar.com/en/legal/privacy-notice
- intervals.icu — Only if you connect it: we send the planned sessions of your week to your intervals.icu calendar (from where Zwift or MyWhoosh can pick them up) and, only if you choose it as a source, we receive your activities from it. FredCoach does not take the data it gets from Garmin Connect, nor your wellness data. intervals.icu/privacy-policy
Rights over your data
Under the GDPR, you have the right to:
- Access: request a copy of all the data we hold about you.
- Rectification: correct inaccurate or incomplete data.
- Erasure: ask us to delete all your data ("right to be forgotten").
- Portability: receive your data in a structured, readable format.
- Objection: object to the processing at any time.
- Withdrawal of consent: by disconnecting the source in My profile → Connections, from each service's settings or by email (also for the AI). We stop reading at once and, if you ask, delete what was already read from that source. For Garmin we do it automatically when you disconnect it.
- Restriction and complaint: you can ask us to restrict the processing and lodge a complaint with the Spanish Data Protection Agency (aepd.es).
To exercise any of these rights, contact us at:
We will reply within one month at most.
How we protect your data
All data is stored in Supabase, encrypted at rest and in transit (HTTPS). Database access is restricted with Row Level Security (RLS) and service keys that are never exposed to the browser.
The access tokens of the services you connect directly (WHOOP, Hammerhead, Polar, Garmin, intervals.icu) are stored encrypted in our database and only used by the server to sync your data; they are never sent to your browser. You can revoke them at any time from each service's settings.
How long we keep each thing. While you have an account: your rides and series (the second-by-second detail older than 6 months, in an encrypted private archive), your recovery data and your conversations (after 13 months they leave the database and move to an encrypted private archive). What we read from a source is deleted if you withdraw that consent and ask for it, and always when you delete your account. The exception is Garmin: what we received from Garmin is deleted when you disconnect it, without you having to ask. Access tokens are deleted when you disconnect. Technical logs without identifiers, up to 400 days.
We keep your data while you use the service. You can delete your account yourself from My profile → Delete my account and data: all your data and your user are deleted from the database at once, and FredCoach's access to WHOOP and Hammerhead is revoked. You can also ask for it by email. Backups: as a security measure required by the GDPR (Art. 32.1.c, being able to restore the data after an incident), the database keeps automatic daily backups for 7 days; they are not consulted or used for anything else and they renew themselves, so after you delete your account your data disappears from them within 7 days at most.
Access and support model. FredCoach is free during the beta and is funded by voluntary contributions (from €2). Your commitment to the project is shown in a bar that fills up every time you contribute and goes down with time, with the days you use the app and with the cost of the AI behind your use of the coach; to work it out we store which days you open it (only the date). If the bar reaches zero and you do not support the project, your access is paused and your place may be offered to someone else; your data stays stored until you decide to delete it, and access is reactivated when you contribute. Contributions are voluntary and non-refundable except in case of a charging error or if your access request is not accepted (see below).
Access requests. Access is by invitation. When you request it from the welcome page we store your name, email, the optional details you add (type of rider, next goal, what you record your rides with) and a fingerprint of your connection to stop abuse (never the IP itself). Places are opened in batches: requests that come with a contribution go first in the queue, then the rest in order of arrival. If you contribute when requesting access, Stripe processes the payment and we link it to your account when you join; if your request is not accepted, it is refunded. If you ask for the paid-subscriber place (the link in the newsletter's emails for paying subscribers), we check with Stripe, the payment processor the newsletter uses, whether that email has an active paid subscription; we only store that your request came from there and whether it was confirmed, never details of your subscription, and cancelling it later does not affect your place. We send you an email confirming your request and, when your place is ready, your invitation with your personal key. If you delete your account, your request is kept only as an anonymous record (without your email, name or messages).
One place per person. Places are limited and the project is kept going by the support of the people who use it, so we check that each person has a single account. To do so we compare, only as encrypted fingerprints and never the data itself: your email, your brand account (WHOOP, Hammerhead), the serial number of the device you record with (it comes in your activity files) and whether your rides exactly match those of another account. If a new account matches another one that is paused or without support, it is put under review and a person on the team decides; it is never decided automatically. If you delete an account that was paused or without support, we keep those encrypted fingerprints for 12 months (they cannot be turned back into your data) and then delete them. Legal basis: our legitimate interest in preventing abuse of the places.
FredCoach is a training support tool and its recommendations are generated by an AI: they are not medical advice. If you have health concerns, consult a professional.
Updates to this policy
We may update this privacy policy from time to time. If we make significant changes, we will let you know inside the app. The date of the last update always appears at the top of this document. If the change affects what you authorised (a new source, a new data type, another use of the AI), we do not apply it until you authorise it again in the app.
If you have any questions about this policy or about how we handle your data, please contact us:
support@freds.cc · Alcorcón, Madrid