Last updated: September 15, 2026
> This English translation is provided for convenience. In case of any discrepancy, the [Spanish version](https://gcentelles.github.io/runandgui-legal/privacidad/) prevails.
This policy explains what personal data we process in the Run&Gui application (the "App"), for what purpose, on what legal basis, and what rights you have. Please read it carefully: the App processes health data, which the GDPR treats as a special category and which we protect accordingly.
For any question about your data or to exercise your rights, write to that address.
We collect only what is necessary to prepare your training plan and follow up on it:
a) Identification and contact data Full name, email address, phone/WhatsApp.
b) Physical and sports data Age, sex, weight, height, goal, experience, weekly availability, paces, heart-rate/watch data, and the training plan your coach prepares for you.
c) Health data (special category, Art. 9 GDPR)
d) Communications The messages you exchange with your coach inside the App and the messages you write in the App's chats (the one that helps you fill in your profile and the one that adapts your plan). Because you write those messages as free text, they may contain information about your health; section 3.1 explains what happens to them and where they go.
e) Technical and subscription data Your account identifier, your device's push notification token, and your subscription status (active/expired). Payment is handled by Apple: we do not process or store your card details.
We do not use third-party advertising or analytics SDKs, and we do not build profiles from your health data.
| Purpose | Legal basis (GDPR) |
|---|---|
| Creating your account and giving you access to the App | Performance of a contract (Art. 6.1.b) |
| Preparing and delivering your training plan | Performance of a contract (Art. 6.1.b) |
| Generating and adapting your plan automatically (template engine and AI assistant) | Performance of a contract (Art. 6.1.b) |
| Processing your health data (PAR-Q, injuries, cycle) to adapt the plan safely | Explicit consent (Art. 9.2.a), given separately and revocable |
| Sending the AI model provider the text you write in the App's chats, which may contain information about pain or injuries if you choose to share it | Explicit consent (Art. 9.2.a) for whatever part is health data, and performance of a contract (Art. 6.1.b) for the rest |
| Communicating with your coach (messages) | Performance of a contract (Art. 6.1.b) |
| Sending you notices (plan published, coach reply) | Consent (system notification permission), revocable from your device settings |
| Managing your subscription | Performance of a contract (Art. 6.1.b) and legal obligations (Art. 6.1.c) |
Part of the Service is automated: on the free tier the plan is generated automatically from your profile (template engine); on paid tiers an AI assistant helps adapt it; and on the coach tier, a person reviews the messages before they are sent to you. None of this processing produces legal or similarly significant effects on you (Art. 22 GDPR), and you can always contact your coach.
We would rather list what is sent than promise you what is not. A promise about what never leaves can break without anyone noticing the day we add a feature; a list of what does leave forces us to update this policy when it changes.
When the AI assistant is involved (generating your plan, adapting it from the chat, preparing your coach's draft reply, or the chat that helps you fill in your profile), the following is sent to the model provider (Anthropic, see section 5), and nothing else:
1. Your training profile: profile version, age, sex, weight, height, experience, goal, weekly availability, preferences, strength, reference paces and heart rates, logistics and, if you have given your explicit consent for health data, also your PAR-Q questionnaire, the injuries and health notes you have declared or that your coach has recorded in your medical record and, if you consented to its tracking, your menstrual cycle data. The assistant uses them to adapt your plan with all the safety information in front of it (for example, not proposing intervals while your questionnaire has an unresolved yes).
2. Your training plan: the overall structure and the weeks with their sessions.
3. Your recent runs recorded by your watch: date, distance, duration and pace.
4. Your session reports from the last 28 days: for each day, whether the session was done or not, whether it was a rest day you completed, whether you did another activity and of what type and for how many minutes, the actual duration and distance, your perceived effort (RPE from 0 to 10), any pain you logged (0 to 10 and whether it is getting worse), the note you write on the report (up to 160 characters) and whether the report came from your watch. Effort, pain and the note are what let the following week be built from what actually happened; pain, in addition, is what triggers the protocol that holds your plan back.
5. Signals computed on your own device from Apple Health or Health Connect data: fatigue, kilometres in the last week, acute versus chronic load, load ramp, weekly readiness and load relative to plan; and, if you have them, your VO2max and your estimated paces. The rest of the raw watch data (beat-to-beat heart rate, sleep, full activities) is not sent: it stays on your device and only the computed signals travel.
6. The adjustments you make on the Adapt screen: minutes available per day and relative intensity.
7. The text you write, exactly as you write it: your messages in the Adapt chat along with the most recent messages in that same conversation, your messages in the chat that helps you fill in your profile, and the most recent messages you exchange with your coach (so their draft reply has context).
8. The text your coach writes about you, if you have a human coach: the instructions they write when they generate or rebuild your plan (for example, “this season prioritise the long run and drop the intervals”), and the health notes they record in your medical record. That text is written by a person, not by you, and it travels to the model provider just like yours.
Read points 4, 7 and 8 carefully, because they are the ones that affect you most. That text is sent unfiltered. If you describe an ache, pain or injury in it, that information about your health is sent to the model provider. This is not a side effect: the system is designed to read it. If you describe pain, the assistant identifies it and the engine uses it to ease, hold back or stop the relevant sessions, which is precisely what makes it safe to adapt a plan in writing.
If you would rather not send free text, you can use the Controls mode on the Adapt screen (minutes and intensity, no free text) and leave the session report note empty. Bear in mind that, with your health consent, your PAR-Q questionnaire and declared health notes also travel to the assistant (item 1 of this list): if you withdraw that consent, they stop travelling and your plan is adapted without that safety information.
What is never sent: your name, your email address, your phone or WhatsApp number, and the raw activities from your watch. Those fields are excluded by a closed list in the code itself, checked automatically on every change.
Processing your health data requires your explicit consent, which we collect separately and granularly in the App (PAR-Q and menstrual cycle separately) before asking you for that data. That consent also covers sending that data to the AI assistant's provider (Anthropic, sections 3.1 and 6), which is part of how your plan is adapted safely. You can withdraw your consent at any time by deleting your account or writing to us; withdrawal does not affect the lawfulness of prior processing. Without consent for health data it is not possible to prepare the plan safely.
If you created your account before the date of this version of the policy, this sending to the AI assistant is a change with respect to what you consented to: it will not apply to your account until you expressly accept it inside the App.
To provide the service we rely on providers that process data on our behalf, under a data processing agreement (Art. 28 GDPR):
Your coach accesses your profile, your plan and your messages to provide the service.
We do not sell or share your data with third parties for commercial purposes.
Where your data is stored: everything we store, including your health data (PAR-Q, injuries and menstrual cycle), is kept on servers in the European Union (Supabase, EU region). It is not moved anywhere else for storage.
What is processed outside the European Union: some technical providers process data in the United States, and you should know exactly which:
These transfers rely on GDPR safeguards (the European Commission's Standard Contractual Clauses and/or the EU-US Data Privacy Framework), in addition to the data processing agreement we hold with each provider.
If you would rather your health information did not leave the European Union, you can decline (or withdraw) the health consent: the App keeps working with Controls mode and without that safety information in front of the assistant.
We keep your data while your account is active. When you delete your account (see section 8) or withdraw your consent, we delete your data, including health data. We only keep the minimum information the law requires us to retain (for example, records related to tax or commercial obligations) for the legally required periods, blocked for any other use.
You can exercise at any time your rights of access, rectification, erasure, objection, restriction, portability and to withdraw consent:
Deleting your account does not cancel your Apple subscription; to cancel it, go to *Settings › your name › Subscriptions* on your device.
If you believe we have not handled your rights properly, you can lodge a complaint with the Autoriteit Persoonsgegevens (the Dutch data protection authority, autoriteitpersoonsgegevens.nl), the authority of the country we operate from, or with the authority of your country of residence (in Spain, the AEPD, www.aepd.es).
We apply appropriate technical and organisational measures: encryption in transit and at rest, EU hosting, and row-level access control (each user can only access their own data). Your health data is not included in diagnostic logs or third-party analytics.
The App is intended for people aged 18 or over. We do not knowingly collect data from anyone under that age.
September 15, 2026. Section 3.1 is completed with two things the code was already sending to the assistant’s provider and the list did not name: your session reports (including the effort, the pain and the note you write) and the text your coach writes about you (their instructions when generating the plan, and the health notes they record in your medical record). This is not a new processing operation nor a new recipient: same purpose, same processor and same category of data already covered by your health consent; what was wrong was the list, which said “and nothing else” without being complete.
We may update this policy to reflect legal or service changes. We will publish the current version at this same address and indicate the date of the last update. If the changes affect the processing of your health data, we will inform you and, where appropriate, ask for your consent again.