Kidder legal information
Children’s Privacy & Data Policy
This policy provides additional transparency about information associated with children and enrolled devices. It does not claim compliance with a specific child-privacy law or a verified-parental-consent process that has not been legally approved.
Document contents
- 1. Parent or guardian account control
- 2. Child-related information
- 3. Purpose limitation and minimization
- 4. Feature-specific handling
- 5. Parent visibility and family transparency
- 6. Providers and security
- 7. Retention and deletion
- 8. Questions, requests, and jurisdiction-specific rights
- 9. Changes to child-data practices
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 should use child-related information only for the family safety, account security, support, and operational purposes described in the applicable notices. Access should be tied to an enabled feature and explained before the associated sensitive capability is activated.
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
Precise background location can support current location, history, geofences, visits, journeys, and arrival or departure context shown to the 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
Safe Internet can process DNS/domain requests and report blocked safety events. Content Safety can locally examine limited visible text and send derived risk information.
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. Kidder should present this relationship clearly during setup and encourage age-appropriate family discussion.
The Parent App does not receive raw visible screen text. This distinction must remain accurate if the product changes.
6. Providers and security
Hosting, data storage, file storage, Firebase messaging, and external DNS services can be involved in handling Child data. Provider identities, regions, contractual roles, and child-directed service eligibility remain subject to confirmation.
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 security, backup, consent, payment, tax, or accounting periods remain subject to operational, legal, or accounting confirmation.
Complete Parent account deletion is not currently presented as a verified live service. 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
A Parent or authorized guardian may have rights concerning a child’s information depending on location. Verification, access, correction, deletion, objection, complaint, appeal, and age-related procedures require legal review for applicable jurisdictions worldwide.
Children and families should be given understandable ways to ask what Kidder does. Questions and requests may be sent to the approved privacy 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.