Forgade Privacy Policy

Data Controller

KS-Agents di LR — Luca Ricatti.

Where your workout data stays

Workouts, GPS tracks, sensor data, and data read from Apple Health or Health Connect remain on your device by default.

If you enable Cloud Sync (separate consent, can be disabled at any time), a copy of your activities (an encrypted CSV of the track and sensor data) is uploaded to private cloud storage so you can also view them from the web portal. A copy of your gym sessions (exercises, sets, loads, reps, RPE, duration and heart rate; never your notes) is uploaded too: you see them in the app and, if you join a team, its trainers see them as the sharing settings allow. The copy also holds a snapshot of your profile, training load and daily recovery values (including the areas where you report soreness and the level you give each, if you do), the gyms, equipment and personal exercises you set up in the app, and your planning context: your active training goals (not goals about health or body composition, and never your notes) with the date, distance and elevation of the race and, if you uploaded the GPX route of a goal, a simplified version of that route (at most 300 points, for up to 6 goals), your weekly availability, the rest days you marked and the availability exceptions you set for specific dates (never your notes, from today up to one year ahead), the sessions already on your calendar for the next 90 days (date, sport and planned minutes only, never titles or notes), a summary of your current program and the program itself, session by session (date, sport, planned minutes and load, instructions, work blocks and, for gym sessions, the prescribed exercises), together with the cards of your planned calendar from 28 days ago to 120 days ahead and whether each was done, skipped or moved (never your notes) and, for a skipped session, the reason you gave if you gave one, as a category and never the text you may write under “Other” (the reasons “Not feeling well” and “Injury or pain” only if you also turned on the separate health switch described under “Health conditions you declare”) and, only if you turned on “Use my calendar commitments”, the hours you are busy on the next 90 days (times only, never titles). If you join a team, its trainers see only what you share with them in the team's sharing settings (activity history, activity details, wellness, food diary, program and calendar; with activity history they also see your planning context, calendar busy hours included if you turned that option on), and can send you workouts, gym routines and programs that change nothing until you approve them in the app. The program and calendar switch is off when you join a team: while it is off, trainers see only the title, the revision and the number of sessions of your program; when you turn it on, they see the sessions of your program and the cards of your calendar, but not the titles of the cards you wrote yourself or imported from another service, and never your notes or the reason you gave for skipping a session. If you share wellness, they also see the areas where you report soreness and the level you give each, if you do. The wellness switch (Team & Beacon → Data Sharing & Privacy → “Recovery & Wellness (HRV, Sleep)”) is on when you join a team. While it is on, the Coach that a trainer uses for you also receives your overnight signals (breathing rate, blood oxygen, the deviation of your skin or wrist temperature from your baseline, and how fast your heart rate drops after exercise) together with your other wellness values; it never receives your menstrual cycle or the notes you write in the diary. You can turn the switch off at any time in the app and the trainer stops seeing your wellness at once. If your goals, availability or calendar change before you approve a program, the app tells you and you decide.

This copy is also what the Coach in the web portal can read to answer your questions, but only if you give it a separate consent: see “AI Coach” below.

Food diary shared with your trainer

If you join a team, in the team's sharing settings you can decide whether its trainers also see your food diary. In this section “trainer” also means the team's owner. The “Nutrition diary” switch is on when you join a team and you can turn it off at any time. When it is on, Cloud Sync is active and the team has at least one owner or trainer other than you, your phone uploads a copy of the last 60 days of the diary: meals with foods and grams, calories and macronutrients, water, supplements with dose and time, the meal plan (items eaten, skipped, still to do), your eating pattern, allergens and foods you avoid. The copy also holds your daily targets and what they are based on: your weight goal (target weight in kg, date and weekly change), basal metabolic rate, activity level, training calories and the adjustment for your goal. A trainer of the team reads it, read-only, in the web portal. The first time a trainer opens your food diary you get a notice in the app, with a button to stop sharing.

If you are in more than one team and the switch is on in several of them, turning it off in one team does not delete the copy while it stays on in another: the trainer of the team where you turned it off stops seeing it right away, the trainer of the other team keeps seeing it. The copy on our servers is deleted at once when no team justifies it any more (in every team the switch is off, you have left it or it has no owner or trainer other than you) and when you turn Cloud Sync off; when a plan expires, after 30 days. We cannot delete what a trainer has already copied or noted outside Forgade. The copy is never sent to the AI provider. What a trainer does with the data they see is the trainer's own responsibility: Forgade provides the portal but does not decide how the data is used.

Account data

The device identifier is a random code kept in the iOS Keychain (on Android, a value from Google Play Integrity) and linked to your account; it can survive reinstalling the app. Our legal basis is our legitimate interest in preventing fraud.

We never ask for phone number, physical address, ethnicity, political/religious beliefs, or sexual orientation. The server never sees or stores your card details: payments are processed by Apple, Google, Stripe, and RevenueCat.

Location

If you record an activity with GPS, precise location is used to track the route — it is the core of the cycling computer. With Cloud Sync enabled, the track is also uploaded to our storage. To display the map (including street/topographic tiles and rain radar), the app downloads tiles directly from your device from map providers (Thunderforest, Mapbox, OpenTopoMap) and the weather radar (RainViewer): the portion of the map you are viewing is transmitted to these services to provide the imagery, not to identify you.

When the app collects it. The app collects your precise location (GPS) while you use it and during an activity you start, even when the screen is off or the app is in the background, to record the route, speed, distance and elevation of your outdoor activities and to show where you are on the map. On Android a notification stays visible while it records, and the app does not ask for the “all the time” location permission. Your route is stored on your phone. Your position is sent to our servers only for the features you use: directions, the weather along a route, Beacon live sharing and Cloud Sync, each described on this page.

For the weather, the app asks Open-Meteo for the conditions and forecast at your position and for past days. If you tap “Show the day's heat” on an imported activity, it sends NASA POWER the start point and the day of that activity. For the forecast along a route, up to 20 points of the route with their estimated time, rounded to about 1 km, go to our server, which asks MET Norway for you without passing on your name or email.

Directions (Lite and Pro plans). When you search for a place to navigate to, the app sends our server the words you type and, when it has it, your current position, to rank the results near you. When you ask for a route, and again when you leave it and the app recalculates it, the app sends our server your current position, the destination and the travel mode (bike, walking or car). Our server asks Mapbox, our directions provider, for the results, with our own access key: Mapbox receives those words and coordinates and sees our server, not your name, email address or IP address, and handles them under its own privacy policy. Our server does not store the words or the coordinates: it only records that you made a request, to apply the usage limits of your plan.

No advertising. We do not use your location, or your health data, for advertising, including personalised ads, and we do not sell it. The app contains no third-party advertising or analytics SDKs.

Using location is always your choice: most of the app (gym, nutrition, coach) works without ever granting this permission.

Bluetooth, notifications, camera and Tasker

Bluetooth. The app uses Bluetooth to find and connect to the sensors you choose, such as heart rate monitors and cadence, speed or power sensors, and to show their readings during your activity. It scans for nearby devices when you tap search, and reconnects to sensors you have already paired. Android calls this permission “Nearby devices”: the app does not use Bluetooth to work out your location. On Android 11 and earlier the system requires the location permission to scan for Bluetooth devices: the app uses it only to find nearby sensors when you tap search, and does not record or store your location for this. Sensor readings stay on your phone, except as described elsewhere on this page (for example Cloud Sync or Beacon).

Notifications. The app sends you notifications for the alerts you turn on: the end of your rest timer in the gym, heart rate alerts, water and hydration reminders, and your weekly summary. The notifications are created on your phone: nothing is sent to our servers or to anyone else to show them.

Camera. The camera is used only when you open the barcode scanner in the nutrition diary. The image is used on your phone to read the barcode: it is not saved or sent. Only the barcode number is sent to Open Food Facts to look up the product, as described above.

Tasker and Automate (Android). If you create an automation that starts a Tasker task, the app asks Android for permission to run Tasker tasks, and it runs only the tasks you choose, for example when an activity starts or ends. The text you set for a task goes to Tasker or Automate on your phone and can include the data you choose to put in it, such as your position. Forgade does not send it to us or to anyone else for this; what your task does with it is up to you.

Services contacted directly from your device

To work, the app and some pages of our site contact a few services directly from your phone or browser, without passing through our servers. Each of them sees your IP address and the request itself, and handles it under its own privacy policy.

• Maps in the app. OpenFreeMap, OpenTopoMap and Esri (satellite imagery) and, with the Pro plan, Thunderforest and Mapbox, for which the app asks our server for the access key. They receive the requests for the map tiles of the area you are viewing. On iPhone, the Apple Maps styles are drawn by Apple, under Apple's privacy policy.
• Rain radar and weather. RainViewer, Open-Meteo and NASA POWER, as described under “Location” above.
• Food data. When you scan a barcode or search for a food, the app asks Open Food Facts with the barcode or the words you type, and loads the product's picture from its servers.
• Exercise pictures and animations. They are loaded from media.forgade.com, our own domain, which Cloudflare serves for us.
• Purchases. The purchases library of the app contacts RevenueCat and the store you pay with (App Store or Google Play).
• Sign in and device check. If you sign in with Apple or Google, the app contacts them directly. On Android, the app also asks Google Play Integrity for the device check that prevents welcome credits from being claimed twice.
• Our website. The fonts of our site are served by us, not by Google. In the web portal, if you turn on the GPS map on an activity, your browser loads the Mapbox map library from Mapbox and then the map from Mapbox or, when Mapbox is not used, the tiles from OpenTopoMap, Esri, OpenStreetMap or CARTO. The public Beacon page loads its map library from unpkg.com and its map from OpenFreeMap or, with the Pro plan, Mapbox: whoever opens a Beacon link makes their own browser contact those services.

Live location sharing (Beacon)

Beacon works only while you have switched it on in the app. While it is on, the app sends our server your current position and the time of the fix, the route so far, distance, duration, speed and heart rate, and a public link is created. When you switch it on you choose how long the link stays valid: 1 hour, 4 hours, 24 hours or Never. For as long as the link is valid, every recording you start sends your position by itself, with nothing else to start: with Never, that means every recording, until you switch Beacon off. Anyone who has the link can see, without an account, your display name, your position, distance, time, speed, heart rate and, unless you hide it, the route; the first 250 metres from the start are not shown. If the app sends no update for 5 minutes (for example because it was closed or has no signal), your position stops being shown, on the public page and to your teammates, and it is shown again when the app starts sending updates again. If you are in a team, your teammates see your position and your gap from them only if you share it in the team's sharing settings, and never the route. We keep only the latest live session: its last position stays on our server, not shown, until you switch Beacon off or, if you chose a duration, the link expires, and then it is deleted; with Never it stays until you switch Beacon off. It is also deleted with your account.

Cockpit automations (webhooks)

Cockpit automations (Lite and Pro): if you create an automation, when you hold its button Forgade sends a request to the address (webhook) you chose. The address and any headers stay only on your phone, are left out of backups and never go through our servers. The message contains only the data you decide to include (event, time, automation name and, if you choose, sport, distance or position). You choose the service that receives the request, and it handles the data under its own privacy policy.

Phone calendar

The app has two calendar options. Both are off by default, and Forgade asks your phone for access to your calendars only when you turn one of them on. You can turn each off at any time.

Using your commitments. If you turn on “Use my calendar commitments” and choose which calendars to read, the app reads from them only when each commitment starts and ends and whether it lasts all day. It never reads titles, places, notes or guests. The app turns those times into the hours you are busy on each of the next 90 days, and the Coach plans your sessions around them. They are not saved on your phone: the app reads them again when it needs them. When you use the Coach in the app, those hours (times only, never titles) are sent to the AI provider described below as part of the context of your messages. If Cloud Sync is on, they are also uploaded, as times only, with your planning context; the Coach in the web portal and the programs prepared for your trainer take them into account, and they are part of the planning context that your trainers see if you join a team and share your activity history. The copy follows the same retention as the rest of Cloud Sync. Turning the option off stops the reading at once, and the hours in the cloud copy are replaced at the next sync. Legal basis: your consent (the switch).

Writing your sessions. If you turn on “Write my sessions to the calendar”, the app creates a calendar called Forgade on your phone and writes your planned sessions in it, with their title and day. It updates them when a session changes and removes them when it is cancelled or moved away. It never changes your other calendars. This data does not pass through our servers, and the list of events it wrote is left out of backups. The calendar is created on the phone itself when the system allows it; otherwise it is created in your default calendar account, and your calendar provider (for example iCloud or Google) syncs it like any other event. Turning the option off deletes the Forgade calendar.

Apple Watch sessions

On an iPhone with iOS 17 or later and a paired Apple Watch, the app can send your structured sessions (the ones made of steps, such as intervals) to the Workout app on your Apple Watch, using Apple's WorkoutKit. It does so for a session only when you tap “Send to Apple Watch” or, if you turn on “Send structured sessions to Apple Watch” in Settings, for the structured sessions of the next 7 days. Both are off until you use them, and the system asks for your permission the first time; you can withdraw it in the Watch app, under Workout.

What the app sends to the Watch is the structure of the session: its title and day, the sport and whether it is indoors or outdoors, and its steps, each with its name, its duration or distance, the repeats and, where Apple allows them for that sport, target ranges for power, heart rate, cadence or speed. The app calculates the ranges on your phone from your thresholds (such as FTP or maximum heart rate); the thresholds themselves are not part of what is sent. The session goes from your phone to your Watch through Apple's own sync and does not pass through our servers.

What the app reads back is limited to what it needs to keep things in order: the sessions it scheduled itself (their identifier, their day and whether Apple marks them as completed) and, in Apple Health, the identifier of the session a workout was started from, so that the session is marked as done in your diary. It cannot see sessions scheduled by other apps, and reading workouts from Apple Health follows your Apple Health permissions.

Forgade keeps no copy of these sessions outside your phone, and nothing in this section is sent to us by itself. If Cloud Sync is on, the workout you did is uploaded like any other activity, and the session counts as done as it does when you complete it in the app. Turning off the automatic sending stops it and removes the sessions it had sent from your Watch.

Health and physical activity

If you authorize it, the app reads from Apple Health / Health Connect: sleep (duration and stages), resting heart rate, heart rate variability (HRV), weight, height and body composition, steps, VO2max, and mood (Apple State of Mind, iOS 18 and later). On Apple Health it also reads active calories. It also reads overnight signals: breathing rate, blood oxygen (SpO2), overnight skin or wrist temperature, and how fast your heart rate drops after exercise. We use them to calculate your recovery score and adjust plans. At each sync the app reads the last 7 days. It also reads your workouts (type, start and end time, distance, calories, average and peak heart rate and the name of the app that recorded them, but not the route), to add them to your diary and to mark your planned sessions as done. The first time it reads the last 30 days, then only what is new since the previous sync; workouts that Forgade itself wrote there are skipped. These data stay on your device unless you turn on Cloud Sync or use the Coach (see below).

On Android, these are all the Health Connect data types the app reads, and what each one is used for. Each value goes to your wellness diary, your body measurements log or your profile on your phone, and stays there unless you turn on Cloud Sync or use the Coach (see below).

• Sleep (sessions and stages): the hours you slept and the time in each stage, in your wellness diary and in your recovery score.
• Resting heart rate: your wellness diary and recovery score, and the resting heart rate in your profile.
• Heart rate variability (RMSSD): your wellness diary and recovery score.
• Respiratory rate, oxygen saturation (SpO2) and skin temperature: the overnight signals (the night's average and, for temperature, the deviation from your device's baseline) in your wellness diary, used in your recovery score.
• VO2max: your profile, where the app uses it to estimate the calories you burn.
• Steps: your step count for each day, and the steps taken during an activity you record, for its step count and cadence.
• Weight: your wellness diary, your body measurements log and the weight in your profile (the most recent one from the last 90 days).
• Height: the height in your profile, from which the app calculates your body mass index (BMI).
• Body fat: your wellness diary and your body measurements log.
• Lean body mass, body water mass and bone mass: your body measurements log (lean body mass as muscle mass, body water as a percentage of your weight).
• Basal metabolic rate: your body measurements log.
• Exercise sessions, distance, total calories burned and heart rate: for each workout recorded by another app, its type, title, start and end time, the app that recorded it, the total distance, the total calories burned, and the average and maximum heart rate over its duration, to add it to your diary and to mark your planned sessions as done. Health Connect works out these totals: the app does not read or keep individual heart rate readings, and it does not read the route.
• Menstruation: only if you turn on the menstrual cycle option (see below).

How we use data from Health Connect and Apple Health. We use it only to provide and improve the features of the app for you: your diary, your recovery score, your plans and the Coach. We do not sell it. We do not use it for advertising, including personalised ads, and we do not use it to decide on credit or lending. We do not transfer it to anyone else except as described in this policy: to the AI model provider, which processes it on our behalf when you use the Coach (see “AI Coach” below); to your own copy in our private cloud storage, if you turn on Cloud Sync; and to the trainers and owners of a team you joined, as your sharing settings allow. Your menstrual cycle is never shared with trainers or team members.

If sending workouts to Apple Health / Health Connect is on, the workouts you record with Forgade (type, start and end time, distance, calories, heart rate and route) are written to Apple Health / Health Connect on your phone. They do not pass through our servers. Sending turns on when you first connect Apple Health / Health Connect, after the system asks for your permission; if you connected before, it stays off until you turn it on. You can turn it off in Settings at any time, and deleting an activity in Forgade also removes it from there.

Menstrual cycle

This is health data of a special category (GDPR art. 9). It is off by default. Only if you turn on the menstrual cycle option in Settings and give your explicit, separate consent, the app reads menstrual flow from Apple Health / Health Connect and estimates the day and phase of your cycle. We use it as context for your recovery score and, if you use the Coach, the Coach receives the cycle day and phase as context only. It is never shown to trainers or team members, even if you share your wellness data with them. You can withdraw your consent at any time by turning the setting off: the cycle day and phase are deleted from your diary on the device, and from the cloud copy at the next sync.

Health conditions you declare

In Profile you can list permanent conditions (for example a chronic one) and in Wellness temporary ones (such as an injury or an illness), each with a short description, an optional body area and optional notes. For a temporary illness you can also pick the type of symptoms (nose and throat; cough, shortness of breath or headache; fever or whole-body symptoms; chest pain, palpitations or dizziness; muscles, joints or tendons), which helps the Coach suggest a gradual return to training. This is health data. We process it only because you choose to enter it so that the Coach takes it into account, which is your explicit consent (GDPR art. 9(2)(a)), and only to generate a safer, more relevant response: the Coach does not diagnose. When you use the Coach in the app, these conditions are sent to the AI provider (see below) as part of the context of your messages. They reach the cloud copy only with a separate switch, and are deleted from it as soon as you turn it off. Trainers in your team see them only if you share your wellness data with them.

When you mark a planned session as skipped you can say why. “Not feeling well” and “Injury or pain” are health data too, and the same rules apply, with the same consent (GDPR art. 9(2)(a)): the reason is optional, and you can skip without giving one. The Coach in the app receives the reason, and the text you may write under “Other” (up to 200 characters), as part of the context of your messages sent to the AI provider (see below). The cloud copy gets only the category of the reason, never the text, and “Not feeling well” and “Injury or pain” only with the separate health switch; turning it off deletes them from the cloud copy at once. Trainers never see the reason, even if you share your program and calendar with them.

Polar connection

If you connect your Polar account (Settings → Cloud & Sync → Polar), you authorize Polar to share your data with Forgade through Polar AccessLink. Forgade only reads: it writes nothing to Polar. The app reads your exercises (sport, start time, duration, distance, calories, heart rate, and the route and the exercise file when Polar has them), your daily activity (steps, calories, active time), your physical information (weight, height, maximum and resting heart rate, VO2max and heart-rate thresholds) and, when your Polar device provides them, your sleep (duration and stages) and Nightly Recharge (heart rate variability and breathing rate). Wherever these data appear in the app, they are marked as coming from Polar.

The access token that Polar gives us is kept only on your phone (and in the backup you make from the app); it is never stored on our servers. Your data goes from Polar to your phone through our server, which only passes it along and keeps no copy of your workouts, daily values, sleep or physical information. Our server keeps only that your account is linked (your Polar user number and a random label we registered you with). It receives no notifications from Polar: the app asks Polar for what is new when you open it or when you refresh. On your phone, Polar data is stored like your other workouts and wellness entries.

Polar data leaves your phone only if you allow it. The switch “Use my Polar data in the Coach and in Cloud Sync” is off by default. While it is off, Polar activities and the sleep and recovery values read from Polar are not given to the Coach, are not sent to the Cloud Sync copy and do not enter your wellness diary. If you turn it on, they are treated like your other activities and wellness data, as described in the Cloud Sync and AI Coach sections, including the AI provider. If you turn it off again, Polar data stops being shared at once, and the copy already in the cloud is removed at the next sync.

To disconnect, use Settings → Cloud & Sync → Polar → Disconnect: the app revokes the access at Polar and deletes the token from your phone, and our server forgets the link. Activities already imported stay in your history until you delete them. You can also revoke the access from your Polar account (account.polar.com). If you delete your Forgade account, the link is deleted with it, and the app disconnects Polar first.

Wahoo connection

If you connect your Wahoo account (Settings → Cloud & Sync → Wahoo), you authorize Wahoo to share your data with Forgade through the Wahoo Cloud API. The app reads your recorded rides (sport, start time, duration, distance, climb, heart rate, cadence, power, calories, and the ride file when Wahoo has it) and your power zones (FTP), which it only shows for information. If you turn on “Send planned sessions to Wahoo”, the app also sends to your Wahoo account the structured cycling and running sessions of your calendar for the next seven days (name, date, steps and targets), so that they show on your ELEMNT; it never uploads your recorded rides. Wherever Wahoo data appear in the app, they are marked as coming from Wahoo.

The access and renewal tokens that Wahoo gives us are kept only on your phone; they are never stored on our servers. Your data goes from Wahoo to your phone through our server, which only passes it along and keeps no copy of your rides, power zones or sessions. Our server keeps only that your account is linked. It receives no notifications from Wahoo: the app asks Wahoo for what is new when you open it or when you refresh. Wahoo states that it may use the data that applications send to its platform for its own business purposes, as described in the Wahoo privacy policy.

Rides read from Wahoo never leave your phone: Wahoo’s terms do not allow Wahoo data to be passed on to third parties, even with your consent, so they are not given to the Coach, are not sent to the Cloud Sync copy and are not shared with trainers, and there is no switch to change this. They stay in your history on the phone until you delete them.

To disconnect, use Settings → Cloud & Sync → Wahoo → Disconnect: the app removes from Wahoo the sessions it sent from today on, revokes the access at Wahoo and deletes the tokens from your phone, and our server forgets the link. Rides already imported stay in your history until you delete them. You can also revoke the access in your Wahoo account settings. If you delete your Forgade account, the link is deleted with it, and the app disconnects Wahoo first.

AI Coach: what happens when you send a message

Every time you use the coach, the text you write (plus relevant workout/health context) is sent at the time of the request to a language model provider to generate the response — nothing else happens until you choose to use it.

Your permission comes first. Before any of your data is sent to an AI service, the app and the web portal show you, on a screen of their own, which data is sent, who receives it (our server and the AI provider, by name, and where it is processed) and what it is used for, and ask you to agree (“Coach AI”). This policy does not replace that permission. Without it nothing is sent and the Coach does not answer. It covers every Coach function that uses an AI service: the chat, the workouts, gym routines and programs the Coach proposes, Coach memory, the Coach in the web portal and the Coach a trainer uses on the data you share with them. The data it covers is described in the paragraphs of this section and in the Health and Cloud Sync sections: your messages and the replies in the conversation; your profile (age, sex, height, weight, body composition, heart-rate and power thresholds; never your name); your activities and gym sessions that you attach or that the Coach looks up; your training load; the sleep, heart rate, heart rate variability, mood, soreness, weight and overnight values stored in the app; the health conditions and symptoms you entered and, only if you turned that option on, your menstrual cycle day and phase; your goals, availability, programs and calendar; and your nutrition diary, targets and supplements when the Coach looks them up. Data imported from Strava is never sent. You can withdraw the permission at any time in Account → Coach privacy in the app, or in Privacy in the portal: sending stops at once. What an AI service has already processed cannot be called back; your saved conversation and Coach memory stay in your account until you delete them with their own switches. We record the permission with its date, the version of the text and the providers you saw; if the text changes or a new provider is added, we ask again.

When your muscle soreness is 4 or 5 out of 5, the Coach compares it with the load of the previous two days (for each session, its duration, ascent or descent, sets and muscle groups). From 3 out of 5 the app also asks where you feel it: you tap the muscles on a body map and each tap sets the level of that area (3, 4 or 5) or clears it, and, if you report them, the Coach receives the areas with their level. The app pre-fills the areas from what you trained in the last 48 hours, at the level you gave your soreness; what is lit when you press Save is what gets saved, and you can skip it. The Coach reads this as data with its date, never as how you feel, and uses it only to propose lighter or moved sessions, which change nothing until you approve them. It does not diagnose.

You choose where the model processes your messages: Europe (data centres in the European Union) or Global (data centres outside the EU, mainly in the United States). The app suggests one based on your phone's region, and you can change it at any time from the app or the web portal. Same model and same credits in both. With Global, the transfer outside the EU relies on the EU–US Data Privacy Framework and the provider's standard contractual clauses.

Coach AI processing. With the Europe setting, your Coach requests are processed only by Microsoft Azure OpenAI (EU DataZone, Sweden Central region), on our own Azure resource, and are never sent to any other provider: if that service is unavailable or at its limit, the Coach shows an error and you can try again, and the request is not routed anywhere else. With the Global setting, if Azure is unavailable the request is automatically routed to backup gateways: OpenRouter (restricted to Azure endpoints with zero data retention) and Requesty. Your content is not used to train models. Microsoft may retain prompts and responses for up to 30 days within the EU solely for abuse monitoring, until the exemption we have requested from Microsoft is approved.

Same protection from every provider. Forgade decides why and how your Coach data is processed; the AI providers process it only on our behalf and on our instructions, never for their own purposes or for advertising, and none of them uses your content to train models. Microsoft (Azure OpenAI) processes it under the Microsoft Products and Services Data Protection Addendum, which is part of the Azure terms, in the European Union for the Europe setting. With the Europe setting no provider other than Microsoft receives your Coach data. With the Global setting only, OpenRouter and Requesty act as backup gateways and only route requests to the model host: OpenRouter is used with endpoints that have zero data retention and do not use your content for training, and processes the requests under its Data Processing Agreement, which is part of its terms of service; Requesty routes to Azure and processes the requests under its own data protection terms. The Coach can also use models from Anthropic (Claude) and Google (Gemini) if we switch them on. Anthropic's own API processes in the United States, so we use it only for the Global setting, under its Data Processing Addendum with standard contractual clauses, which is part of its Commercial Terms; Anthropic does not use API content for training and deletes inputs and outputs within 30 days, unless they are flagged for abuse. Google processes Gemini requests only under its paid-services terms (the Gemini API with billing enabled, or Vertex AI) and its data processing addendum: Google does not use those prompts or responses to improve its products and keeps them for a limited time only to detect abuse. We send them only what a request needs, and we do not send Coach data to a provider that does not give this protection. The Coach screen shows who receives your data before you agree.

The Coach chat works only with cloud coach history turned on (a separate consent, recorded with its date), in the app and in the web portal. You can turn it off at any time, from the app or from the portal; the chat then stops working until you turn it on again. While it is on, the transcript of your conversation, meaning your messages and the Coach's replies and not the workout files or data series attached to them, is stored on our servers, in a store separate from your account data, so the conversation continues between sessions and between the app and the portal. You can delete it in three ways: with “Clear cloud history” in the app or by resetting the conversation in the portal, by turning cloud history off, which deletes it at once (in the portal you first confirm the deletion), or by deleting your account.

The Coach in the web portal is the same conversation as the one in the app, not a separate one: you can start in one place and continue in the other, and the portal also shows the messages written in the app. It needs cloud coach history to be on and a consent of its own, separate from Cloud Sync and from history, recorded with its date and the version of its text. If you turned it on before the latest change to this text (see the date at the top of this page), the portal asks you to confirm it again before you can use the Coach there. To answer a question, the Coach can read, on our servers and only from the Cloud Sync copy: your activities (summary, laps, zones and, when uploaded, the detailed series), gym sessions, profile and thresholds, training load and form, wellness (sleep, heart rate variability, resting heart rate, mood, soreness, weight, overnight signals and the notes you write in the diary), goals (with the date, distance and elevation of the race and a summary of its route: length, elevation gain and main climbs, never the GPS points), weekly availability, rest days, the availability exceptions you set for specific dates, the sessions already on your calendar for the next 90 days (date, sport and planned minutes only, never titles or notes), your program session by session (date, sport, planned minutes and load, instructions, work blocks and the exercises prescribed in gym sessions), the cards of your planned calendar with whether each was done, skipped (with the reason you gave, if you gave one) or moved (for the cards you wrote yourself or imported from another service, only date, sport and planned minutes, never the title) and, if you turned on “Use my calendar commitments”, the hours you are busy in your phone calendar (times only, never titles, places, notes or guests). The health conditions you declared, and the reasons “Not feeling well” and “Injury or pain” for skipped sessions, are included only if you also turned on the separate switch that sends them to the cloud copy. It never reads data imported from Strava, your menstrual cycle (even if you use it in the app), your nutrition diary, the notes you write on sessions, the text you write when you skip a session for another reason or the steps of guided endurance sessions in your programme: only the app has those. The Coach in the portal can also prepare a workout, a gym routine or a new program for you. A proposal changes nothing on your phone: it is kept on our servers, waiting for you, until you approve or reject it in the app or withdraw it from the portal, and it becomes part of your training only if you approve it in the app. The parts it needs are sent to the AI provider described above, in the region you chose, like your messages; what the Coach reads is not kept in the conversation. If Coach memory is on, the Coach in the portal uses it as the app does. You can turn the Coach in the portal off at any time from the Privacy page of the portal or from the app: it stops reading your data at once. The conversation stays until you delete it as described above.

Coach memory (“Persistent memory” in the app) is a separate consent and needs cloud history to be on. While it is on, the Coach can keep on our servers what you choose to carry from one conversation to the next: a dossier (goals, races, preferences, availability, constraints), your active training programme and a short handoff note. The dossier and the programme cannot hold activity data, data series or daily health metrics. When you reset the conversation you can also choose “Save highlights”: the Coach picks goals, decisions and programmes from it and keeps them as notes for later conversations; “Discard all” deletes the conversation and everything kept in memory. All of this is sent to the model provider as context with your requests. Turning memory off deletes the dossier, the programme, the note and the highlights from our servers at once; programmes already saved on your phone stay there.

Technical record of each request. For every Coach request we keep a record with the model used, tokens, cost, credits charged, outcome and timing, the identifiers the model provider assigns to each of its responses, how many model calls and tool calls the request made, and a short code for the version of the instructions used. It never contains the text of your messages or of the Coach's replies. We use it to charge credits correctly and only once, and to investigate errors with the provider (legal basis: performing the contract). It is kept for as long as your account exists and is deleted with it.

Reports. If you report a Coach reply from the app or the web portal, we keep the reported reply, the message that preceded it, the reason and your optional note for up to 24 months, to review reports of harmful or offensive content (our legitimate interest in keeping the service safe, also required by the App Store). If you delete your account, the report is kept but is no longer linked to you.

Diagnostic and crash reports

When you are signed in, the app sends our server technical reports to help us find and fix errors: shortly after each launch, and right away after a crash or a serious error.

A report contains the app and operating-system version and the app's technical log. The log describes what the app was doing (screens opened, sensor connections, synchronisations, errors) and can include values it was handling at that moment, such as a heart-rate reading or the weight read from Apple Health or Health Connect. GPS coordinates, passwords and access tokens are removed before sending, and the log does not contain the text of your Coach messages. On iPhone the report also includes the diagnostics iOS provides to the app (MetricKit): the device model, where in the code the app stopped after a crash, how many times the system closed the app and why, and how much memory it used.

Reports are linked to your account so that we can match them to the problems you tell us about. We use them only to diagnose and fix errors (legal basis: our legitimate interest in keeping the app working and secure). We keep them for up to 12 months; they are deleted earlier if you delete your account.

Feedback from the Home screen

If you send feedback from the Home screen, we store its type, the name you enter, the optional email address and your message. You can send it without an account; if you are signed in, it is linked to your account. We use it only to answer you and to improve the app (legal basis: our legitimate interest), and we may be notified of it by email. We keep it for up to 24 months. If you delete your account, the feedback linked to it is deleted at once; feedback sent without an account is not linked to anyone, so write to us if you want it deleted earlier.

Who we share data with

We do not sell your data. We do not share it for third-party advertising: the app contains no third-party advertising or analytics SDKs.

How long we retain data

• Account, credits, purchase history: for as long as the account exists.
• Cloud Sync data: for as long as the account exists; if a subscription expires, we retain it for an additional 30 days before permanently deleting it from storage.
• Food diary shared with your trainer: until no team justifies the copy any more (switch off, you leave the team, the team has no owner or trainer other than you), you turn Cloud Sync off, plan expiry + 30 days or account deletion.
• Coach history (the transcript): until you clear it, turn cloud history off or delete the account.
• Coach memory (dossier, programme, note and highlights): until you turn memory off or delete the account.
• Technical record of Coach requests (no message text): for as long as the account exists.
• Coach messages at the AI provider (Microsoft Azure): the service does not keep the responses; Microsoft may retain prompts and responses for up to 30 days within the EU, solely for abuse monitoring, until the exemption we have requested is approved.
• Coach messages at other AI providers, only if they are used: Anthropic deletes inputs and outputs within 30 days unless they are flagged for abuse; Google keeps them for a limited time solely to detect abuse.
• Polar connection: the link until you disconnect or the account is deleted.
• Wahoo connection: the link until you disconnect or the account is deleted.
• Directions and place searches: our server does not keep the words or the coordinates, only that a request was made, to apply the usage limits of your plan; Mapbox handles them under its own privacy policy.
• Live Beacon position: until you switch Beacon off or, if you chose a duration, the link expires (with Never, until you switch it off); only the latest session is kept, and it is deleted with the account.
• Reports of Coach replies: up to 24 months from the report, detached from your account if you delete it.
• Diagnostic and crash reports from the app: up to 12 months, deleted with the account.
• Feedback from the Home screen: up to 24 months, deleted at once with the account.
• Subscription records (plan, period, store): deleted with the account. The subscription itself, at Apple or Google, is not cancelled by deleting the account.
• Account deletion: immediate and irreversible, also deletes Cloud Sync data from storage — see account deletion.

Security

All communications between app, web portal, and server occur exclusively over HTTPS. Cloud Sync storage is private: it is not accessible from a browser or directly by the language model provider.

Your rights

You can download a copy of everything the server retains about your account from the app (Settings → Export data) and delete your account at any time, from the app or from this page: account deletion.

Deleting your account does not cancel a subscription bought through the App Store or Google Play: those stores bill you, and only you can cancel it, from your Apple or Google account. The app and the deletion page remind you before you delete the account and link to where you cancel; if we cannot tell which store you used, they show both.

For any request regarding your data — access, rectification, portability, objection — write to [email protected].

Not a medical device

Information about fitness, recovery, and nutrition provided by Forgade is for informational purposes only and does not substitute for professional medical advice.