Privacy for families
Updated 2026-08-15
KlusQuest keeps profiles, missions, reward pots, savings goals and game progress on the device unless the family enables optional sync. Sync uses an anonymous account and the documented EU-hosted processor; the separate Firebase statistics switch is off by default and is not required to use the app.
Privacy choices should be visible before a family turns on a service. The full policy explains optional photo proof, sync, the limited event allowlist, deletion and what changes when statistics are enabled; this page is only a route into those exact decisions.
Turn a clear family agreement into missions children can complete and parents approve.
Plan at a glance
| First check | Read the exact claim and follow its source before relying on it |
| Useful outcome | A parent can tell what is documented, optional or outside our control |
| Boundary | This page does not replace the privacy policy, Apple documentation or professional advice |
A practical checklist
- 1 — Read the current privacy policy and identify the feature the family plans to enable.
- 2 — Keep local use when linked devices are unnecessary, or review the documented sync fields before linking them.
- 3 — Decide separately whether optional photo proof is appropriate for a particular mission.
- 4 — Leave statistics off unless the parent accepts the listed Firebase data and processing boundary.
- 5 — Use the in-app deletion route or support process when the household should be removed.
Example for the first week
Profiles and missions can stay local; enabling family sync sends the documented household records to the EU-hosted sync service.
Common question
Does KlusQuest need a child's email address or bank account?
No. Sign-in is anonymous, and the pocket-money feature is a virtual family record rather than a bank account, card or payment service.