SafeKid Privacy Policy
Last updated: November 5, 2026
SafeKid helps parents and primary-school children communicate during safety incidents and provides device pairing, consent-based location sharing, safe zones, check-ins, and pickup verification. SafeKid is not an emergency service and does not guarantee that a child is safe.
Data we process
- Parent or guardian account data: email address, display name, account identifiers, and family relationships.
- Child data supplied by a parent: display name, sharing permissions, trusted phone number, and school or monitoring schedule when enabled.
- Precise location, accuracy, and timestamps when actively shared, attached to an SOS, or collected under a parent-enabled school monitoring plan.
- SOS, safe-zone, check-in, pickup, and response-status events.
- Necessary technical data: installation or device identifiers, pairing sessions, notification tokens, permission/GPS/service state, and heartbeat timestamps.
- API request logs: time, account or device ID, route without parameters, method, status, duration, full IP address, and user agent. Unauthenticated requests are included. Tokens, cookies, request bodies, and URL parameters are not logged.
- Update checks: a random installation ID, app version name and code, last use time, and parent account ID after sign-in. Child installations appear anonymously in version reports.
SafeKid does not remotely activate the microphone, record ambient audio, sell data, or use data for advertising.
Purposes and use
We use data only to provide requested safety features, authenticate and authorize users, deliver notifications, prevent abuse, troubleshoot, and comply with law. School monitoring starts only after prominent disclosure and parent confirmation; the child device shows an ongoing notification whenever the background location service is active.
Service providers
Supabase (authentication, database, realtime, and server functions), Cloudflare (API relay), Firebase Cloud Messaging/Google Play Services (notifications and location services), and OpenStreetMap (map tiles; its provider may receive an IP address and requested tile coordinates) may process data on our behalf. Schools cannot access family data in the current version. Server-side Row Level Security limits access to authorized family members.
Retention
API request logs in the admin portal are deleted after 30 days and account identifiers are removed on account deletion. Version records are deleted after 90 days of inactivity or when the related account is deleted. Raw location and device-health logs are configured for a maximum of 7 days; check-in requests for 30 days; monitoring consent and audit records while a plan is active and generally up to 90 days after revocation. Some safety events and family configuration may be retained until no longer necessary or the account is deleted.
Your choices and deletion
Parents can stop location sharing, revoke devices or guardians, delete location history, and use Settings → Delete account and related data. If the app is unavailable, send a request to huynhnhutphong1412@gmail.com. We may verify identity and parental authority before fulfilling a request.
Children and security
Data is transmitted over HTTPS; server secrets are not embedded in the app; and access is enforced through server logic and Row Level Security. No system is perfectly secure. A parent must have legal authority and provide verifiable consent before entering or collecting a child's data. Availability in each market remains subject to review under applicable child-data laws.
Contact and changes
Privacy questions and access, correction, or deletion requests: huynhnhutphong1412@gmail.com. We may update this policy when features or legal obligations change and will revise the date above.