Any app that touches a child’s phone is worth a few minutes of scrutiny before it gets installed — the permission it asks for at setup is usually a good preview of what it collects for good.
Five questions worth asking
- Does it need location access to do its core job, or is location requested for something unrelated?
- Does it show ads, and does it use third-party advertising SDKs that can track behavior across apps?
- What happens to the data if you delete the account — is deletion actually available, and what is retained?
- Does it request contacts, photos, microphone, or message access beyond what the stated feature needs?
- Is there a plain-language privacy summary, or only a long legal document?
How WakeKids answers these
- No location tracking for the wake-up feature — it does not need to know where a device is to send an alarm.
- No ads and no third-party advertising SDKs.
- Account deletion is available in the app, with a web fallback form; some records may be retained where legally required.
- No access to contacts, photos, or message content. The camera is used only to scan the pairing QR code, and frames are never stored.
- A plain-language privacy summary exists alongside the full policy.
Read further
- Why WakeKids doesn’t track your child’s location — the reasoning, not just the policy.
- The data "family safety" apps collect — how the category norm compares.
- A privacy checklist for kids’ alarm clock apps — a version of this checklist you can copy and use on anything else you evaluate.