Look at the permission list of a typical app in the broader "family safety" category and a pattern shows up quickly: location, browsing history, app usage, sometimes contacts or message content — often bundled together regardless of which specific feature a family actually wants to use.
Why that pattern exists
Bundling more data collection into one app is often a business decision as much as a product one — more data supports more features to sell, and "just in case a parent wants it later" is an easy justification to reach for. The cost of that bundling falls on the family: broader data collection on a child’s device, whether or not any single feature is actually being used.
Where WakeKids draws the line instead
- It collects what one specific feature — the remote wake-up alarm — actually needs, and nothing added "for later."
- No location, no browsing history, no contacts, no message content, no microphone access.
- No ads and no third-party advertising SDKs, which removes an entire category of data-sharing that many free apps rely on.
- A camera permission exists for exactly one purpose — scanning the pairing QR code — and nothing is stored from it.
What to take from this
This is not a claim that every app in the category is doing something wrong — some families do want the broader feature set. It is a reason to actually read what an app requests before installing it on a child’s phone, rather than assuming narrow scope is the default. It usually is not.