VigilParent Privacy Policy

This Privacy Policy describes how Vigil Studio (“We,” “Us,” or “Our”) collects, uses, synchronizes, and safeguards information in connection with the VigilParent controller application (for parents) and the VigilParent Kid companion application (for the child’s device).

We do not sell, rent, monetize, or trade children’s personal information or family monitoring records to third-party data brokers or marketing companies under any circumstances.

To ensure complete transparency regarding how data flows across devices, review the breakdown below:

How Synchronization Works:

• When the Child Device is Offline: The companion app continues logging device usage and websites visited. All logs are securely cached locally within the internal, sandboxed storage of the Child Device.
• When Child is Online, but Parent is Offline: The Child Device continues storing all activity logs locally on the child's device. It updates only its “Last Seen” status on our server (so the parent can confirm the child's device is active). If the parent has enabled “Auto Location” in the parent settings, the single latest location point is uploaded to the server.
• When Both Devices Connect (Direct P2P Sync): Once both devices are simultaneously active, they establish a secure, authenticated, end-to-end encrypted Peer-to-Peer (P2P) data channel. All pending logs cached on the child's device synchronize directly to the parent's phone.
• No Cloud Intermediary: NO GRANULAR ACTIVITY LOGS ARE EVER RECORDED OR STORED ON VIGIL STUDIO CLOUD SERVERS.

A. Data Retained on Company Servers

To enable account binding and basic device status monitoring, our cloud servers process and retain only:

1. Registered Parent Email ID: The email used to authenticate your account and manage subscriptions.
2. Child Name / Nickname: The label assigned by the parent to identify the child profile.
3. Child Device Model Number: The hardware identification string (e.g., Google Pixel 7) used to display device status.
4. Child Device Last Seen: An active timestamp reflecting when the child device was last connected to network services.
5. Pairing Information: The date and timestamp when the parent account linked the child device.
6. Last Location (Conditional): If the parent enables Auto Location in the parent dashboard, the server stores the child's single most recent GPS coordinate (latitude, longitude, accuracy, and timestamp) so the parent can see the last location even when offline. New location pings overwrite the prior coordinate.

B. Data Processed Strictly On-Device (Never Stored on Server)

• Application Usage Logs: Names of installed applications, timestamps of launches, and daily screen time duration.
• Web Browsing History: URLs accessed via supported web browsers for parental web filtering.
• Notification Summaries: System and messaging notification metadata inspected on-device to deliver parental safety alerts.

To deliver transparent parental controls in compliance with Google Play Developer Policies, the VigilParent Kid companion app requests the following core permissions:

We integrate select third-party software development kits (SDKs) to provide core infrastructure, authentication, and diagnostics:

• Google Firebase: Provides secure account authentication, cloud messaging (push notification alerts for geofencing and pairing), and crash diagnostics (Firebase Crashlytics). Data is processed in compliance with Google Firebase Privacy Terms.
• Google Analytics for Firebase: Collects aggregate, non-identifying telemetry (e.g., app crash rates, device OS versions) to assist developers in troubleshooting bugs and optimizing responsiveness.
• Advertising Network Partners (e.g., Google AdMob): Advertisements are displayed exclusively inside the Parent Controller application (VigilParent).
  Google Play Families Policy Compliance: The companion VigilParent Kid application contains zero behavioral, personalized, or targeted advertising. No advertising identifiers (AdID) are tracked or collected from the child’s device for advertising networks.

Protecting children's personal data is the cornerstone of VigilParent. We comply with international data protection frameworks:

• Verifiable Parental Consent: The VigilParent Kid app cannot be activated in isolation. It requires a cryptographic binding step (QR scan or pairing code) executed directly from the authenticated Parent Device. This establishes affirmative, verifiable parental consent.
• COPPA Compliance (United States): We do not solicit personal information directly from children under 13 without verifiable parental authorization. Parents maintain full control to review, halt, or delete collected data.
• GDPR-K Compliance (European Union & UK): We adhere to Article 5(1)(c) (Data Minimization) and Article 25 (Data Protection by Design). Detailed monitoring data is kept off servers, and parents hold full GDPR data subject rights.
• Digital Personal Data Protection Act, 2023 (DPDP Act, India): In accordance with Section 9 of the DPDP Act 2023, personal data of minors is processed only upon obtaining verifiable consent of the parent or lawful guardian. We do not engage in behavioral profiling of children for marketing purposes.

You have complete control over your data and retain the right to request full erasure at any time:

• Server Data Retention: Account records, child profile labels, and device models are kept while your account is active. The Last Known Location is overwritten continuously whenever new coordinates arrive.
• Local Device Erasure: Uninstalling the VigilParent Kid app instantly wipes the local SQLite activity database from the child’s handset. Parents can also purge historical synced logs directly from the Parent Device settings.
• Permanent Account & Server Deletion: You may delete your account and all associated cloud records at any time. Inside the VigilParent app, go to Settings > Delete Account, or send an email to info.vigilstudio@gmail.com with the subject line "Data Deletion Request". All server metadata is permanently purged within seven (7) business days.

We enforce strict technical and organizational safeguards designed to prevent unauthorized access or disclosure:

• Encryption in Transit: All communication between user devices and our cloud servers is encrypted via industry-standard TLS 1.3 / HTTPS.
• P2P Session Encryption: Direct peer-to-peer data transfers between the Parent Device and Child Device are protected with end-to-end cryptographic handshakes.
• Compartmentalized Infrastructure: Server databases reside in secured Google Cloud data centers protected by multi-factor authentication and strict access controls.

VigilParent operates globally. By registering and utilizing the Services, you acknowledge that your minimal Server-Retained Metadata may be stored or processed in data centers located in India, the United States, or other regions where our cloud providers (such as Google Cloud) operate. All data transfers comply with recognized cross-border security mechanisms.

We may update this Privacy Policy periodically to reflect technological updates or evolving legal requirements. Any material changes will be announced via an in-app notice, push notification, or an updated “Last Updated” date at the top of this document. We encourage parents to periodically review this page.

If you have questions, feedback, or data privacy requests, or wish to reach our Data Protection and Grievance Officer, please contact: