Child Data Notice

Last updated: 2026-07-29. This page's wording is being finalized as part of a legal review; see the note in the file history of this page in our repository.

This notice explains, specifically, how ChannelKeep handles data connected to the children who use a paired device. It works alongside our Privacy Policy and Terms of Service, which cover the account itself.

The one sentence that matters most

Your child does not have an account with us. We never ask their name, their age, or anything that identifies them as an individual. The only thing we know is a device your family owns.

Why there is no child account

We built ChannelKeep around a device, not a child profile:

No child names, ages, birthdates, avatars, or profiles exist anywhere in our systems.
A paired device is stored only with the label the parent gave it (for example, "Kitchen iPad").
Watch history and screen-time data are tied to a random token generated for that device, never to a child's identity.

The trade-off, stated plainly: because activity is tied to a device rather than a child, a device shared by more than one child in a household shows combined history for that device. We accept this trade-off deliberately, because it means we can honestly say we hold no data that identifies an individual child. We do not describe this approach as exempting us from careful handling of children's data -- it does not, and we treat all activity data connected to a device as data that requires this level of care regardless of any exemption that might otherwise apply.

Before a child ever uses a paired device, a parent goes through a sequence of deliberate steps:

Account creation -- a parent creates the ChannelKeep account using their own email.
This notice, accepted explicitly -- a parent must separately acknowledge this child-data notice, distinct from the general terms, before continuing.
A store subscription -- completing a paid subscription through Apple or Google acts as a payment-method-based confirmation that an adult is setting up the account.
Pairing a device -- a parent then takes the deliberate, hands-on step of pairing the specific device their child will use.

Each of those steps is recorded, so the sequence of consent is verifiable after the fact -- but the record itself never contains anything about a child: no name, no age, no fingerprint, nothing that identifies who uses the device.

What is collected once a device is in use

Per-device watch history: which videos, from which parent-approved channels, played on that device.
Per-device screen-time data: how much the device was used, so the parent-facing screen-time features work.
The YouTube/Google connection: playback is embedded through YouTube's own player. When a video plays, the device connects to Google's YouTube service directly, which may set its own cookies and may show ads, per YouTube's terms. We use the privacy-enhanced youtube-nocookie embed mode to reduce this, but it does not eliminate the connection -- see the Privacy Policy for the full disclosure.
Nothing else. No third-party analytics SDK, no crash-reporting SDK, no advertising identifier, and no fingerprinting runs in the kid-facing app.

A parent's controls

From inside the app, a parent can, at any time:

See what is stored for a device -- its label, its watch activity, its screen-time data.
Delete a single device's data immediately.
Delete the entire account, which cascades and removes every device and every activity record immediately.
Export everything held for the account and its devices as a JSON file.

A parent can withdraw consent at any time by deleting the device or the account through the controls above. Doing so removes the corresponding activity data immediately; it does not, on its own, cancel a store subscription -- see the Privacy Policy for how to cancel directly with Apple or Google.

Contact

Questions about how we handle a child's data can be sent to legal@channelkeep.com.