RevivoRomână

Revivo Privacy Policy

DRAFT — to be reviewed by a lawyer. Version 2026-09-30. Written from the app's code (see docs/legal/AUDIT.md). Values in double braces are filled in before publishing. The Romanian version prevails.

In short

1. Who we are

The controller is Mihaela-Nicoleta Cernat, Str. Sachelarie Visarion nr. 18, Sector 2, București, România. Privacy contact: privacy@revivo.training. Phone: +40 731 892 420.

2. What we collect and where from

WhatWhere fromWhy
Email, name and account IDGoogle Sign-In or Sign in with Apple (Apple may give a hidden relay address)The account
Birth month and yearYou enter them at the start; they can't be changed laterAge check and sleep and nutrition thresholds
First name, nickname, height, weight, sex, country, profile photo (optional, from your gallery)YouProfile and score calculation
Logs: sleep, training (type, duration, effort), meals and macros, water, recovery methods, mental state, resting heart rate, notesYouRecovery, strain and discipline scores
Calculated scoresYour phoneWhat you see in the app and, only if you choose, in a team or leaderboard
Teams, groups and your roleYour actionsTeam features
Reports and blocksYouModeration
Consent history (what, when, which text version)You and your parentProof of consent (GDPR art. 7)
Parent's email and name (ages 13–15)You or the parentParental consent
Crash reports (device model, version, the error; no name, email or health data)The phone, only with your consentFixing bugs
Country, from your approximate locationThe phone, only if you unlock the local leaderboard and allow locationCountry leaderboard. Coordinates are not kept.

We don't collect contacts, Apple Health or Health Connect data, precise or continuous location, or the advertising ID.

3. Purposes and legal bases

PurposeBasis
Account, profile, teamsContract (GDPR art. 6(1)(b))
Health data and scoresYour explicit consent (art. 9(2)(a) and Romanian Law 190/2018 art. 3). Without it the app calculates no scores.
Sharing with a team or the communityConsent, given with the button that shows exactly what is visible (art. 6(1)(a) and 9(2)(a))
Crash reportsConsent (art. 6(1)(a)); off by default
Parental consentLegal obligation (GDPR art. 8)
Security, abuse prevention, moderationLegitimate interest (art. 6(1)(f)) and DSA obligations
Keeping proof of consent after deletionLegitimate interest in defending claims (art. 17(3)(e))

We make no automated decisions with legal or similarly significant effects on you (art. 22). Scores are informative estimates.

4. Who receives data

We don't sell data or share it for advertising. Only the providers that help run the app receive it, under data processing agreements:

5. Transfers outside the EU

Firebase Authentication and Cloud Functions may process data in the US, under the EU-US Data Privacy Framework and standard contractual clauses. Sentry is Data Privacy Framework certified. BigDataCloud (Australia) receives only approximate coordinates, under standard contractual clauses.

6. How long we keep data

7. Teams, coaches and the community

8. Children

9. Your rights

You have the right of access, rectification, erasure, restriction, portability, objection, and to withdraw consent at any time without affecting earlier processing. Most of these are in the app (Settings → Privacy and Settings → Account). For the rest, write to privacy@revivo.training. We answer within 30 days.

You can complain to the Romanian data protection authority, ANSPDCP, B-dul G-ral. Gheorghe Magheru 28-30, Bucharest, www.dataprotection.ro, or to the authority where you live.

10. Security

Data is encrypted in transit and at rest. Database rules let everyone read only their own data and what others explicitly showed them. On the phone, data is wiped when you sign out, and on Android it is excluded from Google backups.

11. Studies

If we run a study to validate the scores, taking part will be separate, only with a signed form, and nothing from your account will be used without it.

12. Changes

If we change something important, we tell you in the app before it takes effect and, where needed, ask for consent again. The current version carries the date at the top.