Skip to content
Get Kidder on Google Play
    • Healthy Digital Habits
    • Internet Safety
    • Family Safety
    • All Features
  • How It Works
  • Pricing
    • Getting Started
    • Compatibility
    • FAQ
    • Privacy & Transparency
  • Get the App
Get Kidder on Google Play
← Privacy & Transparency

Kidder legal information

Kidder Child Privacy & Protection Notice

TECHINSPIRE INTERNATIONAL PRIVATE LIMITED operates Kidder Child (com.kidder.child). This notice explains what the app can access on an enrolled child device, why access is requested, what stays on the device, what is sent to Kidder, and what a Parent can see.

Document contents

  1. 1. A companion for an enrolled Child device
  2. 2. What Kidder Child can access
  3. 3. Why this access is used
  4. 4. What stays on the Child device
  5. 5. What is sent to Kidder
  6. 6. What the Parent can see
  7. 7. Safe Internet and external DNS processing
  8. 8. Data security
  9. 9. Service providers
  10. 10. Protection and persistent operation
  11. 11. What Kidder Child does not collect
  12. 12. Retention, unlinking and deletion
  13. 13. Family questions and contact

Last updated 16 October 2026

Kidder is operated by TECHINSPIRE INTERNATIONAL PRIVATE LIMITED

1. A companion for an enrolled Child device

Kidder Child is installed on a child device as part of a Parent- or guardian-directed family digital safety setup and is paired to a Parent-controlled Kidder family account. It supports family-selected protection, Screen Time, app, location, web, and safety features on that enrolled device. Legal age and consent requirements can vary by jurisdiction.

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 Kidder Child can access

Kidder Child uses Android AccessibilityService on an enrolled child device for Parent- or guardian-authorized parental controls, including app and Screen Time rules, Web Safety, Content Safety, and app/settings protection. It is not a disability accessibility service. The access below does not mean that all accessed information is sent to Kidder.

  • 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. Limited text is processed locally for Content Safety; selected reported events are described in Section 5.
  • App usage events and duration information through Android UsageStats.
  • With Parent or guardian authorization and the required Android location permissions, Kidder Child accesses precise location in the foreground and background. Background location enables Safe Place arrival and departure alerts, including 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 to view.
  • 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

Access through AccessibilityService may result in selected app-use, restricted-app/settings-protection, security, blocked-domain and derived Content Safety events being reported to Kidder services for the linked Parent. These events do not amount to a complete saved browsing-history archive.

  • 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. Raw visible or typed text used for Content Safety is not included in these alert payloads.
  • 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

Kidder Child uses Android VpnService for DNS-based Web Safety on supported browsers. This is DNS-based parental-control filtering, not a general-purpose VPN, and does not route all device traffic through Kidder servers. Browser information accessed through AccessibilityService is a separate path from these DNS requests. It checks domain requests locally against Parent-selected rules and safety categories. Blocked, safety-relevant domain events may be stored on the device and reported to Kidder; permitted DNS queries are not uploaded to Kidder as browsing history. This DNS filtering does not inspect all device traffic or collect raw webpage content.

In the verified Kidder Child 1.0 (version code 5) implementation, permitted Web Safety DNS queries are sent to Cloudflare’s 1.1.1.1 for Families service at https://family.cloudflare-dns.com/dns-query using encrypted DNS-over-HTTPS (DoH). This forwarding path uses Android’s certificate and hostname verification and does not fall back to plaintext UDP DNS. This transport description applies to that verified implementation; it is not a guarantee about older installed versions. Cloudflare receives the queried domain and associated network information needed for DNS resolution and filtering. Kidder does not use its VPN for advertising or traffic monetization.

Android VPN permission and any required prominent in-app disclosure remain separate from this website notice.

8. Data security

Kidder Child release builds send app-to-backend requests over HTTPS/TLS. Kidder uses authentication and access controls for backend-held family information and limits administrative access to authorised personnel. These safeguards reduce risk, but no system can guarantee absolute security.

For the verified version code 5 implementation, external DNS forwarding uses HTTPS/TLS to Cloudflare, separately from app-to-backend HTTPS connections. Transport encryption does not prevent Cloudflare from processing the DNS queries it receives. This verification does not cover older installed versions or establish that all device traffic uses encrypted DNS.

9. Service providers

Google Firebase Cloud Messaging supplies push delivery for Child-device notifications and authorised commands. A device push token and delivery information are processed by Google for that purpose; Kidder also receives the token to address the enrolled device.

Google Play services location helps Kidder Child obtain Child-device location for family location and Safe Places features. The location service may process device and location signals under the device’s Google settings; Kidder Child sends resulting location records to Kidder for the Parent-facing features described above.

Cloudflare operates the 1.1.1.1 for Families DNS resolver used for permitted Web Safety queries. Queried domains and associated network information go directly to Cloudflare for DNS resolution and filtering; blocked-domain events that Kidder reports to the Parent follow the separate Kidder backend path described above.

10. Protection and persistent operation

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

Kidder Child 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.

11. What Kidder Child 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.

12. Retention, unlinking and deletion

Local raw location records have a seven-day pruning policy after synchronisation; local Child-device security events have a 30-day retention window. Synced blocked web-filter events older than 14 days are removed from the device. Server-side family data is retained only for as long as necessary for the purposes described in this notice, subject to applicable legal, security and operational requirements; other server-side periods are not stated here as fixed guarantees.

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 local cleanup to continue.

Delete Account is always available in Kidder. When a Parent starts deletion, Kidder checks for linked child devices; any that remain must be removed before deletion can proceed. The public Data Deletion page explains the process and how to get help if app access is unavailable. Ordinary account and family data is deleted or anonymised through Kidder’s account-deletion process. Limited records may be retained only for applicable security, legal, financial, audit, consent or backup purposes under the documented retention rules.

13. Family questions and contact

A Parent should review each permission with the family, enable only the intended features, and revisit settings as needs change. Do not include passwords, authentication codes, or unnecessary child information in support messages.

For privacy questions or help with account deletion, contact TECHINSPIRE INTERNATIONAL PRIVATE LIMITED at support@kidderpro.com. CIN: U62011UP2025PTC234487. Registered office: 1st Floor 129, Ambala Road, Saharanpur City, Saharanpur, Uttar Pradesh – 247001, India.

Related documents

  • Platform Privacy Policy
  • Children’s Privacy & Data Policy
  • Data Deletion

Questions about this document

For support, privacy, or data-related questions, contact Kidder support. Do not include passwords, authentication codes, or unnecessary child information.

Email support@kidderpro.com

Helping families build healthier digital habits and a safer digital future.

support@kidderpro.com
Product

Product

  • Download & Setup
  • Features
  • How Kidder Works
  • Pricing
Resources

Resources

  • Getting Started
  • Compatibility
  • FAQ
  • Privacy & Transparency
Company

Company

  • About Kidder
  • Contact
Legal

Legal

  • Privacy Policy
  • Kidder Privacy Notice
  • Terms
  • Data Deletion
  • Subscription / Refund
  • More Legal & Privacy

© 2026 Kidder. All rights reserved.

Google Play and the Google Play logo are trademarks of Google LLC.

Kidder

Create your Parent account

Choose how you’d like to begin.

Creating an account does not start a subscription. No details are submitted in this preview.

Mobile signup

Use a mobile number you control.

i

Signup previewNothing was submitted or saved.

Email signup

Create sign-in details for your Parent account.

Passwords need to match.

i

Signup previewNothing was submitted or saved.

Enter the code

Enter the 6-digit code sent to your mobile.

Email sign in

Reset password

If an account uses this email, instructions will be sent.

Verify your email

Open the verification email, then return here.

Confirm account details

Finishing securely…

Please keep this window open.

Your Kidder account is ready.

Continue to Google Play

We couldn’t complete that