← Back to Privacy Policy
Transparency Matrix
Data Flow & Privacy Architecture
Callro is architected around strict data minimization. Every decision to block or allow an incoming call executes locally on your device using Android's native screening APIs. Below is our comprehensive data flow matrix.
Umer Mustafa
Founder & Architect
| Data Category | Processing Location | Destination | Purpose & Retention |
|---|---|---|---|
| Contacts & Address Book | On-Device Only | Never Transmitted | Stays strictly on your handset. Callro never requests the READ_CONTACTS permission and never uploads your address book. |
| Incoming Phone Number | Encrypted Transmission | OpenCNAM (HTTPS) | The 10-digit incoming caller number is transmitted securely to resolve Caller ID name metadata in real time. |
| Call Audio & Recordings | On-Device Only | Never Transmitted | Zero audio access. Callro does not intercept, record, listen to, or upload any call audio or voicemail content. |
| Crash & Diagnostic Logs | Encrypted Transmission | Firebase Crashlytics | Anonymized crash stack traces, OS versions, and device model telemetry used exclusively for diagnosing application stability. |
| Trial & License State | Encrypted Transmission | Supabase Backend | Hashed trial ID stored in Supabase to validate 7-day trial eligibility without collecting personal identity. |
| Customer Support Messages | Encrypted Transmission | Vindication Support | Inquiries submitted via support chat or email are retained up to 12 months for ticket resolution and service follow-up. |
| Local Shield Call History | On-Device Only | Local device storage | Records blocked and screened call outcomes locally on the phone. Can be cleared by the user at any time in Settings. |
| Carrier Telemetry & Battery Optimization | Pending Confirmation | [Pending Android-side confirmation] | [Pending Android-side confirmation] |
Zero Address Book Reads
Unlike legacy caller ID apps that crowd-source directory listings by uploading user contact books, Callro never requests access to your contacts. Your personal address book stays private on your phone.
Hashed Trial ID Validation
Trial validation uses a hashed trial ID stored in Supabase. Raw personal identifiers and persistent account records are never maintained.