Kidder legal information
Children’s Privacy & Data Policy
This policy provides additional transparency about information associated with children and enrolled devices in a Parent- or guardian-controlled Kidder family account.
1. Parent or guardian account control
Kidder’s family account is created and controlled by a Parent or guardian who is 18 or older. The Child App is intended for enrolled devices used by children ages 3–17. The Parent creates Child profiles, pairs supported devices, selects protection settings, and reviews information made available through the Parent App.
The current setup asks the adult to confirm that they are the legal guardian. Kidder does not currently claim a legally verified parental-consent process. Jurisdiction-specific age and consent requirements still apply.
2. Child-related information
- Child name, date of birth or age information, profile photo, and profile identifiers.
- Enrolled-device identifiers, technical metadata, battery, network, permissions, and protection status.
- Installed apps, app usage, foreground activity, Screen Time, rules, routines, and schedules.
- Precise location, Safe Places, geofences, visits, journeys, stops, and related timestamps.
- Blocked domain events, Internet Safety status, and Parent-configured domain rules.
- Derived Content Safety risk classifications and selected event context.
- Pairing, commands, notifications, security events, and device acknowledgements.
3. Purpose limitation and minimization
Kidder uses child-related information for the family safety, account security, support, and operational purposes described in the applicable notices. The information processed for a feature depends on the features the Parent or guardian sets up and enables.
Raw visible Child-device text used for Content Safety classification is processed locally rather than sent to Kidder. The Child App does not use an advertising SDK or Advertising ID for advertising.
4. Feature-specific handling
Location and Safe Places
Parent or guardian authorization and the required Android location permissions are needed for precise foreground and background location. Safe Place arrival and departure alerts can use location when Kidder Child is closed or not in use. Depending on enabled features, location also supports family location/map views, Parent-requested location refresh, history, geofences, Alert Area entry/exit alerts, and derived visits/journeys. Relevant location records and events may be sent to Kidder services for the authorized Parent.
Screen Time and installed apps
UsageStats and installed-app information support summaries, app-specific rules, schedules, and enforcement selected by the Parent.
Internet and Content Safety
Web Safety can access website addresses/domains exposed through supported browser interfaces using Android AccessibilityService and process DNS/domain requests using Android VpnService. These are separate data paths; selected blocked-domain events may be reported to Kidder. Content Safety can locally examine limited visible, editable or search text and send derived risk information rather than raw text. The verified Kidder Child 1.0 (version code 5) implementation sends permitted Web Safety DNS queries to Cloudflare’s 1.1.1.1 for Families service using encrypted DNS-over-HTTPS. Cloudflare processes queried domains and associated network information. This transport verification does not cover older installed versions; the Kidder Child Privacy & Protection Notice explains the DNS path and its limits.
Protection status
Permission, service, battery, network, and device-security state help the Parent understand whether selected protections are operating.
5. Parent visibility and family transparency
The Parent may see the Child profile, device status, installed apps, Screen Time and usage summaries, Child location and history, rules, Internet Safety events, and derived Content Safety alerts. Parents and guardians can discuss these features and the information visible in Kidder with the child in an age-appropriate way.
The Parent App does not receive raw visible screen text.
6. Providers and security
Kidder uses hosting, data-storage, and file-storage services for the family features described here. Firebase Cloud Messaging supports push delivery to enrolled Child devices. Google Play services location supports Child-device location features. Cloudflare’s 1.1.1.1 for Families resolver handles permitted Web Safety DNS queries.
Safeguards include encrypted Kidder service connections, authentication, access controls, disabled Child App backup, limited administrative visibility, and security logging. No safeguard removes all risk.
7. Retention and deletion
Raw precise child-device location currently has a seven-day pruning process, and local child-device security and protection logs use a 30-day window. For a completed deletion request, authentication and security events may be retained for up to 90 days from each event, and the protected request-level device record for up to 90 days. Other retention periods depend on the type of record and applicable security, legal, or accounting requirements; this policy does not state a fixed period for them.
Kidder supports complete Parent account deletion through its account-deletion process. Device authorization does not need to wait indefinitely for an offline child device; a one-way revocation marker can keep the installation denied and allow local cleanup when it reconnects.
8. Questions, requests, and jurisdiction-specific rights
Depending on location, a Parent or authorized guardian may have applicable privacy rights concerning a child’s information, including requests for access, correction, or deletion. Kidder may need to verify a request and may retain information where an applicable legal exception requires it.
Questions and requests can be sent to Kidder support using the contact below.
9. Changes to child-data practices
Material changes to Child App access, Parent visibility, providers, purposes, or retention will be reflected in the applicable notices, in-app explanations, and store declarations where required.