Parent & your privacy.

Your Parent account

YellowHat Parent uses Google sign-in on Android. On iOS, it offers Google sign-in and Sign in with Apple. The authentication provider and Supabase supply account and session information, which can include an email address, provider identifier and profile details. YellowHat does not offer a separate email-and-password login in the Parent app.

Linked devices and remote controls

The service stores device identifiers, display names, platform, last-activity and protection-health information, Parent-device relationships, pairing and recovery records, and device settings. Installed-app information, app selections, ignored words and protection state support device status and paid remote controls.

For linked Android devices, the installed-app catalogue can include package identifiers, app names, selection state and version information.

Alerts and end-to-end encryption

Parent alert rows include routing metadata such as device, category, severity, source app and time. The current Kids app encrypts each alert title and analysis reason for the registered Parent installations before upload. Parent private keys stay in secure storage on those installations, so YellowHat's server cannot read the encrypted title or reason.

Full notification text is off by default. A subscribed parent can enable it for a device only after a privacy warning. Kids then includes full text only for future alerts and protects it with the same end-to-end encryption. Turning the setting off stops future full-text sharing; existing alerts remain until they expire.

During the app upgrade transition, older compatible Kids versions may submit alerts using the previous unencrypted title and reason format. All Parent alert rows expire after 30 days.

Kids can also create a protection alert when Android reports that notification permission is disabled for a selected app. This can identify the app but does not report individual notification-channel state. The protection alert is archived after selected apps pass the check again.

Push notifications and local cache

When notifications are allowed, Parent registers a push token for Firebase Cloud Messaging on Android or Apple Push Notification service on iOS. Visible push messages are generic and instruct you to open Parent; sensitive alert titles, reasons and message text are not placed in the push notification.

Parent encrypts its offline screen cache with a per-installation key in secure storage. Cached alert and device payloads expire after 30 days and are cleared on sign-out. Lock-screen visibility still depends on your phone's notification settings.

Purchases

Parent uses Google Play Billing on Android and StoreKit on iOS. Purchases are verified to determine the subscription for each linked Kids device. The service stores product, transaction, verification, status and subscription-period records. Payments and localized prices are handled by the app store. Linking devices is not itself a purchase.

If you use a creator invite, the service stores the code, referring creator, Parent account, trial device, redemption time and trial end date. This attribution is retained with subscription records so YellowHat can prevent repeated trials and calculate creator commissions if you later subscribe.

Service providers

YellowHat uses Supabase for authentication, backend records, device pairing, settings synchronization, alert delivery and connected app services. Parent receives cache-invalidating push events and reconciles missed changes on resume or manual refresh rather than maintaining a persistent realtime connection. Google and Apple provide sign-in, store and push services for their platforms. Notification analysis uses YellowHat Offline AI on the child device, as described in the Kids privacy notice. Parent does not analyze child notification content.

Your controls

Parent lets you manage links, supported device settings, alert-content sharing and subscriptions. Settings → Delete Account removes the Parent identity, linked-device relationships, Parent alert history, push registrations and YellowHat subscription records. Store billing must still be cancelled separately through Google Play or the App Store.

Unlinking a device removes it and its alerts from that Parent account, while settings already saved in Kids remain on the child's phone.

Requests and contact

For access, correction or deletion questions, email privacy@yellowhatapp.com. Identify the account or device without sending private notifications, passwords, PINs, pairing codes or API keys. See the data deletion guide for direct in-app deletion steps.