Kidder legal information
Kidder Platform Privacy Policy
This policy explains how Kidder handles Parent account information and information associated with connected child devices. Kidder is the parent app; Kidder Child supports selected features on an enrolled child device.
1. Scope and status
This policy covers the Kidder website, Kidder app for parents, Kidder Child on enrolled child devices, and related support or administrative operations. More specific notices explain the parent and child-device experiences separately.
Kidder is the product name used throughout this policy. Service availability, rights, and obligations can differ by jurisdiction.
- Kidder Privacy Notice: information handled through the adult account-holder application.
- Kidder Child Privacy & Protection Notice: access and processing on an enrolled Child device.
- Children’s Privacy & Data Policy: additional transparency for child-related information.
2. How the Kidder service works
A Parent or guardian creates and controls the Kidder family account. The Parent may create Child profiles, pair supported Child devices, configure family rules, and review information sent by those enrolled devices.
The Parent App does not collect the Parent phone’s precise or coarse location. Child location shown in the Parent App comes from the connected child device through Kidder’s services.
- The Parent App manages the family account and displays family information.
- Software on the connected child device supports the protections and features selected by the Parent.
- Kidder’s services secure accounts, coordinate pairing and settings, store operational data, and provide information to the Parent App.
- The website provides product, setup, privacy, security, and request information.
3. Parent account and device information
Depending on the sign-in method and features used, Kidder may process the following Parent information.
- Name, email address, phone number, country setting, and account status.
- Firebase, Google, Kidder account, installation, session, and authentication identifiers.
- Password or Parent PIN credentials in protected authentication workflows.
- Optional Parent profile photo.
- Parent notification token and notification-delivery information.
- Parent device model, platform, app version, session IP address, user agent, and security events.
- Support, privacy, or security communications when an operational channel is used.
4. Child device and family information
The categories processed depend on which family features are set up and enabled.
- Child profile name, date of birth or age information, profile photo, and profile identifiers.
- Paired-device identifiers, model, manufacturer, operating-system version, app version, battery, network, permission, protection, and connectivity status.
- Installed-app names, packages, versions, app usage, foreground activity, Screen Time totals, and related summaries.
- Rules, routines, schedules, allowed or blocked apps, domain rules, Safe Places, and other Parent-selected settings.
- Precise Child-device location, timestamps, accuracy, movement context, geofences, visits, journeys, stops, and location summaries.
- Blocked web-domain events, safety categories, action, relevant app package, network context, and event time.
- Derived Content Safety risk category, score, band, context, source, fingerprint, and Parent-configured watch-term references.
- Notifications, device commands, pairing records, acknowledgements, and operational events.
5. Sources and purposes
Information comes from the Parent, Parent App, connected child device, sign-in providers, device operating system, and Kidder services. Kidder uses it for the product, security, support, and administration purposes described here.
- Create and secure Parent accounts and sessions.
- Pair the intended Child device with the correct family profile.
- Provide Screen Time, app rules, routines, location, Safe Places, Internet Safety, Content Safety, notifications, and device-health features.
- Deliver Parent-selected settings and commands to an enrolled device.
- Detect misuse, investigate failures, protect account access, and maintain auditability.
- Respond to support, privacy, deletion, or security requests when verified channels are available.
- Administer subscriptions and entitlements if a purchase channel is enabled later.
6. Content Safety and local text processing
The enrolled child-device software can read limited visible on-screen text through Android Accessibility for local safety classification. Raw visible screen text is processed locally and is not sent to Kidder as part of this feature.
Derived classifications and selected event context may be sent to Kidder so the Parent can receive a meaningful safety alert. These derived records can include a category, score, risk band, app package, source, fingerprint, and reference to a Parent-configured watch term.
On an enrolled child device, Android AccessibilityService can also access foreground application identity, app/settings navigation and enforcement signals, limited visible, editable or search text, and website addresses/domains exposed through supported browser interfaces. Browser website/domain information is Web browsing history data. Selected app/settings-protection, security and blocked-domain events may be sent to Kidder services for the linked Parent. See the Kidder Child Privacy & Protection Notice for the access and reporting details.
7. Service providers and external processing
Kidder uses Firebase Authentication, Firebase Cloud Messaging, Google Identity, Google Maps, Android geocoding, and providers for hosting, data storage, file storage, and communications. These providers process information needed to supply their respective services.
Safe Internet can send supported domain requests to Cloudflare’s 1.1.1.1 for Families external DNS resolver. Cloudflare receives domain-query and associated network information to provide DNS resolution and filtering. The verified Kidder Child 1.0 (version code 5) implementation uses encrypted DNS-over-HTTPS; this transport description does not establish the behavior of older installed versions. See the Kidder Child Privacy & Protection Notice for the separate DNS and selected blocked-domain reporting paths.
8. Security practices
Kidder uses authentication, encrypted service connections, access controls, private file access, account and session controls, limited administrative visibility, and security logging. No security control eliminates all risk.
- Kidder app-to-backend connections are configured to use HTTPS. External DNS processing is described separately in the Kidder Child Privacy & Protection Notice.
- Authentication tokens are protected in the Parent App, and child-device app backup is disabled.
- Administrative permissions separate ordinary and sensitive access.
- Selected Parent and Child details are masked in administrative views.
- Security and access events may be recorded for investigation and account protection.
9. Retention and deletion
Kidder intends to keep information only for service, security, support, and lawful purposes. 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. Raw visible screen text is not sent to or retained by Kidder as part of Content Safety.
Retention varies by the type of information, the feature being used, security needs, and applicable legal or accounting requirements. Subscription, payment, consent, tax, administrative-audit, and backup periods are therefore not presented here as fixed guarantees.
Kidder supports complete Parent account deletion. Delete Account is always available in Kidder. When a Parent starts deletion, Kidder checks for linked child devices. If any remain, the Parent must remove them first; once none remain linked, deletion can proceed. The Data Deletion page explains the steps and how to get help if app access is unavailable.
- Authentication and security events associated with a completed deletion request are retained for up to 90 days from each event.
- The protected device-removal record associated with a completed deletion request is retained for up to 90 days.
- A one-way device-revocation marker may remain for as long as needed to keep a removed installation denied and allow local data to be cleared after reconnection.
- Protected backups and administrative security records follow separate restricted-access retention controls.
- Consent and genuine subscription, payment, tax, or accounting records are retained only where required; the applicable period depends on the record and legal or accounting requirement.
- Applicable Parent account and family data is deleted or anonymized according to Kidder’s documented deletion and retention rules. Information that must be retained for security, legal, financial, audit, consent, backup, tax, or accounting purposes is kept only for the applicable purpose and retention period.
10. Requests, rights, and international processing
Privacy rights differ by location and may include access, correction, deletion, restriction, objection, or complaint rights. Kidder may need to verify a request and may retain information where an applicable legal exception requires it.
Service providers may process information in countries other than the family’s country. Contact Kidder support for questions about production data locations or applicable transfer safeguards.
11. Changes and contact
Kidder may update this policy as product behavior, providers, law, or service availability changes. Material changes will be communicated through an appropriate notice. Questions may be sent to the privacy contact below.