Privacy Policy

Effective 18 April 2026 · Last updated 7 October 2026

This Privacy Policy explains what personal data RunBoost collects, why we collect it, how we use it, who we share it with, and the rights you have over it. We take your privacy seriously, particularly because RunBoost processes data about your body, your training, and your location.

Data controller: Erwin Wijnveld, trading as RunBoost ("RunBoost", "we", "us"), Binderserf 8, 6846 AH Arnhem, the Netherlands. Chamber of Commerce (KvK) number 77119509.
Contact: support@runboost-app.com

1. Who we are

RunBoost is an AI-powered training-plan and coaching application for runners. The service is provided by Erwin Wijnveld, a sole proprietorship trading as RunBoost and registered in the Netherlands. When this policy refers to "the Service", it means the RunBoost mobile app, website, any associated APIs, and customer-support channels.

For the purposes of the EU/UK General Data Protection Regulation ("GDPR"), RunBoost is the data controller for the personal data described below, unless stated otherwise.

2. Data we collect

2.1 Account data

Name and email address.
How you sign in. RunBoost has no passwords: you sign in with Apple or with a one-time code we email you. With Apple we store the anonymous identifier Apple gives us; if you chose "Hide My Email", the address we hold is Apple's private relay address, not your real one. With an email code we store your email address and when you last signed in that way. The code itself is stored only as a one-way hash, works once and expires after 10 minutes.
Profile information you choose to provide (date of birth, running experience, race goals and training preferences).
Support correspondence you send us.

2.2 Training and health-related data

Some of the data RunBoost processes is, or could be used to infer, health-related information. Under Article 9 GDPR this may qualify as a special category of personal data. We process this data on the basis of your explicit consent, which you can withdraw at any time. The data includes:

Your running workouts, read from Apple Health (iPhone) or Health Connect (Android).
Per workout: distance, duration, average and maximum heart rate, average pace, elevation gain and calories.
Route data (the GPS trace of a run), used to show the route and to recognise interval sessions.
Your date of birth and resting heart rate, when Apple Health or Health Connect provides them, to calculate your heart-rate zones.
What you tell us yourself during onboarding: weekly distance, easy pace, personal records, goal and race date.
Anything you choose to write to the AI coach, including notes about injuries or how a run felt.

2.3 Data from Apple Health and Health Connect

RunBoost reads your running workouts from Apple Health (HealthKit) on your iPhone, and only after you grant permission in Apple's own dialog. We request read access only: RunBoost never writes anything back to Apple Health. You can withdraw or narrow that permission at any time in iOS Settings → Health → Data Access & Devices → RunBoost.

On Android, RunBoost reads the same kind of data from Health Connect, and only after you grant permission in Health Connect's own screen. We ask to read exercise sessions (runs), distance, calories burned, heart rate and resting heart rate, and your history older than 30 days so your coach can see your recent training. We request read access only: RunBoost never writes anything to Health Connect. You can withdraw or narrow that permission at any time in the Health Connect app → App permissions → RunBoost.

If you use a Garmin, Polar, COROS, Samsung or Fitbit watch, your runs reach RunBoost the same way: that brand's own app writes them into Apple Health or Health Connect, and we read them from there. RunBoost has no direct connection to those brands, and does not use their APIs. Commitments that apply specifically to Apple Health and Health Connect data are set out in Section 12.

2.4 Device and usage data

Device model, OS version, app version, language, time zone.
IP address, approximate location derived from IP.
Crash reports, sent to our own servers (we do not use a third-party crash-reporting service). A report contains the error, where in the app it happened, and the app version.
A push-notification token issued by Apple, so we can send you reminders and coaching notifications on your iPhone. You can switch notifications off in iOS Settings.
Records of the notifications we sent you and whether you acted on them, used to keep from sending the same thing twice.
Records of which sign-up screens you saw in the app and whether you continued, skipped a question or went back, with the app version. These records never contain your answers. We use them only to find out where signing up is unclear, and they are kept with your account.

2.5 Payment data

Paid subscriptions are billed by Apple through your App Store account on iPhone, or by Google through Google Play on Android, and are managed for us by RevenueCat. RunBoost never sees or stores your card details: Apple and Google do not share them with us. We receive an anonymous customer identifier, the product you bought, the transaction identifier and whether your subscription is active.

2.6 Communications with our AI coach

Messages you send to the RunBoost AI coach are processed to generate responses and refine your plan. These messages, together with the model's responses, are stored in your account history. We describe AI processing in more detail in Section 8.

If you report something the coach wrote ("Report" under an answer, under the feedback on a run or under a check-in), we receive the text you reported, the reason you chose and where in the app it was, linked to your account, so we can look into it.

2.7 The waitlist on this website

If you sign up for the waitlist on this website, we collect only your first name and email address, so that we can tell you when RunBoost opens up. We store that on our own server in Germany and we do not use it for anything else. You can ask us to delete it at any time by emailing support@runboost-app.com.

3. How we use your data (and the legal basis)

Purpose	Legal basis (GDPR)
Create your account and provide the Service (generate plans, sync activities, show progress).	Performance of a contract (Art. 6(1)(b)).
Process health-related data to personalise training, adapt load, and support injury recovery.	Explicit consent (Art. 9(2)(a)).
Send the data your coach needs to Anthropic, our AI provider, to generate your plan, run feedback and answers (see Section 8).	Explicit consent, given in the app (Art. 6(1)(a) and 9(2)(a)).
Take payment, prevent fraud, and meet tax/accounting obligations.	Contract and legal obligation (Art. 6(1)(b), (c)).
Send service notifications (plan updates, sync issues, security alerts).	Contract and legitimate interests (Art. 6(1)(b), (f)).
Tell waitlist sign-ups when RunBoost opens.	Consent (Art. 6(1)(a)). You can ask us to remove you at any time.
Debug, secure, and improve the Service.	Legitimate interests (Art. 6(1)(f)).
Respond to legal requests and defend legal claims.	Legal obligation and legitimate interests.

4. Who we share data with

We do not sell your personal data. We share limited data only with:

Laravel Cloud, which hosts the app's servers and database in Frankfurt, Germany.
Resend (Resend, Inc., United States), which delivers the emails the app sends, such as sign-in codes, club invitations and password resets. It receives the recipient's email address and the message.
Microsoft (Microsoft 365), which hosts our support mailbox.
Apple, for Sign in with Apple, App Store billing and delivering push notifications. Apple Health data flows one way only: into RunBoost, never back out.
Google, for Google Play billing on Android. Health Connect data flows one way only: from Health Connect on your phone into RunBoost, never back out, and Google receives no health data from us.
RevenueCat, our subscription-management provider, which receives an anonymous customer identifier and your purchase events. It receives no health or training data.
Anthropic (Anthropic, PBC, United States), the company behind Claude: a third-party AI service that runs the RunBoost coach. Anthropic receives the data listed in Section 8, only after you allow it in the app, and only to generate your plan, feedback on your runs and answers to your questions. It is contractually bound to provide that data the same or equal protection as this policy, and never to train any model on it, in any form, under any circumstances (see Section 8).
Your coach or club, only if you join one in the app. They can see your plan, runs and results, and can adjust your plan.
The partner who referred you, only if you entered their partner code. They see a shortened version of your name, the date you joined and whether you have RunBoost Pro. Nothing else.
Authorities, where required by law, court order, or to protect rights, property, or safety.
A successor in case of a merger, acquisition, or asset sale, in which case we will notify you and ensure any successor honours this policy.

Every service provider on this list may use your data only to provide its service to us, and must provide it the same or equal protection as this policy does. Apple handles Sign in with Apple, App Store payments and push notifications under its own privacy policy, and Google handles Google Play payments and Health Connect under its own privacy policy.

5. International data transfers

RunBoost stores your account and training data in the European Union (Frankfurt, Germany). Anthropic, RevenueCat and Resend are based in the United States. When data is transferred outside the EEA/UK, we rely on the European Commission's Standard Contractual Clauses, adequacy decisions where available, and additional technical safeguards (such as encryption in transit and at rest).

6. How long we keep your data

Apple Health and Health Connect data: stored in your account for as long as it is active, so your coach can reason about your training history. Deleted with your account (see Section 9): deletion is immediate and removes your runs, plans and coach conversations.
Sign-in codes: 10 minutes, stored only as a one-way hash.
Reports about AI text: until we have handled them, and deleted with your account.
Account and training data: for as long as your account is active. When you delete your account, we delete it immediately, together with your runs, plans and coach conversations.
Waitlist sign-ups: until RunBoost opens up and we have contacted you, or until you ask us to delete them.
Backups: purged on a rolling basis (typically within 35 days).
Financial records we must keep for tax purposes: 7 years (Dutch tax law).
Support tickets: up to 3 years after last contact.
Diagnostic data such as crash reports: up to 14 months.
Records of the sign-up screens you saw (Section 2.4): for as long as your account is active, deleted with your account.
RunBoost uses no third-party analytics, and never puts health data from Apple Health or Health Connect into aggregated datasets.

You can request immediate deletion at any time (see Section 9). We may retain a minimal record that you exercised this right.

7. Security

Your data is encrypted in transit (TLS) and at rest, and only RunBoost itself has access to the production systems. No system is perfectly secure. If we become aware of a personal data breach likely to result in a risk to your rights, we will notify you and the relevant supervisory authority as required by law.

8. AI coaching and model training

The RunBoost AI coach runs on Claude, a third-party AI service from Anthropic. To build your plan, give feedback on your runs and answer your questions, RunBoost sends Anthropic the data needed for that answer:

your runs from Apple Health or Health Connect: date and start time, distance, duration, pace, heart rate, elevation gain and calories, so the coach can score them and give feedback;
your first name, and what you fill in: goal, training plan, preferences, personal records and notes (for example about an injury), to build and adjust your plan;
the messages you send your coach, to answer them;
if you joined a club and your coach adjusts your plan with RunBoost's AI assistant: the same data, together with your coach's name, your club's name and what your coach writes about your plan.

The route itself (the GPS coordinates of a run) is never sent to Anthropic, only results we calculate from it, such as whether a run contained intervals.

Nothing is sent to Anthropic until you allow it on the "Share your data with Anthropic?" screen, the first screen after you sign in, before Apple Health or Health Connect is connected. When we change what we send, the app asks you again. Our servers refuse every AI request for an account that has not allowed it. If you decline, or later switch AI coaching off under Profile → AI coaching, we stop sending your data to Anthropic, and the AI features pause until you switch it back on.

No AI training, ever. No opt-in. RunBoost does not train, fine-tune, evaluate, or otherwise use any personal data, any training data, any health-related data, any AI-coach conversation, any data read from Apple Health, or any other user data to develop artificial-intelligence, machine-learning, or similar models, whether our own or a third party's, whether identifiable, pseudonymised, de-identified, or aggregated. There is no opt-in mechanism to allow this. We will never ask you to consent to it, and we will not introduce one in the future. If this commitment ever changes materially, it will only be through a new product with a new privacy policy that you separately sign up for.

Anthropic is contractually bound to the same commitment: no training and no fine-tuning on your data. It keeps what we send only for as long as it needs to return the response and to detect abuse, and then deletes it.

We improve RunBoost using technical data such as response times and crash reports, and the feedback you send us.

9. Your rights

Under the GDPR (and similar laws in the UK, California, and elsewhere), you have the right to:

Access a copy of your personal data.
Rectify inaccurate or incomplete data.
Erase your data ("right to be forgotten"). You can delete your account yourself in the app: Profile → Delete account. Without the app, see how to delete your account.
Restrict or object to processing, including for legitimate-interest purposes.
Port your data to another service in a structured, commonly used format.
Withdraw consent at any time (this does not affect the lawfulness of prior processing).
Lodge a complaint with your local supervisory authority. In the Netherlands, the Autoriteit Persoonsgegevens.

To exercise any of these rights, email support@runboost-app.com. We will verify your identity and respond within one month, extendable by two further months for complex requests as allowed under Article 12(3) GDPR.

10. Children

RunBoost is not directed at children under 16. We do not knowingly collect personal data from children under 16. If you believe a child has provided us with personal data, please contact us and we will delete it.

11. Cookies and similar technologies

This website sets no cookies and runs no analytics or tracking of any kind. There is nothing to consent to, which is why you will not find a cookie banner here.

Two things do reach other parties when you visit, and you should know about them:

Fonts. The typefaces are loaded from Google Fonts, so Google receives your IP address and browser details in order to serve the font files.
Hosting. The site is served by Vercel, which keeps short-lived server logs (including IP addresses) to deliver the site and to protect it against abuse.

The app uses mobile equivalents (device identifiers, secure storage, push tokens) to sign you in, deliver notifications, and diagnose crashes.

12. Apple Health and Health Connect commitments

Health and fitness data that RunBoost reads from Apple Health or Health Connect ("Health Data") is treated more strictly than anything else in this policy. In addition to everything above, and in line with Apple's requirements for apps that use HealthKit and Google's Health Connect permissions policy:

Permission first, and only what we need. We read Health Data only after you grant access in Apple's or Health Connect's own permission screen, and we request only the types we use: on iPhone workouts, heart rate, route, date of birth and resting heart rate; on Android exercise sessions, distance, calories burned, heart rate, resting heart rate and older history. RunBoost asks for read access only and never writes to Apple Health or Health Connect.
Coaching only. Health Data is used to build and adapt your training plan, to score and give feedback on your runs, and to show you your own history. Nothing else.
Never for advertising or marketing. We do not use Health Data for advertising, marketing, retargeting, or any similar purpose, and we never will.
Never sold, never brokered. We do not sell, rent, license or otherwise disclose Health Data to data brokers, advertising networks, or any third party for their own purposes, even if you were to ask us to.
No model training. Health Data is sent to our AI provider, Anthropic, only after you allow it in the app and only to generate your own coaching. It is never used to train or fine-tune any model. See Section 8.
No people reading Health Connect data. Nobody at RunBoost reads the data we receive from Health Connect, except with your permission (for example when you ask us for help), when it is needed for security, or when the law requires it.
Yours to withdraw. Revoking access in iOS Settings or in the Health Connect app stops new data from reaching us immediately. Deleting your account removes the Health Data we already hold.

13. Other third-party platforms

Apple's own privacy policy continues to apply to data held on Apple's side, including in Apple Health and your App Store account, and Google's privacy policy to data held in Health Connect and your Google Play account. If your runs reach Apple Health or Health Connect through a Garmin, Polar, COROS, Samsung or Fitbit app, that brand's privacy policy applies to the data they hold. We recommend you review those policies. You can revoke RunBoost's access at any time in iOS Settings or in the Health Connect app.

14. Changes to this policy

We may update this policy to reflect changes in the Service, in technology, or in the law. When we make material changes, we will notify you in-app or by email at least 14 days before they take effect. The commitment in Section 8 that we will never train AI or ML models on your data will not be weakened by such updates.

15. Contact

Questions, requests, or complaints? Email support@runboost-app.com.

← Back to home