Kidder Child App Privacy & Protection Notice

1. A companion for an enrolled Child device

The Child App is designed for enrolled devices used by children ages 3–17 and is paired to a Parent-controlled Kidder family account. It supports family-selected safety, Screen Time, app, location, web, and protection features on that enrolled device. Legal age and consent requirements can vary by jurisdiction.

Kidder is not positioned as a hidden surveillance product. Setup should be performed transparently by a Parent or guardian who has authority to enroll the device and should be discussed with the child in an age-appropriate way.

2. What the Child App can access

• Accessibility events and limited visible interface text for local Content Safety classification and configured app or settings enforcement.
• App usage events and duration information through Android UsageStats.
• Precise location in the foreground and background for location, Safe Places, history, and geofence features.
• Installed-app names, package names, versions, categories, and system-app status.
• DNS/domain requests and blocked-domain context for Safe Internet.
• Device identifiers and device, operating-system, battery, network, SIM operator, permission, and protection status.
• Overlay, Device Admin, foreground service, notification, battery, boot, and package-change capabilities used to keep configured protection visible and operating.

3. Why this access is used

• Measure Screen Time and support Parent-configured app limits, routines, and rules.
• Show the Parent useful location, Safe Place, arrival, departure, and journey information.
• Identify installed apps so the Parent can understand and configure app-specific controls.
• Block configured apps or websites and show a clear blocking message on the Child device.
• Classify selected on-screen safety signals locally and send a derived alert when appropriate.
• Report whether protection permissions or services are active and respond to authorized Parent actions.

4. What stays on the Child device

Raw visible screen text used for Content Safety classification is read and evaluated locally and is not sent to Kidder as part of this feature. Kidder may store local app, usage, location, web, security, policy, and event records so the device can operate and synchronize.

Permitted DNS queries are not stored by Kidder as browsing history in the current reporting path; blocked, safety-relevant domain events may be retained locally and sent to Kidder. The external DNS provider may separately process DNS requests.

5. What is sent to Kidder

• Pairing code and family/device linkage information.
• Device IDs, FCM token, model, manufacturer, Android version, app version, permission and protection state.
• Installed-app inventory and app usage or Screen Time records.
• Precise location, accuracy, speed or movement context, time, geofence, visit, and journey information.
• Blocked domain, category, action, reason, relevant app, network context, and event time.
• Derived Content Safety category, score, risk band, context, source, fingerprint, and configured watch-term reference.
• Battery, charging, network, SIM operator, security, package-lifecycle, command, and synchronization status.

6. What the Parent can see

• Child profile and connected-device status.
• Installed apps, usage summaries, Screen Time, rules, routines, and requests.
• Current or recent location, Safe Places, history, visits, journeys, and relevant alerts.
• Blocked web events and Internet Safety status.
• Derived Content Safety alerts and categories, not raw visible screen text.
• Battery, connectivity, protection, permission, sync, and security status.

7. Safe Internet and external DNS processing

Safe Internet uses Android VPN Service to handle supported browser domain requests and apply domain-safety controls. Domain requests and associated network metadata may be processed by an external DNS provider so filtering can operate. The provider’s identity, contractual role, and production configuration remain subject to review.

This website notice does not replace the separate, clear in-app VPN disclosure and consent required before access.

8. Protection and persistent operation

Accessibility, overlay, Device Admin, foreground services, background operation, boot handling, and battery settings support Parent-configured monitoring and enforcement. These capabilities can affect how apps are opened, when blocking UI appears, and how easily protection can be stopped or removed.

The Child App should display purpose-specific explanations before the relevant Android setting or permission is enabled. A general privacy policy or one grouped guardian checkbox is not a substitute for those disclosures.

9. What the Child App does not collect

• Contacts, call logs, SMS content, or general files and media.
• Advertising ID for advertising or personalized advertising.
• Raw visible screen text sent to Kidder.
• Camera images through the current pairing route; QR-camera pairing is not currently offered.

10. Unlinking and deletion

When a Child device receives an authenticated removal signal, it stops device-scoped work and clears its token, account preferences, scheduled work, and device-scoped local records. Reusable public catalogues may remain on the device.

Removing a device does not depend indefinitely on that device being online. If it reconnects later, a one-way revocation marker can keep it denied and allow its local cleanup to continue. Complete Parent account deletion is not currently presented as a verified live capability.

11. Family questions and choices

A Parent should review each permission with the family, enable only the intended features, and revisit settings as needs change. Questions may be sent to the privacy contact below. Do not include passwords, authentication codes, or unnecessary child information.