Privacy Policy
Application: Child Story Web (com.mohameedsalah.childstoryweb) Effective Date: May 25, 2026
Application: Child Story Web (com.mohameedsalah.childstoryweb) Effective Date: May 25, 2026
This Privacy Policy describes how Child Story Web ("we", "our", or "the Application") handles user information. We are fully committed to protecting the privacy of our users, especially young children and families, in absolute compliance with the Google Play Families Policy, the Children's Online Privacy Protection Act (COPPA), and the General Data Protection Regulation (GDPR).
Child Story Web is designed as a safe, educational, and engaging story platform for children. We implement stringent privacy controls to ensure a clean, secure environment:
We do not collect or request any personal biological data, names, accounts, or addresses from children.
Any core sensitive feature (such as voice tracking/recording) operates strictly locally on the user's device.
Below is an explicit breakdown of the specific data types utilized by the Application, detailed exactly as disclosed in our Google Play Data Safety form:
Voice / Sound Recordings (Audio Files)
Collection Mode: Local Only (Optional)
Data Sharing: No Sharing (0% Transmitted)
Purpose & Handling Architecture: Used exclusively for interactive reading features. Audio is recorded via the device microphone and processed locally inside isolated app storage. It is never uploaded to any server or third-party client.
Device & Other IDs (Firebase Analytics)
Collection Mode: Automated (Required)
Data Sharing: No Sharing
Purpose & Handling Architecture: Collected via Google Analytics for Firebase to measure product health, session duration, and user retention metrics. Transmitted securely via encrypted HTTPS protocols.
To deliver specific functionalities, the Application requires explicit runtime hardware consent from the user. These permissions are requested contextually and are never pre-loaded at launch:
This permission is used solely when the child actively interacts with our interactive reading tools. It enables the child to hear their own voice reading alongside the stories. The audio streaming pipeline exists wholly within the volatile or local cache directory (context.filesDir / context.cacheDir). No audio streams ever leave the phone perimeter.
We leverage industry-leading standard safe transmission protocols for all operational analytical streams:
Encryption in Transit: Any high-level metadata transmitted for crash logs or application usage statistics (via Firebase) is strictly encrypted in transit using secure Transport Layer Security (TLS/HTTPS) protocols.
Data Isolation: Local temporary audio creations are maintained inside the application's secure container sandbox, completely isolated from outside applications, and are automatically purged when the application is uninstalled.
Because we do not store personal recordings or identifiers on remote servers, there is no remote cloud vault of your child's data to delete. Local app audio artifacts are cleanly removed by clearing the application data from device settings or executing an uninstallation. For any automated platform metrics associated with an internal analytics container, parents may request manual analytical deletion by contacting our privacy compliance liaison at the email provided below.
Any monetization systems implemented within Child Story Web comply entirely with the Google Play Families Policy restrictions:
We display ads that are designated solely for children/all audiences by using appropriate content filtering tags (such as Google Mobile Ads SDK tagForChildDirectedTreatment).
We do not utilize interest-based behavioral profiling targeting mechanisms on any child demographics.
If you have any operational technical concerns, programmatic privacy inquiries, or questions about this policy, please reach out to our team:
Developer Support & Privacy Liaison Email: mohamedsalah.dev@gmail.com