Privacy policy

Two ways to play: a profile under the tutor's account, or the child's own account

Model A (default): the adult creates the account and, inside it, a child profile with a nickname and avatar from a fixed list; the child has no account or email of their own. Model B: if the child already has their own Google account, they can sign in themselves; in that case they do have an account and email, handled by Firebase Authentication just like the adult's account, though in Firestore we never store their email, name or photo. In both models, sign-up requires passing an adult challenge (a simple sum) first — a reasonable-effort measure, not strong identity verification. The child's progress (streak, stars, badges, preferences) is always stored on the device itself; the local-latch PIN (Model A only) never leaves the device. If there was already progress stored on the device before creating the account, it is automatically transferred to the cloud without loss when the first profile is created, with a warning beforehand.

What data we process

Only if there is an active account (Model A or B):

• The adult's email and password, or the email/name/photo of the adult's or child's Google account when signing in with Google. These are handled by Firebase Authentication (Google); we never see or store a password in clear text.
• The child profile's or child account's learning progress, and their nickname and avatar (chosen from a fixed list), to save and sync them in Cloud Firestore (European region). For the child's Google account, Firestore only stores a technical identifier, never their email, name or photo.
• Current status: all of this is already built in code; there is no effective processing of any real user's data until a real Firebase project exists.

What data we do NOT process

We never process the following:

• In Cloud Firestore, no identifying data: no real name, birth date, photo, voice or email — the adult's or the child's. The nickname comes from a fixed list.
• The child's PIN is never stored in the cloud in any form; it lives only on the device (Model A only).
• Neither the adult's email nor the child's (Model B) is copied into the progress database: both reside only in Firebase Authentication.
• We use no analytics, advertising, trackers, or third-party cookies for commercial purposes. One security exception: Google reCAPTCHA v3 protects accounts against automated abuse; it is not used for analytics or advertising purposes.

Legal basis and consent

Model A: consent and control rest with the responsible adult, not the child; the adult gives informed consent before anything is saved in the cloud. Model B: the child themselves signs in, after passing the adult challenge and the consent screen. That challenge is a reasonable-effort measure, not strong identity or age verification; whether it suffices as valid parental consent for a minor's own account (GDPR Art. 8, Spain's LOPD-GDD Art. 7) is a point pending confirmation by a qualified legal professional, not automated review alone. The app targets children below the age of digital consent (14 in Spain, Art. 7 LOPD-GDD), so processing relies on the responsible adult's consent (Art. 6(1)(a) and 6(1)(b) GDPR). There is no profiling, automated decision-making or advertising directed at minors.

Where data is stored and international transfers

Progress and child profiles are stored in Cloud Firestore in a European region and do not leave the European Economic Area at rest. The adult's email and, in Model B, the child's Google account email/name/photo are handled by Firebase Authentication, which runs on Google's global infrastructure and cannot be pinned to an EU region: that may involve an international transfer of that data. Google acts as processor under its Data Processing Addendum, with the Standard Contractual Clauses (SCCs 2021) and, where applicable, the EU-US Data Privacy Framework. Firestore, in turn, never stores that identifying data: only a technical identifier.

Hosting of the web version

The app can be used installed on Android or straight from a browser, at repasosdeprimaria.mrgnlabs.com. The web version is served from Cloudflare, which acts as hosting processor: it handles technical connection data (IP address, browser type, date and time of the request) for a limited time, in order to deliver the page and protect it from abuse. We use no analytics or advertising cookies, and that technical data is never combined with the account or the progress. Information pages like this one are static HTML and run no code in the browser. Apart from hosting, the web version processes exactly the same data as the installed app.

Retention and deletion

Data is kept while the adult account exists. The adult can delete a child profile or close the account from the app; closing the account cascade-deletes all their cloud data and removes the user. Progress stored on the device can be deleted at any time from Settings.

Your rights

The responsible adult may exercise over their account data the rights of:

• Access, rectification and erasure (right to be forgotten).
• Restriction, objection and portability.
• Lodging a complaint with the Spanish Data Protection Agency (AEPD), www.aepd.es.

Security

Each adult can only access the data under their own account (Firestore security rules). Writing to the cloud requires prior email verification. Sensitive actions (deleting data, closing the account, changing email or password) are protected by a parental gate that requires the adult to re-authenticate.

Contact

You can raise any privacy question, or exercise your rights, through the project's GitHub repository. If this policy changes, we will update its date and version and, where the change is substantial, request the adult's consent again.