Privacy policy

This policy explains what Name the Face does with your data, in plain language. It covers the game and this website.
Last updated: 2026-10-11

1. Who we are and what this covers

Name the Face is a friendly game for learning the names and faces of the families in your group. In this policy, “we” means Name the Face. Our first launch is in Spain, in the European Union. This policy explains our data practices and your rights under the EU General Data Protection Regulation (GDPR).

2. What we collect and why

Firebase Authentication holds adult account identifiers and sign-in details. Profiles hold names, processed photos, optional self-authored fun facts, family links and claim state. We record who contributed a profile, its current adult owner, claim events and claim requests, recipient notices (including telling a family that someone added a profile to it) and structured reports so families can correct mistakes. An account is not required to appear in the group’s game.
Any admitted adult can add another adult to the group before that person has joined or agreed. When they join, they can claim the profile and change it, or ask for it to be removed through the profile’s “Report a problem” button. A child can be added only after the adult confirms that a parent or guardian agrees to sharing the child’s name and photo. Contributors do not become members of the destination family. Kids do not create passwords or adult accounts. Their paired device has a technical authentication identity, readiness and revocation state. Children write their own optional fun fact on that device.
We save learning progress and answer history to schedule practice and improve the learning algorithm. Answer records include profile IDs, choices, hints, timing, learning state, app and scheduler versions, time zone and whether play used a grown-up account or kid device. We also store group membership, family links, invitation records and joining times.
To protect groups, we store keyed hashes of blocked sign-in identities, reasons and dates. Rate limits use hashed IP addresses and account IDs, counters and expiry times. Joining records link an account to a family. App Check and reCAPTCHA process security signals; our cloud services also generate operational logs. When the app hits an error, it sends a minimised error report (see section 7). The app has no ads or analytics SDK, and no data-selling or marketing-sharing integration.
If you send an organizer request, we store your email, group type, optional family count and message, language, submission date and a broad device category (mobile, desktop or unknown). We use these only to respond and help set up your group, not for advertising. Requests are private to the Name the Face team and stored in our EU database. We delete them after 12 months or earlier on request at privacy@nametheface.com. Please do not include children’s personal details.

3. Photos and face detection

Uploaded photos are processed in a Cloud Function in europe-west1. A bundled detector finds a face to help crop the image; it does not recognise who you are. Detection is transient: pixels and boxes stay in the function’s memory. No biometric templates, landmarks or detector results are stored or logged, and photos are not sent to an external face-detection service.
We keep a square photo and a tiny, heavily blurred teaser, stripping metadata such as EXIF and GPS. Until your own profile is ready, ordinary browsing shows blurred teasers, not the group’s real photos. During admitted-adult onboarding, a narrow exception shows up to five matching unclaimed adult candidate photos after you confirm your name. Those processed bytes are returned privately, not through a public photo link; relatives’ photos and the full gallery are not unlocked. Paired ready kid devices retain ordinary playable-photo access.

4. Who can see what

Group details and scenery covers are visible through invite links and social previews; never use people’s faces for covers. Published names, family connections and optional facts are visible to active group members and paired kids, with photo readiness gates. Private drafts can be read by their contributor, destination-family adults and the organiser; photo access still requires the applicable private-photo permission. Adults’ claimed names and photos are self-edited; unclaimed adults can also be corrected by their contributor and family. Contributors cannot author facts or manage child devices. Organisers can moderate details and clear, not invent, facts.
Grown-ups can read their own learning progress and their kids’ progress. A kid device can read its own player’s progress. The admin role gives no access to other players’ progress or answer history. Answer logs cannot be read through the app, even by the player. The Name the Face team can use them server-side to tune learning; pseudonymous analysis copies are still personal data.
A suggested name is not identity verification. If the profile’s family has no grown-up who has joined yet, confirming your own candidate profile joins that family straight away with normal grown-up rights: you manage its kids and devices and see their progress. If the family already has a grown-up who has joined, confirming sends a request instead, and nothing changes until one of that family’s grown-ups, or the organiser, approves it. To help them recognise who is asking, they see the requester’s sign-in email address with the request (the requester is told this before sending); it is shown only while the request is pending. Other family grown-ups receive an in-app notice when someone joins and can report mistakes. Organisers can review reports, merge eligible duplicates and reverse a current mistaken claim, revoking affected device access. Claim and report records support this handling; they are not public identity evidence. Family and pairing previews remain limited and expose no gallery.

5. Children and grown-ups

The game is designed for grown-ups first, and kids around six and older can play too. A grown-up adds the kids, manages their profiles and pairs or removes devices. Adding a kid shares their published profile with the group. Please only add a child you are authorised to represent, and explain this sharing to them in a way they understand.
Kids do not sign up themselves. A paired device lets a kid play, browse the group and add their own fun fact, not manage family settings or other players. The legal consent requirements for children in Spain still need review before use by real families.

6. Where data is stored

Our group database is in Firestore’s EU eur3 location. Photo storage and Cloud Functions are in europe-west1. This EU storage choice does not mean all processing happens in the EU. Firebase Authentication, Firebase Hosting’s content-delivery network, Google or Apple sign-in and reCAPTCHA can also process data outside the EU. Error reports are processed by Sentry in the United States.
Their processing is subject to the providers’ terms and data-protection arrangements. We do not promise EU-only processing for those services. Contact us if you need information about the applicable international-transfer arrangements.

7. Services we use

Google Firebase and Google Cloud provide authentication, the database, photo storage, server functions and website hosting. Google reCAPTCHA Enterprise and Firebase App Check help protect the app against misuse. Google sign-in, and Apple sign-in once configured, handle the sign-in method you choose. These services receive the information needed for their role. App stores may also provide their own crash reports.
Sentry (Functional Software, Inc., USA) receives error and crash reports so we can find and fix problems, such as photos that fail to load. Reports contain the error, the app version, the type of device and browser, the screen’s route pattern and coarse counts. We remove names, photos, fun facts, email addresses, invitation and pairing codes, account IDs and anything you type before a report leaves your device. Sentry sees your IP address when receiving a report but is set not to store it. Transfers to the USA rely on the European Commission’s Standard Contractual Clauses.

8. How long we keep data

Group data is kept while the group exists, unless a profile or account is removed earlier. Removing a profile starts cleanup of its photos, progress and answer records, including records about that person in other players’ history. Account deletion also deletes the grown-up’s sign-in and profile. Access changes take effect when removal is accepted; background cleanup is retried if interrupted.
When a claim request is approved, declined or lapses (for example, the requester publishes a separate profile, deletes their account or the profile changes), its notices, including the requester’s email address, are deleted at once or, for a lapse, automatically shortly afterwards. A short decision record (profile, family, outcome, who decided and when) stays while the group exists so a repeat request gets the same answer; it keeps only a coded identifier, not the requester’s account ID, and a grown-up’s ID is removed when they delete their account. An approved request becomes an ordinary claim record. Contributed profiles outside your own family survive your departure or account deletion; deleted creator attribution is cleared. The person (once they claim it), their family or the organiser can correct or remove it. Account deletion still reviews your own family’s children and device access: children stay with another adult, otherwise you must arrange another adult or explicitly review their deletion. Cleanup is retried. Deletion jobs and tombstones expire after seven days; some revoked-access records remain for security. Contribution is not a promise of permanent retention or a waiver of the person’s rights.
Our documented retention policy requires backups and analysis copies to be purged within 30 days. Production database backups and point-in-time recovery are documented with seven-day retention. We cannot recall photos that another device has already downloaded.

9. Your rights and your choices

Under the GDPR, you can request access, correction, deletion, restriction of processing or a portable copy of your data, and object to processing where these rights apply. Where processing relies on consent, you can withdraw it. Withdrawal does not change the lawfulness of earlier processing. You can complain to your national data protection authority, such as the AEPD in Spain.
Use Family for authorised profile edits and device management. Use a profile’s Report action for a duplicate, incorrect details, a request to remove a photo or a mistaken claim; family claim notices also offer reporting. Claiming a profile is not a substitute for consent or proof of identity. Delete your own account in Settings after signing in again; deleting your account does not automatically remove external contributions. For someone else’s information, child data, access, portability or removal requests, contact us. We may need to check identity and authority; the applicable consent and legal basis still require review before real-family use.
Delete your account

10. Cookies and device storage

The web app uses persistent browser storage for your sign-in session. Local storage remembers language, appearance and sound choices, pending email sign-in or method-linking details, return paths, a linking-session check and a paired-device marker. Game navigation remembers player IDs and mode in app memory; sign-out clears the remembered selections. These support app functions, not advertising.
The product website remembers language and appearance without loading the game’s authentication or group data. On the web, Firestore data and downloaded photos are cached in memory, not a persistent roster or photo database. Native apps use device storage for sessions and preferences and private cache files for photos. Sign-in and reCAPTCHA services may use their own browser storage or cookies.

11. How we protect data

Firestore and Storage rules use active membership or a live paired device to restrict access to group profiles, progress and processed photos. Privileged changes run on the server. Callable functions require App Check, and code guessing is rate-limited. Photo downloads use authenticated access rather than public download links. Hosted web connections use HTTPS. These controls reduce risk, but no system can guarantee absolute security. Keep devices and invitations safe.

12. Changes to this policy

We will update this page when our practices change. The date at the top identifies this version. Please check it when deciding whether to use a new feature or share more information.

13. Contact

For privacy questions or to exercise your rights, contact privacy@nametheface.com. Tell us what you need, but please do not send photos, passwords or unnecessary details about children in your first message.
privacy@nametheface.com