Summary & Core Architectural Principles
FamilyShield is engineered from the ground up to protect families and vulnerable individuals from phone fraud, spoofing, and manipulation scams. We adhere to strict data minimization, clear platform separation between Android and iOS capabilities, local cryptographic processing, and complete user ownership of all personal data.
- Zero Raw Call Audio Recording or Cloud Upload: FamilyShield never records, eavesdrops on, transcribes, or uploads private phone conversations to any remote server.
- Platform-Differentiated Call Protection: Android screens incoming phone numbers via native
CallScreeningService; iOS operates via Apple’s isolatedCallDirectoryExtension, maintaining a pre-compiled local blocklist without runtime access to cellular calls. - Pseudonymized Contact Matching Tokens: Address book numbers and names are processed into SHA-256 tokens on-device. Plaintext address books and contact names are never transmitted to our servers.
- Monetization & Advertising Transparency: We never sell personal information to data brokers. Free-tier users may receive non-personalized or personalized ads via Google AdMob (with European UMP consent controls); Pro subscribers enjoy an ad-free experience.
- Robust Row-Level Security (RLS) & Encryption: All user database tables in Supabase enforce strict RLS policies, TLS 1.3 encryption in transit, and AES-256 encryption at rest.
- Absolute Right to Complete Erasure: Users can permanently delete their account and purge all associated data within the mobile app or via our publicly accessible web deletion portal.
1. Introduction & Scope
FamilyShield Safety Technologies Inc. ("FamilyShield", "we", "us", or "our") develops and operates the FamilyShield mobile application for Android and iOS, associated backend APIs, and web services. This Privacy Policy governs the collection, processing, storage, sharing, and permanent deletion of data when you download, install, or use FamilyShield.
By downloading, accessing, or using FamilyShield, you acknowledge the privacy practices and operational workflows detailed in this policy. If you do not agree with this policy, please refrain from using or installing our application.
Privacy Officer & Contact Details
2. Information We Collect or Process
We collect and process only the minimal data strictly necessary to provide scam call warnings, family emergency alerts, secure pairing, and account management:
2.1 Account & Identity Data
When you create an account, authenticate, or manage your profile, we process:
- Email Address & Display Name: Provided directly by you or via Google Sign-In / Sign in with Apple (including Apple Private Relay email aliases).
- Supabase Authentication UUID: A cryptographically unique, non-human-readable user identifier generated during account registration.
- Profile Role: Designating whether you operate as a Guardian / Protector or a Protected Family Member.
- Authentication Metadata: Session refresh tokens and account creation timestamps stored securely on your device.
2.2 Family Linking & Pairing Data
To safely coordinate scam protection and emergency escalation between family accounts, we process:
- Temporary Pairing Codes: Ephemeral 6-digit codes and signed QR tokens (expiring automatically after 15 minutes).
- Pairing Link State: Relationship records establishing which Guardian is paired with which Protected Person.
- Family Verification Secrets: Cryptographically generated HMAC-SHA256 secrets used to generate daily rotating verification codes for family safety checks.
- Emergency Safe-Words: User-configured verification phrases encrypted locally on-device and protected by biometric authentication (Face ID / Biometric Prompt).
2.3 Call Screening & Threat Detection Data (Platform Differentiated)
Platform Separation Notice:
Android: Uses the native CallScreeningService API to evaluate incoming phone numbers against local blocklists and community databases in real time, displaying safety overlays.
iOS: Uses Apple’s CXCallDirectoryProvider extension. The app pre-populates a local database of known scam numbers which the iOS system uses to identify or block callers. The iOS application does not and cannot access, intercept, or inspect incoming cellular caller numbers or ongoing phone conversations at runtime.
When scam detection runs on supported devices, the data processed includes:
- Normalized caller phone numbers (used strictly for risk lookup against curated blocklists and community databases).
- Call timestamp, direction, and duration metadata (synchronized to the family dashboard only for alert context).
- Computed risk classifications (Safe, Suspicious, High Risk, Impersonation Threat).
- User-submitted community reports (phone numbers flagged voluntarily by users to protect other community members).
2.4 On-Device Voice Clone & Synthetic Speech Analysis (Android Only)
On supported Android devices with speakerphone mode active, users can optionally enable synthetic speech and AI voice clone detection. When activated:
- Audio buffers are captured from the microphone solely to compute acoustic spectral entropy and voice artifact features.
- 100% On-Device RAM Processing: Audio samples exist only in temporary volatile memory and are discarded within milliseconds.
- Zero Cloud Transmission & Zero Recording: No audio files, voice recordings, or transcripts are ever written to disk or sent to any server.
2.5 Contact Matching & Impersonation Prevention
To prevent spoofed calls from impersonating family members, the app allows local contact matching:
- Contact phone numbers and names are normalized and converted into cryptographic SHA-256 tokens locally on your device.
- Only the pseudonymized hashes (
phone_hashandname_hash) are synchronized to your private, RLS-protected database table. - Raw address books, contact names, notes, and unhashed numbers are never uploaded or readable by our backend.
- Contact protection is entirely optional and can be enabled, disabled, or purged at any time in Settings.
2.6 Subscription, In-App Purchase & Advertising Data
- Subscriptions (RevenueCat): We process anonymous RevenueCat App User IDs, transaction dates, product identifiers, and active Pro entitlement status to verify subscription rights. All financial and payment data is handled exclusively by Apple App Store and Google Play In-App Billing.
- Advertising (Google AdMob): Free-tier users may receive advertisements served by Google Mobile Ads. AdMob collects advertising identifiers (IDFA on iOS where authorized, GAID on Android), IP address, and coarse diagnostic telemetry to prevent fraud, manage frequency capping, and serve relevant ads. European users can customize or revoke consent anytime via the in-app Privacy Options form. Pro subscribers receive a completely ad-free experience.
2.7 Diagnostics & Device Telemetry
- Firebase Cloud Messaging (FCM): Push notification device tokens used solely to route urgent family scam alerts.
- Firebase Crashlytics: Anonymous crash traces, device hardware models, and OS versions used strictly for diagnosing fatal crashes.
- Firebase Analytics: Aggregated, non-personally identifiable product interaction events and screen navigation flows to optimize user experience.
3. How We Use Information
Collected information is used exclusively for safety, communication, and core application functionality:
- Authenticating user sessions and validating family pairing relationships.
- Calculating scam risk scores and delivering incoming call warnings.
- Transmitting immediate push alerts to designated family Guardians when high-risk calls occur.
- Enabling biometric safe-word confirmation during suspected emergency voice clone scams.
- Managing Pro subscription access and eliminating advertisements for paid subscribers.
- Serving frequency-capped ads to free-tier users in compliance with Google Play and Apple advertising policies.
- Detecting system defects, preventing unauthorized abuse, and resolving user support requests.
4. Local Processing vs. Cloud Processing Architecture
FamilyShield operates an edge-first privacy architecture designed to process sensitive indicators locally on your device whenever technically feasible:
Processed 100% On-Device
- • Acoustic voice clone frequency analysis (RAM only)
- • SHA-256 contact normalization and hashing
- • Biometric safe-word decryption (Keychain / KeyStore)
- • iOS CallKit blocklist compilation
- • 24-hour scam verdict caching
Synchronized Cloud Infrastructure
- • Supabase Auth user profiles & session tokens
- • Active family pairing relationships
- • Real-time Guardian push alert routing (FCM)
- • Global community scam number blocklist
- • Encrypted call threat history for family dashboard
6. Permissions & Device Access
FamilyShield requests the following specific system permissions based on platform and feature use:
Android System Permissions
CALL_SCREENING_SERVICE&READ_PHONE_STATE: Required to detect incoming phone numbers and display real-time scam risk overlays.POST_NOTIFICATIONS: Required on Android 13+ to deliver immediate family scam warnings and call alerts.READ_CONTACTS: Used strictly on-device to compute SHA-256 tokens and identify trusted callers.RECORD_AUDIO: Optional. Used strictly for real-time acoustic AI voice clone analysis on speakerphone calls. Subject to prominent in-app disclosure. Zero audio is stored or uploaded.CAMERA: Used strictly to scan family pairing QR codes.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS: Ensures background call screening operates reliably during incoming calls.
iOS System Capabilities & Disclosures
Call Directory Extension: Allows FamilyShield to supply Apple CallKit with a verified list of known scam phone numbers for OS-level identification and blocking.NSContactsUsageDescription: Prompts for permission to hash contact numbers locally for impersonation matching.NSCameraUsageDescription&NSPhotoLibraryUsageDescription: Used to scan or import family pairing QR codes.NSFaceIDUsageDescription: Authenticates the user before revealing the encrypted family safe word.User Notifications (remote-notification): Delivers time-sensitive family alerts.
7. Data Storage & Security Protections
We implement multi-layered technical controls to safeguard family data:
- Row-Level Security (RLS): Every user-owned PostgreSQL table in Supabase enforces granular RLS policies. Authenticated JWT claims guarantee that users can access only their own records and those of active, authorized family links.
- Encryption in Transit: All communication between mobile applications, web portals, and backend APIs is encrypted using TLS 1.3 / HTTPS.
- Encryption at Rest: Database volumes, backup archives, and Supabase storage are encrypted at rest using AES-256.
- Hardware-Backed Secure Local Storage: Auth tokens and secrets are stored in Android KeyStore (EncryptedSharedPreferences) and iOS Keychain via
flutter_secure_storage.
8. Data Retention Schedule
We retain data only for as long as necessary to provide safety services and maintain account synchronization:
| Data Category | Active Retention Period | Deletion Trigger |
|---|---|---|
| Account Profile & Auth Tokens | Lifetime of active account | Account deletion request |
| Call Threat Logs & Alerts | Retained while account is active | Manual log clearance or account deletion |
| Contact Match Tokens (SHA-256) | Duration of contact protection toggle | Toggle off in Settings or account deletion |
| Pairing Codes & QR Tokens | 15 minutes | Automatic expiration or successful link |
| Audio Buffers (Voice Clone Detection) | 0 seconds (volatile RAM only) | Immediate discard after feature computation |
| Crash Traces & Analytics | 90 days to 14 months (Firebase default) | Automated provider TTL aging |
9. Account Deletion & Your Privacy Rights
You have absolute control over your personal data. You have the right to access, export, rectify, or permanently erase your data at any time.
9.1 How to Delete Your Account
You can initiate immediate and permanent account deletion directly inside the app, or outside the app via our official web portal:
In-App Deletion
Open FamilyShield $\rightarrow$ Shield Settings $\rightarrow$ Account & Security $\rightarrow$ Delete Account. Confirm your intent to trigger atomic backend erasure.
Official Web Deletion Portal
In full compliance with Google Play and Apple Store requirements, request complete erasure without opening the app at: FamilyShield Web Deletion Portal.
When your account deletion is processed:
- Your user authentication record and JWT credentials in Supabase Auth are permanently removed.
- All paired family links, pairing codes, and verification secrets are dissolved atomically.
- Your call logs, alert histories, contact matching tokens, and device push tokens are purged.
- Local cryptographic caches, Keychain items, and Keystore tokens are cleared immediately.
10. Children’s Privacy
FamilyShield is intended for adult caregivers, parents, seniors, and family guardians. It is not directed to children under 13 years of age. We do not knowingly collect personal information directly from children under 13. If you believe a child under 13 has provided personal information without verifiable parental consent, please contact us immediately to have the data expunged.
11. International Data Transfers
Our cloud infrastructure is hosted within secure data centers in the United States. If you access FamilyShield from the European Economic Area, United Kingdom, or other international regions, your information will be transferred to and processed in the United States under standard data protection mechanisms and encrypted transmission protocols.
12. Third-Party Service Providers
FamilyShield integrates the following verified third-party SDKs to provide core services:
13. Changes to This Privacy Policy
We may update this Privacy Policy periodically to reflect new features, platform policy changes, or regulatory requirements. When updates occur, the "Last Updated" timestamp at the top of this document will be revised, and active users will receive notice via an in-app banner or push alert for material changes.
14. Contact Us
For questions, privacy inquiries, or data subject requests, please contact our team: