Children's privacy
Last updated 2026-08-27
This is section 4 of the full privacy policy, published separately because Google Play’s Families policy asks for its own URL.
4. Children's privacy (COPPA)
SafeTrace collects location about a child. That is only lawful with a guardian's verified consent, so the consent check is built into the database itself rather than into a screen that could be skipped.
How it works. Before any child location can be collected, read or paired to your account, there must be a consent record on our servers that says a parent or legal guardian affirmed they are the parent or legal guardian, tied to the verified email address on the account. Without that record:
- a child's tracker cannot be paired to the account,
- location and battery rows for it cannot be read, and
- newly arriving location rows are refused at the point of storage.
All three checks run on the server. An app that skipped a consent screen would still be refused.
Withdrawing consent. You can withdraw at any time. Withdrawal stops collection immediately and erases the location and status history that consent covered. The record that consent was given and then withdrawn is kept, because that is the audit trail the rule exists to create; the data it covered is gone.
Email privacy@safe-track.dev to withdraw, or use the in-app control once it ships. The enforcement above is live on our servers today; the in-app consent and withdrawal screens are still being added.
A child's given name is never sent to us at all (section 3), so there is no child profile on our servers to withdraw, export or correct. There is a tracker, and the positions it reported.