============================================================
KidBlock — Privacy Policy (English)
============================================================
Effective date: November 8, 2026
App: KidBlock (package: com.momoko.kidblock)
Developer: Momoko
This Privacy Policy explains how KidBlock (“we”, “us”, “the App”) handles information when you use the parental screen-time control features on Android.
- Summary
KidBlock is a parental-control utility designed to help parents set and enforce daily app time limits on a child’s phone.
- In offline / on-device mode (the primary mode), limits, usage, and the parent PIN stay on that device.
- Optional cloud features (when enabled with a real Firebase configuration) may sync family settings between a parent account and a linked child device.
- KidBlock does not sell personal data and does not show third-party advertising.
- KidBlock does not read chat message contents, full browser search history, photos, contacts, or microphone/camera audio/video for monitoring.
- Who this policy covers
- Parents / guardians who install and configure KidBlock
- Children using a device where a parent has enabled KidBlock
Parents are responsible for configuring the App on a child’s device and for deciding whether to use offline-only or optional cloud linking.
- Information we process
A) On the device (offline / local mode)
Stored locally on the phone (for example with on-device databases / preferences), and used only to operate KidBlock:
- Parent PIN (stored for unlocking settings on that device)
- App list (package names and display labels of installed apps)
- Daily limits you set (minutes per app, allow-only mode, total daily quota, reminder settings)
- Screen-time usage measurements (minutes/seconds used per app per day)
- Language and basic UI preferences
- Role / setup state (e.g. child device configured offline)
In offline mode, this information is not uploaded to our servers for family sync.
B) Optional cloud mode (only when cloud sync is enabled)
If cloud features are enabled, KidBlock may use Google Firebase services to:
- Create / sign in a parent account (email and password via Firebase Authentication)
- Create a family group and invite code
- Link a child device (device identifier, display name, timezone, last-seen time)
- Sync installed-app metadata (package name, label, category flags)
- Sync daily limits and used minutes/seconds for parental monitoring
- Deliver push notifications related to parental control (Firebase Cloud Messaging / device token)
We do not require cloud account creation to use the core offline parental controls on the child phone.
C) Information we do not collect for monitoring
KidBlock does not intentionally collect or upload:
- Contents of chats, emails, or social messages
- Full web browsing or search history
- Photos, videos, files, contacts, call logs, or SMS contents
- Precise GPS location for tracking
- Payment card details
- Advertising identifiers for ad targeting
- Permissions and why they are needed
KidBlock requests Android permissions only to measure app usage and enforce limits:
- Usage Access (PACKAGE_USAGE_STATS) — measure time spent in apps
- Accessibility Service — detect which app is in the foreground (window-state events). It is configured not to retrieve window content for reading messages
- Display over other apps (SYSTEM_ALERT_WINDOW) — show the time-up / block screen
- Query installed apps — list apps so parents can set limits
- Notifications — remaining-time reminders and service status
- Foreground service / battery unrestricted / boot completed — keep monitoring reliable after restart
- Internet / network state — optional cloud sync and Firebase messaging when enabled
If you deny required permissions, some parental features may not work.
- How we use information
We use the information above solely to:
- Enforce daily app limits and allow-only rules
- Show remaining time and the lock / block screen
- Protect settings behind the parent PIN
- Optionally sync family limits and usage between parent and child devices
- Improve reliability and support of the App
We do not use this data for advertising profiles or sell it to data brokers.
- Sharing
We may share information only as needed to operate the App:
- Google Firebase / Google Play services (authentication, database sync, messaging) when cloud mode is enabled
- When required by law, legal process, or to protect users’ safety and rights
We do not sell personal information.
- Children’s privacy
KidBlock is intended for parents/guardians to manage a child’s device.
- We do not knowingly market to children or ask children to create independent accounts for advertising.
- On-device parental settings are controlled by the parent PIN.
- If cloud linking is used, parents should use their own email account and supervise invite codes.
- Parents may delete the App and local data by uninstalling. For cloud data deletion requests, contact us (see Section 11).
- Data retention and deletion
- Local data remains on the device until you clear app data or uninstall KidBlock.
- Cloud family data (if any) is retained while the family account / linked devices remain active and may be deleted upon verified request or account closure.
- Backups: Android auto-backup for this App is disabled in the App configuration where applicable.
- Security
We use reasonable technical measures appropriate for a consumer parental-control app, including on-device storage for offline mode and Firebase security mechanisms for optional cloud features. No method of transmission or storage is 100% secure. Protect your parent PIN and parent account password.
- International processing
If cloud mode is enabled, data may be processed on Google Firebase infrastructure in regions operated by Google. By enabling cloud features, you understand that such processing may occur outside your country subject to Google’s terms and applicable law.
- Contact
Developer: Momoko
App package: com.momoko.kidblock
Support / privacy email: (add your real support email here before publishing)
For privacy questions, data access, or deletion requests, email the address above and include the app name “KidBlock” and enough detail for us to locate the relevant account or device setup (without sending the parent PIN).
- Changes to this policy
We may update this Privacy Policy from time to time. The “Effective date” at the top will be revised when changes are posted. Continued use of KidBlock after an update means you accept the revised policy.
- Google Play Data safety note (for developers)
When completing Play Console Data safety, declare at least:
- App activity / app usage (on device; may be collected if cloud sync is on)
- App info and performance as needed for Firebase
- Account info (email) only if cloud parent sign-in is offered
- Data is used for App functionality; not sold; not used for ads
- Data encrypted in transit when using Firebase HTTPS
- Users can request deletion
End of Privacy Policy (English)
============================================================