Privacy should
be easy to understand.
What FamSafe may collect, why the app needs it, who can see it, and the choices available under UK data protection principles.
Effective Date: 9 November 2026 · Version 2.5 · Information Practices
1. The short version
FamSafe is designed around clear relationship separation: Family circles share location and device management with authorised guardians, while Friend connections support messaging and optional, consent-based location sharing without guardian access.
Separate circles
Friends cannot manage your device, view your app limits, or access guardian capabilities. Only verified parent-child links carry guardian permissions.
Visible indicators
Location sharing and monitoring require explicit on-device permissions and present persistent system indicators on supported Android versions.
Directional consent
Sharing location with a friend is directional. Each person can stop sharing their own location from their profile settings.
2. Information the service may process
The data processed by FamSafe depends on the account type, active features, and device permissions granted:
| Category | Examples | Purpose |
|---|---|---|
| Account & profile | Username, email, display name, profile avatar, and account identifiers. | Registration, authentication, profile identification, and customer support. |
| Relationships & pairing | Invitation tokens, QR pairing state, parent-child links, friend links, and consent records. | Enforcing role separation and controlling who may communicate or view information. |
| Location & safe zones | GPS coordinates, timestamps, accuracy radii, safe zone boundaries, and enter/exit events. | Displaying live location on the Safety Radar map and triggering authorised safe zone alerts. |
| Routines, screen time & device rules | Battery level, network status, installed package names, per-app usage minutes, daily device-wide screen time, routine schedules and revision history, Extra Time requests and time-bounded grants, device commands, and device acknowledgement receipts. | Displaying device telemetry, synchronizing scheduled routines, granting temporary screen time extensions, and enforcing guardian app limits on child devices. |
| Communications & SOS emergencies | Encrypted chat messages, call-signalling states, emergency SOS broadcasts (trigger type, initial snapshot GPS, live tracking updates during active incidents, guardian response status, delivery receipts, cancellation or resolution reasons), and emergency SOS audio recordings. | Delivering private family messages, connecting peer-to-peer calls, alerting guardians during emergencies, and maintaining a verifiable safety audit trail. |
| Website filtering and activity | Domain rules, filter status and, when reporting is enabled, domain contact counts and times. | Applying rules and showing authorised guardians contacts observed by the DNS filter. A contact can come from an app or a background lookup. These reports do not include full URLs, searches or page contents. |
| Device protection & removal approval | Protection settings and policy versions; Device Administrator, overlay, Usage Access and Accessibility states; location, microphone and notification permission changes; enforcement/location service and website-filter/VPN health, restriction readiness and report times; tamper event history; removal requests, decisions and approval-use status; account, device, request and event identifiers and a phone manufacturer/model label. | Applying guardian protection settings, explaining unavailable permissions or services, reviewing reported changes, managing removal approval and delivering authorised protection alerts. |
| Technical records | IP addresses, device identifiers, push notification tokens, error logs, and security audit entries. | Delivering notifications, diagnosing service faults, and preventing fraudulent access. |
When you open a support ticket, FamSafe stores its subject, messages, status and account details for support staff to review. If you choose to include web diagnostics, the ticket can also contain browser and operating system details, window size and connection status. In the Android app, the optional device details are the phone model, Android version, FamSafe version, battery level and network type (Wi-Fi or mobile); they never include location, messages, contacts or browsing. Keep passwords, invitation codes and private location details out of your message.
Protection status, alerts and removal approval
When protection monitoring is in use, FamSafe records which relevant permissions and services the phone reports as available, when a change was observed and received, and whether restrictions could be enforced. Website-filter health can include VPN status, installed VPN app package names and browser compatibility notes. These records describe protection readiness; a permission change, approval being used or a phone going silent does not by itself prove that FamSafe was uninstalled.
A removal request includes the child account, a request identifier, policy version, phone label such as manufacturer/model, request and expiry times, and its status: pending, approved, declined, cancelled, expired, used or no longer applicable. Guardian decisions record the deciding account and time. The service also records approval validity and use separately from device-confirmed deactivation. These records help the family review what was requested, authorised and actually reported.
The device account can view its own protection status and removal request. Authorised guardians can view the protection records allowed by their current monitoring or device-management permissions. Service administrators can also review protection information and manage approvals under their administrative permissions. Friends, siblings and unrelated ordinary accounts do not gain access or approval authority through those relationships.
Current protection push notifications use identifiers and state flags to tell the app to fetch authorised details. Older recovery workflows can send an authorised one-time PIN in a push notification. Detection and notification delivery are best-effort and may stop or be delayed when permissions are disabled, the app is stopped or removed, or a device is offline. See protection record retention below and the uninstall-protection FAQ.
3. Why information is used and legal bases
Under UK data protection law (UK GDPR Article 6), each processing activity must have an established lawful basis:
- Contractual necessity (Article 6(1)(b)): Providing basic user accounts, authenticating sign-in sessions, routing chat messages, delivering push notifications, and presenting the web dashboard.
- Consent (Article 6(1)(a)): Sharing directional live location with Friends. Consent is explicitly chosen when pairing or adjusting profile sharing, and can be withdrawn at any time.
- Legitimate interests & Parental responsibility (Article 6(1)(f)): Enabling parents and legal guardians to protect their children, monitor locations within a verified family circle, configure safe zones, and manage app access.
- Vital interests (Article 6(1)(d)): Transmitting urgent emergency SOS alerts and location coordinates to designated family guardians when an emergency trigger is activated.
4. Who may see or receive information?
Access depends on the account role, relationship permissions and the feature in use:
- Authorised family guardians: Verified parents and guardians in a family circle can view connected child locations, device status, and configured app rules.
- Authorised service administrators: Protection records and removal approvals can also be reviewed and managed under existing administrative permissions for service administration and safety review.
- Connected friends: Friends can receive messages and see your live location if you share it with them. They cannot access app lists, device controls or guardian permissions.
- Infrastructure service providers: We use self-hosted UK VPS infrastructure for API and database operations; Google Maps SDK for ephemeral vector tile rendering; and Firebase Cloud Messaging (Google) for push notification delivery using device tokens. No third-party advertising networks or data brokers have access to user data.
- Legal and safety disclosures: Information may be disclosed where required by law, court order, or to protect vital life-safety interests.
5. Children and family privacy
Location and device monitoring directly impact a young person’s privacy. FamSafe is designed so that children understand what is being monitored and why.
For younger FamSafe users
“Your family uses FamSafe to stay connected and help keep you safe. When location or screen time controls are turned on, your parents or guardians can see your location and app usage. Friends cannot see your phone rules or control your device. If you have questions about what is shared, talk with your parent or guardian.”
If your family turns on location sharing, screen-time controls or website activity reporting, talk together about what the guardian can see and why. Review the settings together when they change. Friends cannot see these family controls or reports. On a phone with family controls, signing out of FamSafe or needing to sign in again does not switch those settings off. Until the child signs in again with the same account, the phone does not send location, messages or reports, and FamSafe tells the child it cannot reach the family.
6. SOS, calling, microphone and audio
FamSafe supports voice communication and emergency alerts. Different audio paths operate under distinct technical rules:
- Peer-to-peer WebRTC calls: Real-time voice and video calls connect directly between devices via WebRTC with server-mediated signaling. Call audio and video streams are transient and are not recorded or saved on FamSafe servers.
- Live ambient microphone stream: An authorized family guardian may request a live audio stream from a paired child device. This audio is transmitted as a transient real-time stream; it is not recorded, analyzed, or stored on the server.
- SOS emergency audio recordings: When SOS is triggered, supported configurations can record and send an emergency audio clip to eligible recipients. Such clips may be kept with the emergency messages.
- SOS incident lifecycle and audit trail: An incident can contain available location, alert events, delivery information, guardian responses and closure details. Device permissions and connectivity affect what is available. An alert being sent does not establish that a person received or viewed it.
- Presentation window vs. retention: The recent incident view shows active alerts and recently closed alerts. Its 24-hour window controls what is shown. Records may remain stored after the window ends.
7. Security, storage and retention
FamSafe applies technical and organisational measures to safeguard data against unauthorised access, alteration, or disclosure.
How long is data kept?
FamSafe stores account and relationship information to operate the service. Recent locations shown on the map do not represent the full storage lifetime of location records.
Screen-time records, device command acknowledgements, routine revisions and Extra Time records support reporting and rule management. Removing a family link changes what that relationship can access. Historical records may remain stored.
Scheduled cleanup removes website activity records dated more than 14 days before the current date. SOS incident records, audit entries and emergency messages may be retained for safety review beyond the recent incident display window.
On Android, FamSafe keeps its sign-in credentials encrypted with a key held by the Android Keystore and excludes them from device backups and transfers. Account deletion removes account data and linked records through the service’s deletion process. Some records may be handled separately, including audit entries and backups. You can ask about specific records using the privacy contact below.
Protection record retention
The service stores the latest protection report and replaces it with later reports. Removal requests and approval records are kept with their protection policy and can be replaced by a later request or policy change. A request or approval expiring ends its use; expiry is not a deletion timer.
Tamper history is limited to the most recent 200 events per account; an inbox may show fewer. That count limit, a report freshness window or an alert display window is not a storage period. Protection settings, removal records and the latest tamper states currently have no fixed automatic age-based deletion schedule. Administrative alerts, audit entries, queued delivery records and backups can remain separately.
Removing a family link changes access but does not erase the history. Account deletion does not itself guarantee that all cached protection records or backups are immediately removed. Ask privacy@famsafe.co.uk about specific records, retention or deletion requests.
Data storage & international transfers
Core databases and application services are hosted on VPS infrastructure in the UK and European Union. Third-party notification delivery via Google Firebase and map tile loading via Google Maps SDK may involve infrastructure operated by Google LLC under standard contractual clauses and UK data bridge safeguards.
Cookies and website technologies
FamSafe uses browser storage for dashboard sign-in and to continue an invitation in the same browser tab. These public pages do not use advertising or analytics trackers.
8. Your data protection choices and rights
Under UK data protection law, users and guardians have specific rights regarding personal data:
- Access: Request a copy of the personal data held about you or your paired child account.
- Rectification: Correct inaccurate account details or update profile information.
- Erasure (Right to be Forgotten): Request the deletion of your account, location history, and message data.
- Restriction & Objection: Object to specific processing activities or request limits on how data is handled.
- Portability: Request your account data in a structured, machine-readable format.
- Withdraw Consent: Disable Friend location sharing or revoke optional device permissions at any time.
To exercise any of these rights, contact our privacy team at privacy@famsafe.co.uk.
9. Operator and contact information
Service operator: FamSafe (operated by DevYield, United Kingdom). Registered office details are available upon request for legal correspondence.
Privacy enquiries: privacy@famsafe.co.uk
Product support: Open a FamSafe support ticket
If you have an unresolved concern regarding our data handling, you have the right to lodge a complaint with the UK supervisory authority:
Information Commissioner's Office (ICO)
Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF
Helpline: 0303 123 1113