How we protect your family's data at every layer — from device to cloud and back.
All communication between the parent app, child companion app, and our servers uses TLS 1.3 (HTTPS). Firebase SDKs enforce certificate pinning. No monitoring data ever travels in plaintext.
Data stored in Firestore, Realtime Database, and Cloud Storage is encrypted at rest using AES-256 by default on Google Cloud Platform. Encryption keys are managed by Google's Key Management Service (KMS) with automatic rotation.
We retain monitoring data only as long as parents actively need it. All time-sensitive data auto-purges via Firestore TTL policies:
| Data Type | Retention | Method |
|---|---|---|
| Safety alerts & notifications | 30 days | Firestore TTL on expireAt |
| Location history | 30 days | Firestore TTL |
| Chat message snapshots | 30 days | Firestore TTL |
| Audio recordings | 30 days | Cloud Storage lifecycle rule |
| Photo captures | 30 days | Cloud Storage lifecycle rule |
| Screen mirror frames | Ephemeral | Overwritten per frame (single-doc buffer) |
| Call logs & app usage | 30 days | Firestore TTL |
| Guardian consent records | Account lifetime | Immutable — required for compliance |
| Trial anti-recycling hashes | Permanent (pseudonymized) | SHA-256 hash only — no PII |
Before any monitoring begins, the parent/guardian must complete a documented consent flow:
recordConsent Cloud Function)completePairing verifies consent exists before activating monitoringEvery database read and write is gated by Firestore security rules that enforce ownership. A parent can only access documents under their own parents/{uid} path. Cross-account access is structurally impossible — the rules reject any request where request.auth.uid does not match the document's parent path.
Premium features (screen mirroring, audio, camera, chat sync) are gated server-side via the triggerFeature Cloud Function. The client cannot bypass the paywall — even a modified APK cannot activate premium features because the server verifies subscription status before allowing any trigger.
Firebase App Check with Play Integrity is enforced on all 21 callable Cloud Functions. Requests from unverified or tampered clients are rejected before reaching business logic.
We collect children's device data only with verifiable guardian consent. Data is minimized to what is necessary for safety monitoring. Parents can delete all child data at any time.
Guardian consent is obtained before processing any child's personal data. Data retention is limited (30-day TTL). The right to erasure is supported via instant self-service deletion. A Grievance Officer is designated per Section 13.
Parents can delete all their data through two paths:
Deletion covers: parent profile, all child profiles and subcollections, consent records, Storage files (photos, audio), RTDB data, pairing codes, and Firebase Auth account. Trial anti-recycling hashes (pseudonymized, no PII) are retained to prevent abuse.
For data protection concerns or complaints under the DPDP Act:
Grievance Officer
MODERN GENESIS TECHNOLOGY (OPC) PRIVATE LIMITED
Email: support@parentalsystem.com
Response time: Within 48 hours
All backend services run on Google Cloud via Firebase — Firestore, Realtime Database, Cloud Functions (Node 22), Cloud Storage, and Firebase Authentication. Google Cloud maintains SOC 1/2/3, ISO 27001, and ISO 27017 certifications. Data residency is managed by Google's global infrastructure.
Payment processing is handled by Razorpay, a PCI DSS Level 1 certified payment gateway. We never store card numbers, CVVs, or bank account details on our servers. Webhook signatures are verified using HMAC-SHA256 with timing-safe comparison.