Zyphra Privacy Policy
Last updated: 13/11/2026
1. Who is responsible
Daniel Muñoz, an individual, is the controller of the Zyphra app. Contact for any privacy matter: daniel.munoz@zyphra.me
Zyphra has no Data Protection Officer; it is not required to have one.
2. Minimum age
Zyphra is only for people aged 18 or over. If we learn that an account belongs to a minor, we delete it.
3. What data we process, why, and on what legal basis
| Data | Purpose | Legal basis (GDPR) |
|---|---|---|
| Account: email, username, password (stored only as a hash), account id; if you sign in with Google or Strava, that account's id | Create your account and let you sign in | Performance of a contract (Art. 6(1)(b)) |
| Training: workouts (distance, pace, HR, power, cadence, RPE), plans, routines, tests, goals, weight, height, declared max/resting HR, zones and thresholds | Estimate your fitness and build your plan | Performance of a contract (Art. 6(1)(b)) |
| Health (C1): Health Connect/HealthKit data (resting HR, HRV, SpO₂, sleep, steps…), injuries, per-session pain, OSTRC-H questionnaire, health problems, diagnoses, medication, supplements, menstrual cycle and fertility data, risk screenings | Adapt your load and warn you about risks | Your explicit consent (Art. 9(2)(a)). Without it, none of this is stored or read |
| Cloud backup (C2): your profile and private data | Restore them on another device | Your consent (Art. 6(1)(a)) |
| AI (C3): what you type in the chat and the training and fitness data each answer needs, without your name, email or id; images you send for analysis | AI chat, analysis and plan generation | Your consent (Art. 6(1)(a)) |
| Social profile (C4): username, division, score and, for completed workouts, date, type, title, distance, duration and "respects"; followers and squads | Social features | Your consent (Art. 6(1)(a)) |
| Crash reports (C5): technical data about the crash and the device | Fix bugs | Your consent (Art. 6(1)(a)) |
| Security: counter of failed sign-in attempts (stored under a hash, not your plain email) | Block attacks (10 failures in 15 min) | Legitimate interest in protecting accounts (Art. 6(1)(f)) |
| Welcome email: email and name | Send it to you | Performance of a contract (Art. 6(1)(b)) |
Each consent is separate, nothing is pre-ticked, and you can change them at any time in Más → Privacidad y consentimientos. Withdrawing one does not affect earlier processing, but it deletes the data that depended on it (see §6).
Without the health consent, Zyphra does not know about your injuries or health and cannot adapt your plan to them. If you have an injury, an illness or any doubt, see a healthcare professional before training.
Zyphra does not make decisions with legal effects on you and does not profile you for advertising. We do not sell data or show ads. Plans and tips are guidance only: they are not medical advice and do not replace a professional.
4. Where data is stored
- On your device: all your data, in the app's local database.
- In the cloud (only with C2, and the social profile with C4): Google Firebase (Firestore), region eur3 (Europe).
5. Who we share it with (processors and third parties)
| Provider | What it receives | When | Where · safeguard if outside the EEA |
|---|---|---|---|
| Google Firebase (Auth, Firestore, Crashlytics, Cloud Messaging) | Account, cloud backup, crash reports, notification token | Account always; the rest per C2/C5 | Firestore in Europe (eur3). Auth, Crashlytics and Messaging may process data in the US · EU-US Data Privacy Framework |
| Cloudflare (Zyphra's server) | Sign-in, AI, YouTube and email requests. Zyphra keeps no logs of those requests | When you use them | Global network · EU-US Data Privacy Framework and Standard Contractual Clauses |
| Groq | The text of AI requests (no name, email or id). Not used for training and not stored (zero data retention enabled) | With C3 | US · Standard Contractual Clauses (its DPA) |
| Google (Gemini API) | Text and images of some AI requests (no name, email or id). With the service we use, Google may store that content, have humans review it and use it to improve its products | With C3 | US and other countries · EU-US Data Privacy Framework |
| OpenRouter | The text of some plan-generation requests | With C3 | US · adequacy decisions and Standard Contractual Clauses (per its policy) |
| Brevo | Email and name | When sending the welcome email | EU (France) |
| YouTube (Google) | Exercise video searches | When you watch videos | US · EU-US Data Privacy Framework |
| Strava | What is needed to connect your account and import your activities. Strava is responsible for its own data | Only if you connect it | US · Standard Contractual Clauses (per its policy) |
| Open-Meteo | Coordinates and dates for weather | When computing the heat correction | Company in Switzerland (adequacy decision); servers in Europe and North America, the nearest one answers (GeoDNS) |
OpenStreetMap maps (tile.openstreetmap.org) |
Your IP and the map area you view | When you view a map | OpenStreetMap Foundation (UK, adequacy decision); tiles are served from Fastly's global network (US), from the nearest server |
| CARTO maps | Your IP and the map area you view | When you view a workout map | CartoDB Inc. (New York, US) · EU-US Data Privacy Framework and Standard Contractual Clauses |
| Health Connect / HealthKit | Nothing leaves: the app reads from your phone | Only with C1 | Your device |
6. How long
| Data | Period |
|---|---|
| On your device | Until you delete it or your account |
| In the cloud | Until you withdraw C2 or C4 or delete your account: deleted at that moment (if offline, when you next open the app) |
| Health data | Until you withdraw C1: deleted from the phone and the cloud |
| Failed sign-in counter | Deleted on a successful sign-in |
| AI providers | As set by each provider (see §5) |
7. Your rights
You can access, rectify, erase, object, restrict processing, ask for portability and withdraw any consent:
- Export your data (JSON copy): Más → Privacidad → Exportar mis datos.
- Rectify: from the profile screens and each data screen.
- Delete your account (device + cloud + sign-in account): Profile → Cerrar sesión / Eliminar cuenta → Eliminar Cuenta, or via zyphra.me/delete-account.
- Withdraw consents: Más → Privacidad y consentimientos.
- By email to daniel.munoz@zyphra.me. We reply within one month at the latest.
If you think we have not handled your data properly, you can complain to the Spanish Data Protection Agency (www.aepd.es) or the authority in your country.
8. Security
Encrypted connections (HTTPS); the session is kept in the system's secure storage; the cloud only lets your own account read your private data; passwords are stored only as hashes. If a breach affects you, we will notify you as required by law.
9. Changes
If we change this policy we will tell you in the app. If the change affects a consent, we will ask for it again.
10. This website
zyphra.me is hosted on Firebase Hosting (Google): when you visit it, Google receives your IP to serve the page. The privacy and deletion pages use no cookies and load nothing from other sites.