Last updated: September 29, 2026
This English translation is provided for convenience. In case of any discrepancy, the Spanish version 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.
This version describes the App from the update released on September 24, 2026. If you have not updated yet, the version installed on your device may keep behaving like the previous one until you do.
The data controller is a natural person, not a company: Run&Gui is developed and operated by a single individual.
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. Messages with your coach do not reach the AI assistant: they are stored in Supabase (section 5) and read by your coach. Section 3.1 explains what happens to the App's chats 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). These are three independent consents: processing your health data (required to complete sign-up), sending it to the AI assistant's provider (optional) and the menstrual cycle one (optional). You withdraw them by writing to us or deleting your account (section 8) |
| 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 responds to you by messages and can adjust your plan when needed. None of this processing produces legal or similarly significant effects on you (Art. 22 GDPR), and you can always contact us.
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, composing your week, 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:
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 leave the session report note empty and not write in the chats: your plan is still generated and adapted without it. Bear in mind that, if you ticked the sending box, your PAR-Q questionnaire and declared health notes travel to the assistant on every generation (item 1 of this list), not only when you write. If you left it unticked, or if you withdraw it later, they stop travelling to the model provider, but they are still used inside our service, in the European Union, to brake or block the sessions that warrant it: what the consent governs is the sending, not the safety of your plan.
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, which an automated test checks every time we run our test suite.
Processing your health data requires your explicit consent. We collect it in the App as independent consents, and we ask for them before asking you anything on those topics:
You can withdraw them at any time by writing to us or deleting your account; withdrawal does not affect the lawfulness of prior processing.
And one important clarification, because it is easy to read it backwards: not ticking (or withdrawing) the sending consent stops the sending to the model provider, not the use of that data inside our service. The block triggered by an affirmative PAR-Q answer, the brake on pain and the step-down on cycle symptoms are computed by our engine on servers in the European Union, with the complete data, whether the sending is open or closed. If you also want us to stop processing it, you can ask us in writing or delete your account; section 7 explains what deleting it altogether means if you have the medical block active.
If you created your account before September 24, 2026, you accepted an earlier version of this consent, which was a single checkbox with a less complete text than this one. We will ask you inside the App as soon as you update to the version released on September 24, 2026. Until you do, your health data stops being sent to the AI assistant's provider; your plan keeps being generated and adapted as normal in the meantime.
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 the European Commission's Standard Contractual Clauses (Implementing Decision (EU) 2021/914) and on the data processing agreement we have with each provider. In the case of the AI assistant, those clauses form part of Anthropic's data processing addendum, whose contracting entity for customers in the European Economic Area is Anthropic Ireland, Limited.
If you would rather your health information did not leave the European Union, leave the second box at sign-up unticked, the one about sending to the AI assistant. Sign-up completes all the same and your plan is generated all the same: what is required to complete sign-up is the first box, the one about processing your data in the European Union, because without the PAR-Q questionnaire we cannot prepare a plan for you. The cycle one is optional too. If you already have an account and you write to us to withdraw the sending consent, we stop sending that data to the assistant's provider from that moment on; your plan keeps being generated by our engine on servers in the European Union.
It is worth knowing when it actually leaves: the AI assistant is also involved on the free tier, in the chat that helps you fill in your profile during your first sign-up; outside that, it is only involved on paid tiers. Not even in that free-tier chat do your PAR-Q, your health notes or your cycle reach the model provider: that chat does not include health data (section 3.1).
We keep your data while your account is active. When you delete your account (see section 8) we delete your data, including health data. If what you want is to withdraw the sending consent without deleting your account, write to us: we will stop sending that data to the AI assistant's provider and will keep it only inside our service, in the European Union, to carry on braking or blocking the sessions that need it (section 4). If you would rather we deleted it altogether, tell us that too, but bear in mind that your plan then loses the information that sustains the PAR-Q block: the block stays on as a precaution and we will no longer be able to lift it, even if you bring us your doctor's clearance. 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). We do not write the content of your health data to our diagnostic logs: not the PAR-Q answers, not your cycle entries, not the pain figures from your reports, not the text you write. Nor do we use third-party analytics. And since the controller is a single person (section 1), there is no company or team behind it: the database is administered by that one person. If you have a human coach, they see your training profile and the health notes recorded in order to train you, but they do not see your PAR-Q questionnaire or your cycle entries. With one exception we would rather tell you about: when your PAR-Q questionnaire triggers the medical block, the server records in its technical log that the block fired and for what reason, without your name or your identifier.
The App is intended for people aged 18 or over. We do not knowingly collect data from anyone under that age.
September 29, 2026. Four statements about the role of the AI and of the coach are corrected. Section 3 no longer says that a person reviews the messages before they are sent to you: on this tier, your coach responds to you directly by messages and can adjust your plan when needed. The same section 3 now says you can always contact us, and no longer that you can always contact your coach: that phrase was not true for the tiers without a coach (Free and Plan). Section 3.1 no longer says the AI assistant is involved in preparing your coach's draft reply: that feature does not exist in the App. As a result, your messages with your coach are no longer listed among what is sent to the assistant; they are stored in Supabase (section 5) and read by your coach, not by the model provider. And section 6 no longer says that the AI assistant is only involved on the paid tiers: it is also involved in the chat that helps you fill in your profile during your first sign-up, which any tier uses, the free tier included. That chat does not include health data, so neither your PAR-Q, nor your health notes, nor your cycle reach the model provider through it.
September 24, 2026. This revision corrects several things the previous version stated that were not accurate, and describes the new consent:
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.