This Privacy Policy explains how personal data is collected, used, and shared when you use the Athletics AI mobile application (the “App”) and the website athleticsai.app (together, the “Service”).
Please read it alongside our Terms of Service.
1. Who is responsible for your data
The controller of your personal data is:
Jelle Heijne, trading as Athletics AI Boschdijk 409 5621 JC Eindhoven The Netherlands
Email: musclemindai@gmail.com
We have not appointed a Data Protection Officer, as we are not required to do so under Article 37 GDPR. All privacy questions and requests go to the email address above.
2. Who this policy applies to
This policy applies to everyone who uses the Service, anywhere in the world. It also applies to athletes whose jumps a coach analyses with the Service, even if they do not have an account themselves (Section 7.1). Some sections grant rights that apply only to people in specific regions — the European Economic Area and the United Kingdom (Section 12), and certain U.S. states (Section 13).
3. What we collect
3.1 Account data
Depending on how you sign up, we collect:
| Sign-up method | Data collected |
|---|---|
| Email and password | Email address, encrypted password credential |
| Sign in with Google | Email address, name, Google account identifier |
| Sign in with Apple | Apple account identifier, and email address (or Apple’s private relay address if you choose to hide it) |
| Anonymous / guest | A randomly generated account identifier only — no email or name |
Authentication is handled by Firebase Authentication. We never see or store your password in readable form.
3.2 Athlete profile
Information you enter about yourself so that analyses can be calculated and interpreted:
- Name or display name
- Date of birth, from which we calculate your age
- Height and weight
- Gender
- User type — athlete, coach, or supporter
- Experience and skill or competition level
- Personal bests
- Jumping (take-off) leg
- Focus areas and training goal, chosen from preset options
Your date of birth is required, because we need it to apply the age rules in Section 14. Everything else is up to you, though these details make your feedback more accurate and more relevant, and leaving them out may reduce its quality.
If you use the App as a coach, the details you enter for an analysis may describe the athlete you are analysing rather than yourself. They are processed in exactly the same way.
3.3 Video and analysis data
- Video you record in the App or select from your device’s photo library. Video may contain your image, your surroundings, and any audio recorded by your device. We do not analyse audio.
- Derived analysis data produced from that video: detected body-joint positions and angles, timing and phase data, calculated metrics, scores, and written feedback.
- Snapshots — still images extracted from your video at key phases of the movement, so that you can see your own position at each moment. These are full frames from your video. They will normally show your face, and anything or anyone else that was in shot.
Section 5 explains what happens to your video and your snapshots. Section 6 explains how snapshots are also used to improve our models, and how to switch that off.
3.4 Subscription data
Subscriptions are sold through the Apple App Store and Google Play, and managed for us by RevenueCat. Apple and Google process your payment; we never receive your card, bank, or billing details. We receive subscription status, product purchased, purchase and renewal dates, store transaction identifiers, and an anonymous app user identifier.
3.5 Usage and diagnostic data
- Usage stats (via Mixpanel): screens viewed, features used, actions taken in the App, session timing, a pseudonymous device or user identifier, device model, operating system version, app version, and coarse country-level location derived from your IP address. In the EEA, the UK, and Switzerland, usage stats are off until you allow them. Elsewhere they are on unless you switch them off. See Section 12.4.
- Onboarding step counts (via Google Firebase): daily totals of how many people reach each step of the App’s first-run journey. We store only the totals — no user ID, device ID, answers, or exact time. See Section 12.5.
- Crash and performance diagnostics (via Firebase Crashlytics): crash traces, error logs, device state at the moment of a crash, device model, OS version, and app version.
3.6 Support correspondence
If you contact us, we keep your message, your email address, and our reply.
We do not collect your precise location, contacts, calendar, health-app data (Apple Health, Google Fit), or device sensor readings.
4. Why we use your data, and our legal basis
| Purpose | Data used | Legal basis (GDPR) |
|---|---|---|
| Create and maintain your account | Account data | Performance of a contract (Art. 6(1)(b)) |
| Analyse your video and return results | Video, snapshots, analysis data, athlete profile, results of earlier analyses | Performance of a contract (Art. 6(1)(b)) |
| Store and display your snapshots so you can see your own technique | Snapshots | Performance of a contract (Art. 6(1)(b)) |
| Store your analysis history so you can track progress | Analysis data, snapshots, athlete profile | Performance of a contract (Art. 6(1)(b)) |
| Provide and verify your subscription | Subscription data, account identifier | Performance of a contract (Art. 6(1)(b)) |
| Improve the accuracy of our movement-analysis models (Section 6) | Snapshots, analysis data, and non-identifying profile attributes | For users 18 and over: legitimate interests (Art. 6(1)(f)) — developing and improving the analysis technology the Service depends on, subject to your unconditional right to opt out at any time. For users under 18: consent of a parent or guardian (Art. 6(1)(a)), asked for separately and withdrawable at any time |
| Keep the App stable and fix crashes | Diagnostic data | Legitimate interests (Art. 6(1)(f)) — keeping the Service functional and secure |
| Prevent abuse, fraud, and misuse of the Service | Account data, usage data | Legitimate interests (Art. 6(1)(f)) |
| Understand how the App is used and improve it | Usage stats (Mixpanel) | Consent (Art. 6(1)(a)) in the EEA, UK, and Switzerland; legitimate interests (Art. 6(1)(f)) elsewhere |
| Find out where people get stuck while setting up the App | Onboarding step counts | Legitimate interests (Art. 6(1)(f)) — measuring, in aggregate, whether the App’s setup works (Section 12.5) |
| Respond to your support requests | Correspondence, account data | Legitimate interests (Art. 6(1)(f)) |
| Send service messages (e.g. security or billing notices) | Email address | Performance of a contract (Art. 6(1)(b)) |
| Comply with legal, tax, and accounting obligations | Subscription and account records | Legal obligation (Art. 6(1)(c)) |
Where we rely on legitimate interests, we have weighed those interests against your rights and concluded they do not override them. You can object at any time — see Section 12.
5. How we handle your video and snapshots
Video is the most sensitive thing you give us, so we are specific about it.
-
Upload. Your video is uploaded over an encrypted connection to Google Cloud Storage in the Netherlands (europe-west4).
-
Analysis. The video is processed by automated computer-vision models (person detection and pose estimation) running on Modal. These models locate your body and joints in each frame. They do not recognise faces and do not identify who you are.
-
Interpretation. To generate written technique feedback, we send the following to Anthropic’s Claude API:
- the five snapshots of the key phases of the jump — full frames from the video, which will usually show the athlete’s face;
- the numerical analysis of the jump: joint positions, angles, timings, metrics, and scores;
- the profile details listed in Section 3.2, except name: age, gender, height, weight, user type, experience, personal best, jumping leg, focus areas, and goal;
- results of earlier analyses in the App — their metrics and written feedback, but not their snapshots.
Your name, your email address, your account identifier, and the video itself are never sent to Anthropic. Anthropic processes this data on our behalf only to produce the feedback. Under its commercial terms it does not use it to train its models, and it retains it only for the limited period those terms allow.
-
Deletion of the video. Your video file is automatically deleted within 24 hours of upload. We do not keep the footage.
-
What is kept. Before the video is deleted, we extract the derived analysis — metrics, joint data, scores, feedback — together with snapshots: still frames showing your position at key phases of the movement. The analysis and its snapshots are stored in your account so that you can review your history and see your own technique, and are kept until you delete your account.
Snapshots are photographs of you. They are full frames taken from your video, so they will usually show your face, your clothing, your surroundings, and anyone else who was in shot. Unlike the video, they are not deleted after 24 hours — they stay for as long as your account exists, because they are what the App shows you when you open a past analysis.
We do not perform facial recognition, biometric identification, or any processing intended to uniquely identify you from your body or face. The pose data we generate describes how you move; it is not used as an identity signal.
We do not sell your video, snapshots, or analysis data, and we do not share them publicly. An analysis is visible only to you unless you choose to export or share it yourself. If you share it, that copy is outside our control.
6. Using your snapshots to improve our models
Movement-analysis models get better when they learn from real athletic movement. Unless you switch it off, we use the snapshots and analysis data stored in your account to develop and improve the models that power the Service.
To be precise about what this involves: we do not make a separate copy for training. Training runs against the analyses already stored in your account, and reads only those belonging to users who have not opted out.
Your uploaded video is never used for training — it is deleted within 24 hours, as described in Section 5. Only the extracted snapshots and analysis data are used.
6.1 Your choice
This is on by default. Unless you switch it off, your snapshots and analysis data may be used to improve our models.
You can switch it off at any time, for any reason, in Profile → Settings → “Help improve Athletics AI”. You do not have to give a reason, we will not ask you to justify it, and it costs you nothing: every feature of the Service works identically either way. We tell you about this setting when you first open the App, before you upload anything.
If you are under 18, it works the other way round. Nothing from your account is used for model development unless your parent or guardian has separately agreed to it. We ask them that as its own question — it is not part of setting up the account or accepting our terms — and either of you can withdraw it at any time in the same settings screen. If you reach 18 while using the App, your setting simply stays as it is — on if it was on, off if it was off — and from then on it is yours to change at any time.
6.2 What switching it off does
- Your snapshots and analyses are excluded from all model development from that moment on.
- Your snapshots are not deleted, and your analysis history is unaffected. They remain in your account and the App continues to display them — switching off changes what we may do with them, not what you can see.
- Models already trained cannot be un-trained. A model that has already learned from a dataset cannot have one contribution surgically removed, and we will not claim otherwise. Trained models do not store or reproduce your snapshots.
- If you want the snapshots gone as well as excluded, delete your account (Section 11).
6.3 Limits we hold ourselves to
- Under-18 accounts are opt-in only. Snapshots from an account registered to someone under 18 are never used for model development unless a parent or guardian has specifically agreed. Refusing costs nothing, and the App works identically either way.
- Never for athletes analysed by a coach. Analyses a coach uploads of an athlete other than themselves are never used for model development, whatever the coach’s setting says. Those athletes have not chosen our settings, so we do not rely on them.
- Internal use only. Snapshots are not sold, licensed, or published, and are not used to train any third party’s models, including Anthropic’s. Apart from the processors that help us run the Service (Section 9) — such as Anthropic when generating feedback — they are not shared with anyone.
- Never used to identify you. We do not train identification, facial-recognition, or re-identification systems, and we do not use your snapshots to profile or target you.
- Never published. Your snapshots will not appear in marketing, on our website, in app-store listings, or in any public material. If we ever want to use an image of you publicly, we will ask you first and you are free to say no.
- Deleting your account removes your snapshots from our systems, and with them any further use for model development.
6.4 What we do not do
We do not use your snapshots for advertising, and we do not use them to make any decision about you.
7. Athletes analysed by a coach, and other people in the video
7.1 Coaches analysing their athletes
Coaches can use the App to analyse athletes they coach. When they do, the athlete in the video is not the account holder, and the coach is responsible for:
- having the athlete’s permission to film and upload the jump — and, if the athlete is under 18, a parent’s or guardian’s permission;
- telling the athlete that their jump is analysed with Athletics AI and where to find this policy; and
- entering accurate details about the athlete.
The athlete’s snapshots and details are processed in the same way as any other analysis, including being sent to Anthropic to generate feedback (Section 5), and are kept in the coach’s account until the coach deletes it. They are never used for model development (Section 6.3).
An athlete, or their parent or guardian, can contact us at the address in Section 1 at any time to have analyses of them deleted, even though they do not have an account.
7.2 Other people in shot
Only the athlete performing the movement is analysed. Other people who happen to be in frame — training partners, coaches, spectators — are not analysed or identified.
However, snapshots are full frames, so anyone standing in shot will appear in the stored image, and that image is kept for as long as your account exists.
You are responsible for the video you upload. Only upload video that you are entitled to upload. If other identifiable people appear in it, make sure you have their permission (or, for a minor, their parent’s or guardian’s permission), as required by the law where you are filming. Do not upload video filmed in places where filming is prohibited or where people have a reasonable expectation of privacy.
If someone appears in one of your snapshots and objects, contact us at the address in Section 1 and we will delete the affected analysis.
8. Automated processing
Your analysis is generated automatically, without a human reviewing it. This is the core function of the Service, and it produces sports-technique feedback only. It does not produce legal effects and does not significantly affect you within the meaning of Article 22 GDPR.
Analysis output is informational, not professional advice. It is not medical, physiotherapeutic, or diagnostic advice, and it is not a substitute for a qualified coach or clinician. Automated analysis can be inaccurate, particularly with poor camera angles, low frame rates, or obstructed views.
9. Who we share data with
We do not sell your personal data. We share it only with service providers (“processors”) who process it on our instructions, under written data-processing agreements:
| Provider | What they process | Purpose | Location |
|---|---|---|---|
| Google Cloud (Firestore, Cloud Storage, Cloud Run) | Profile, video, snapshots, analysis data, onboarding step counts | Database, image and video storage, backend hosting | Netherlands (europe-west4) |
| Google (Firebase Authentication, Crashlytics) | Account credentials, diagnostics | Authentication, crash reporting | United States |
| Modal | Video frames during processing | Pose estimation compute | United States |
| Anthropic (Claude API) | The five snapshots of the analysed jump, analysis data, profile details (not name), and metrics and feedback from earlier analyses — never the video, name, email, or account identifier | Generating written technique feedback | United States |
| Mixpanel | Analytics events, pseudonymous identifiers, device data | Product analytics | European Union (EU data residency) |
| RevenueCat | Subscription status, store transaction data, app user identifier | Subscription management | United States |
| Apple / Google (app stores) | Purchase and payment data | Selling and billing subscriptions, as independent controllers under their own privacy policies | Global |
We may also disclose personal data where we are legally required to (for example, a valid court order or lawful request from an authority), or where necessary to establish, exercise, or defend legal claims. If the Service is ever sold or transferred, your data may transfer with it; you will be notified before that happens and this policy will continue to apply until replaced.
10. International transfers
Your videos, snapshots, analyses, and profile are stored in the Netherlands. Some processing still takes place in the United States: pose estimation on Modal, feedback generation by Anthropic, authentication and crash reporting by Firebase, and subscription management by RevenueCat.
When personal data leaves the EEA or the UK, we rely on:
- the European Commission’s Standard Contractual Clauses (and the UK International Data Transfer Addendum), incorporated into our agreements with those providers; and
- where applicable, the provider’s certification under the EU–U.S. Data Privacy Framework.
Copies of the safeguards we rely on are available on request at the address in Section 1.
11. How long we keep data
| Data | Retention |
|---|---|
| Uploaded video files | Deleted automatically within 24 hours of upload, whatever your settings say |
| Snapshots (still frames from your video) | Until your account is deleted |
| Analysis results and history | Until your account is deleted |
| Account and profile data | Until your account is deleted |
| Usage stats (Mixpanel) | Up to 24 months, then deleted or aggregated |
| Onboarding step counts | Up to 25 months, then deleted |
| Crash and diagnostic data | Up to 90 days |
| Subscription and transaction records | Up to 7 years, where required by Dutch tax and accounting law |
| Support correspondence | Up to 24 months after the matter is closed |
When you delete your account, your account data, profile, snapshots, and analysis history are deleted immediately from our active systems. Residual copies may persist in encrypted backups for up to 30 days before being overwritten, and we may retain the minimum records required by law (for example, proof of a transaction for tax purposes).
You can delete your account from within the App at Profile → Settings → Delete account, or by emailing us.
12. Your rights in the EEA and the UK
If you are in the EEA or the UK, you have the right to:
- Access the personal data we hold about you, and receive a copy
- Rectify inaccurate or incomplete data
- Erase your data (“right to be forgotten”)
- Restrict processing in certain circumstances
- Object to processing based on legitimate interests, including our use of your snapshots for model improvement (Section 6) and the onboarding step counts (Section 12.5) — switching the relevant setting off is a complete and immediate way to exercise this right
- Data portability — receive your data in a structured, machine-readable format, or have it transmitted to another controller
- Withdraw consent at any time, where processing is based on consent (this does not affect processing already carried out)
- Not be subject to a decision based solely on automated processing that produces legal or similarly significant effects
12.1 How to exercise them
Email musclemindai@gmail.com. We will respond within one month, and will tell you if we need longer (up to a further two months) because the request is complex. We may ask you to verify your identity before acting.
Some rights can be exercised directly in the App: you can edit your profile, change your usage-stats and model-improvement settings, and delete your entire account.
12.2 Complaints
You can lodge a complaint with your local supervisory authority. In the Netherlands this is the Autoriteit Persoonsgegevens (autoriteitpersoonsgegevens.nl). In the UK it is the Information Commissioner’s Office (ico.org.uk). We would appreciate the chance to address your concern first.
12.3 Anonymous accounts
If you use the App anonymously, we hold no name or email for you, which means we may be unable to identify you well enough to act on a rights request (Article 11 GDPR). We may ask for information sufficient to link the request to your account.
12.4 Usage stats and your choices
In the EEA, the UK, and Switzerland, usage stats are off until you allow them. Nothing is sent to Mixpanel before you say yes.
There are two ways to choose:
- During your first analysis. While your first jump is being analysed, we show a one-time card asking whether you want to share usage stats. You can tap “Allow” or “No thanks”. Both buttons look the same, and the App works the same whichever you pick.
- In Settings, at any time: Profile → Settings → “Share usage data”.
If you tap “No thanks”, or close or ignore the card, usage stats stay off. We show the card at most once on each device and do not ask again, but you can change your mind in Settings whenever you like. Your choice is saved to your account and on your device.
We work out your region from the country set on your device. If we can’t tell, we treat you as being in Europe, so usage stats stay off.
Everywhere else, usage stats are on by default under our legitimate interests (Section 4), and you can switch them off at any time with the same setting.
Crash reporting stays on everywhere, because we need it to keep the App working safely.
Model improvement (Section 6) is a separate setting: Profile → Settings → “Help improve Athletics AI”. Your choice about usage stats does not change it, and the other way round.
12.5 Onboarding step counts
Separately from usage stats, the App keeps simple daily totals of how many people reach each step of its first-run journey: the intro screen, each setup question, sign-in, the upload screen, choosing a clip, starting, finishing, or failing an analysis, the usage-stats card, the goal and plan screens, and the paywall shown during setup, including whether a purchase is made there.
What that means in practice:
- Each step has one number per day. When you reach a step, that number goes up by 1. Each step is counted at most once each time you open the App.
- We store only the number. No user ID, no device ID, none of your answers, and no time more precise than the date.
- The totals are stored in Google Cloud Firestore in the Netherlands (europe-west4), with Google as our processor, and are deleted after 25 months.
Why we do this without asking first. We use these totals only to see where people get stuck while setting up the App, so we can fix it. Because we keep nothing but anonymous totals, the effect on your privacy is minimal, and we rely on our legitimate interests (Section 4) rather than your consent. This is why Section 12.4 says nothing is sent to Mixpanel before you agree: the step counts are not Mixpanel, and they are not linked to you.
An honest caveat. To add 1 to a total, your device sends a small request to Google using your normal App sign-in, so the request includes your device’s IP address and your App sign-in ID. Google handles that request as our processor, as it does for every other part of the App, and may record it in its technical logs. Nothing from the request is stored with the totals, and we do not use these requests to find out who reached which step.
How to stop it. Switching off “Share usage data” in Settings, or tapping “No thanks” on the usage-stats card, also stops the step counts. Tapping “No thanks” is the last step we count.
13. Your rights in the United States
If you are a resident of California, Colorado, Connecticut, Virginia, or another U.S. state with a comprehensive privacy law, you may have the right to know what personal information we collect, to access and delete it, to correct it, to obtain a portable copy, and to be free from discrimination for exercising these rights.
We do not sell your personal information, and we do not share it for cross-context behavioural advertising. We do not use your data for targeted advertising or profiling that produces legal or similarly significant effects. There are no advertising SDKs in the App.
You may opt out of the use of your snapshots for model improvement at any time in Profile → Settings → “Help improve Athletics AI”, as described in Section 6.
To exercise these rights, email musclemindai@gmail.com. You may use an authorised agent, and we will verify their authority. You may appeal a decision by replying to our response with the word “Appeal”.
Notice for Illinois and Texas residents: we do not collect or use biometric identifiers as defined by the Illinois Biometric Information Privacy Act or the Texas Capture or Use of Biometric Identifier Act. Our models detect body-joint positions for movement analysis. We do not create face-geometry scans, voiceprints, or any template used to identify an individual.
14. Children and young athletes
You must be at least 13 years old to use Athletics AI. We do not knowingly collect personal data from anyone under 13.
If you are between 13 and 17, you may use the Service only with the permission and supervision of a parent or legal guardian, who must review this policy and agree to it on your behalf. Where the law of your country requires a parent’s consent below a higher age (16 in the Netherlands and several other EU member states), we rely on that parent’s or guardian’s consent.
Snapshots from an account registered to someone under 18 are not used to improve our models unless a parent or guardian has separately agreed to it. We ask this as a distinct question, separate from permission to use the App at all, and it can be withdrawn at any time in Profile → Settings → “Help improve Athletics AI” without affecting anything else. Where a parent has not agreed, or has withdrawn, that account’s snapshots are excluded from all model development.
A parent or guardian may contact us at musclemindai@gmail.com at any time to review, correct, or delete their child’s data, or to close the account.
If we learn that we have collected data from a child under 13, or from a minor without the required parental consent, we will delete it promptly.
Coaches: if you analyse an athlete other than yourself, you must have that athlete’s permission before you upload — and, if they are under 18, their parent’s or guardian’s permission — and you must tell them about this policy (Section 7.1). Analyses of athletes uploaded by a coach are never used for model development, whatever the athlete’s age.
15. Security
We protect your data with encryption in transit (TLS) and at rest, access controls on our backend systems, authentication handled by Google’s Firebase infrastructure, and a 24-hour retention window for uploaded video. Access to production systems is limited to the controller.
No system is perfectly secure. If a data breach occurs that is likely to result in a high risk to your rights and freedoms, we will notify you and the relevant supervisory authority as required by Articles 33 and 34 GDPR.
16. Changes to this policy
We may update this policy as the Service develops. The “last updated” date at the top always reflects the current version. If we make a material change — for example, a new category of data, a new purpose, or a new recipient — we will notify you in the App or by email before it takes effect, and where the law requires it, ask for your consent. A change of this kind will never apply retroactively to video we have already deleted.
17. Contact
Questions, requests, or complaints:
Jelle Heijne — Athletics AI Boschdijk 409, 5621 JC Eindhoven, The Netherlands Email: musclemindai@gmail.com