1. Scope and responsibility
This Privacy Policy applies to the SnapCARE Android app and its supporting cloud functions. “SnapCARE,” “we,” “us,” and “our” mean the SnapCARE developer identified in the Google Play listing. The privacy contact for this version is MH Tech.
A parent account creates a family space and links one or more child accounts using a private six-digit code. Within a linked family, the parent manages protection settings and can view the child information described below. The parent or guardian is responsible for choosing appropriate settings and obtaining any consent required for a child in their country.
2. Data we access, collect, and store
Features only work when their related data is available. Some data is entered by a user, some is generated by the app, and some comes from Android or connected providers.
| Category | What it includes | Where it comes from | Why it is handled |
|---|---|---|---|
| Account and profile | Email address, Firebase user ID, account role, display name, child name and age, profile photo URL/image, and Google profile details when Google Sign-In is chosen. | User, parent/guardian, Firebase Authentication, Google Sign-In | Create and secure accounts, show the correct dashboard, identify linked family members, and personalize the experience. |
| Family linking | Parent and child user IDs, private six-digit link code, linked-child status, and link timestamps. | Parent and child actions | Connect the intended devices and restrict family data to authenticated linked accounts. |
| Device and app inventory | Device model, manufacturer and brand; installed app package names, app names, and app icons. | Android device and package manager | Let a parent recognize the protected device, choose apps for limits, and display correct app icons. |
| Screen time and protection activity | Per-app usage duration, daily totals, app-limit commands, schedules/routines, block reasons, active grants, approval requests and decisions, activity history, streak/progress information, and protection/tamper events. | Android Usage Access, Accessibility Service, parent/child actions, app calculations | Calculate reports, enforce limits, operate routines, process access requests, and show an audit trail to the linked family. |
| Location and safe zones | Precise or approximate latitude and longitude, accuracy, update time, parent-defined safe-zone coordinates/radius, and geofence entry or exit alerts. | Android location services and family settings | Show the child’s live location to the linked parent and provide requested safe-zone alerts, including while the app is not open when background permission is granted. |
| Snap Review media | Optional 5–10 second camera video, app name/package, parent goal or reason, review mode, timestamps, status, and reviewer outcome. | Child camera and family limit settings | Allow a child to demonstrate a requested real-world activity for parent review or, only when selected, Amazon Bedrock AI review. |
| Notifications | Firebase Cloud Messaging token and notification routing fields such as request type, child ID, request ID, and review ID. | Firebase Cloud Messaging and app events | Deliver time-sensitive limit, approval, Snap Review, and safe-zone updates. |
| Subscription and purchase status | Google Play product/base-plan identifiers, plan key, entitlement status, purchase token, purchase and expiry/renewal times, auto-renewal state, and lifetime/subscription status. | Google Play Billing | Display plans, confirm entitlement, restore purchases, and manage premium access. SnapCARE does not receive a full payment-card number. |
| Operational information | Error state, request timing, cloud-function invocation data, security events, and limited technical logs. Provider systems may also receive IP address, device/browser information, and diagnostic data under their own terms. | App, Firebase, Google Play services, and cloud providers | Operate, secure, debug, prevent abuse, and maintain the service. |
Passwords are handled by Firebase Authentication and are not stored in SnapCARE’s Realtime Database. Payment credentials are handled by Google Play rather than SnapCARE.
3. Android permissions and sensitive APIs
Android controls these permissions. A user can review or revoke them in system settings, although doing so may stop the related feature.
| Permission or API | What SnapCARE does | Required? |
|---|---|---|
| Foreground and background location | Obtains the child device’s location for the linked-parent map and safe-zone alerts. Background location keeps this current when SnapCARE is not open. | Required for live-location protection; background access is requested separately. |
| Usage Access | Reads app-usage duration and foreground-use statistics to calculate screen-time totals and per-app reports. | Required for screen-time reporting. |
| Package/app visibility | Reads the installed-app inventory, names, package identifiers, and icons so a parent can select the correct apps to limit. | Required for app-specific limits. |
| Accessibility Service | Detects the foreground package to enforce a chosen app limit and display its block screen. For protection against disabling or uninstalling SnapCARE, it also examines visible text and content descriptions only on Android Settings or package-installer screens. That Settings text is processed on-device and is not stored or sent. SnapCARE does not use Accessibility Service to read messages, passwords, ordinary typing, or content inside other apps. | Required for app-limit enforcement. A separate in-app disclosure and affirmative consent are shown before Android settings opens. |
| Display over other apps / accessibility overlay | Shows the app-themed limit or protection screen above a restricted app. | Required for the visible block screen. |
| Camera | Records a short Snap Review only after the child chooses the feature and holds the record control. | Optional; only needed for Snap Reviews. |
| Notifications | Shows approval decisions, protection events, and family alerts. | Needed for timely alerts; Android may let the user disable them. |
| Device Admin | Allows a parent-requested emergency screen lock. SnapCARE does not request or use device-wipe capability. | Optional. Setup and core app limits can continue without it. |
| Battery-optimization exemption, foreground service, wake lock, and boot start | Keeps user-visible family safety, location, approvals, scheduled limits, and protection synchronization reliable when Android is saving power or after restart. | Required for reliable persistent protection. Android always presents the system control. |
| Internet and Google Play Billing | Synchronizes linked-family data and checks or purchases premium entitlement through Google Play. | Required for cloud and subscription features. |
4. How we use data
- Authenticate accounts and maintain the parent–child family link.
- Sync limits, routines, access grants, protection state, location, and activity between authorized linked devices.
- Enforce a parent-selected app limit on the child device and provide request/review controls.
- Generate screen-time reports, safe-zone alerts, progress summaries, and recent activity.
- Store and deliver profile images, app icons, and optional Snap Review videos.
- Perform an AI Snap Review only when the child explicitly selects the AI review option.
- Deliver push notifications and confirm premium subscription entitlement.
- Secure, troubleshoot, maintain, and improve reliability of the service.
6. Children and family consent
SnapCARE includes a child role because family safety and digital-wellbeing features are used on a child’s device. A parent or legal guardian must authorize the child’s use, create or approve the family relationship, and supervise the permissions and settings. Children should not create or link an account without their parent or guardian’s permission.
The parent can review the child data visible in the app and can request correction or deletion. If we learn that child data was collected without legally required parental authorization, we will take reasonable steps to delete it after verification. Age-of-consent rules differ by country; the family is responsible for providing accurate age information and following local requirements.
SnapCARE does not show interest-based advertising to children and does not transmit advertising identifiers for advertising.
7. Retention
SnapCARE currently retains account profiles, family links, settings, app inventory, screen-time summaries, current location/safe-zone records, activity history, requests, subscription entitlement, and Snap Review records while the account is active and as needed to provide the service. Resolved requests and uploaded Snap Review videos do not have an automatic expiry in this version; they remain until removed by an authorized family member, the account is deleted, or they are no longer reasonably needed for the stated purpose.
Short camera recordings are first created in the app’s private cache. Failed or too-short recordings are deleted by the app; other local cache files may remain until replaced, the app/Android clears its cache, or the app is uninstalled. Provider security and operational logs are retained under the provider’s configured retention period.
After a verified deletion request, we delete or de-identify associated active-service data unless limited retention is necessary for security, fraud prevention, resolving disputes, complying with law, or maintaining transaction records. Deletion from encrypted backups and provider replicas can take additional time under normal backup rotation.
8. Delete your SnapCARE account and data
A parent or child account holder can request permanent deletion at any time. A parent or guardian may also request deletion of a linked child’s data. Send the request from the account email where possible and identify whether the parent account, a child account, or the entire linked family should be deleted.
We may ask for limited verification to prevent someone else from deleting your family data. After verification, the account’s Firebase Authentication record and associated SnapCARE database/storage data will be deleted, subject only to the limited retention described above.
9. Your choices and controls
- Access and correction: view and update available profile or family settings in the app, or contact us for assistance.
- Permissions: review or revoke Android permissions in system settings. Revocation stops the related feature and may prevent protection from operating.
- Emergency lock: Device Admin is optional and can be skipped or disabled in Android settings.
- Snap Review: the child chooses whether to record a video and whether to send it to the linked parent or select AI review.
- Location: Android controls foreground/background and precise/approximate location access.
- Notifications: notification categories can be disabled through Android settings, although decisions may arrive less promptly.
- Family link: a parent can unlink a child device. Unlinking stops family access but is not the same as deleting the child account and its stored data.
- Deletion: use the prominent process in Section 8.
10. Security
SnapCARE uses Firebase Authentication, authenticated database and storage rules, role/link checks, scoped storage paths, upload content-type/size limits, HTTPS/TLS service endpoints, and Google Play purchase verification data to reduce unauthorized access. Raw notification tokens and complete user records are not intentionally written to application diagnostic logs.
Users should keep passwords and link codes private, use secure device locks, and unlink lost devices. No security system is perfect; we cannot guarantee that transmission or storage will never be compromised.
11. International processing
Firebase, Google, and Amazon cloud services may process information in countries other than the user’s country, including the United States. Privacy laws may differ in those locations. We use these providers only for the purposes described here and apply available access controls and contractual/provider safeguards.
12. Changes to this policy
We may update this policy when SnapCARE features, providers, legal obligations, or data practices change. The effective date at the top will be updated. Material changes will be communicated through the app, store listing, or another reasonable channel before they take effect when required.
13. Privacy contact
App: SnapCARE
Developer contact: MH Tech
Email: hello@getsnapcare.co
Use the subject “SnapCARE privacy request” for access, correction, consent, child-data, or privacy questions, and “SnapCARE account and data deletion request” for deletion.