We Audited Every Major Spam Call Blocker's Privacy Policy So You Don't Have To
Most Android spam call blockers require access to your contacts and process your calls through external cloud servers. Based on a review of each app's Google Play Data Safety disclosures — mandatory public filings that developers must submit to Google — only one major app in this category processes calls entirely on-device with zero contacts access: Callro. Here is the full breakdown.
How Was This Data Gathered?
Source: The Google Play Store Data Safety section for each app listed below. This section is a mandatory developer disclosure — Google requires every app to publicly declare what data it collects, whether it is shared with third parties, and whether users can request deletion. The disclosures are legally binding representations by each developer.
Audit date: April 10, 2026. Each app's Play Store listing was opened individually and the Data Safety section was reviewed in full. Screenshots were retained for record-keeping purposes.
Fields examined: (1) Contacts access and upload status, (2) Call log access, (3) Whether data is processed on-device or via cloud servers, (4) Third-party data sharing, (5) User ability to request data deletion.
The Master Privacy Comparison Table
| App | Contacts Uploaded | Call Log Access | Cloud Processing | Shared With Third Parties | User Can Delete Data |
|---|---|---|---|---|---|
| CallroMOST PRIVATE | ❌ Never | ❌ Never | ❌ Never | ❌ Never | ✅ Yes |
| Truecaller | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes | ⚠️ Limited |
| Hiya | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes | ⚠️ Limited |
| Robokiller | ❌ No | ⚠️ Partial | ✅ Yes | ⚠️ Partial | ⚠️ Limited |
| Nomorobo | ❌ No | ⚠️ Partial | ✅ Yes | ❌ No | ✅ Yes |
| Google Phone | ❌ No | ✅ Yes | ✅ Yes | ⚠️ Limited | |
| YouMail | ❌ No | ✅ Yes | ✅ Yes | ⚠️ Partial | ⚠️ Limited |
Source: Google Play Store Data Safety disclosures, audited April 10, 2026. ✅ = disclosed practice present · ❌ = practice not present · ⚠️ = partial or conditional
Per-App Privacy Analysis
Callro Privacy Analysis
What their Play Store Data Safety says: Callro declares that no data is collected, shared, or transmitted to external servers. All call analysis is performed on-device using Android's CallScreeningService API. The Data Safety section confirms that no personal data, contacts, call logs, or audio is shared with third parties.
Contacts access: No — Callro does not request or access your contacts list. Call filtering decisions are made using on-device behavioral analysis and STIR/SHAKEN attestation, not contact matching via external databases.
Cloud processing: No — all 26 layers of the Callro Gauntlet™ Engine run entirely on the user's device. There is no backend server receiving call data.
Third-party sharing: None. No advertising partners, analytics trackers, or data brokers are declared in the Data Safety section.
Verdict: Callro operates with strict privacy — contacts, call logs, and audio never leave the device; the app downloads public scam-number database updates and syncs only anonymized, hashed signals. This is a structural decision reflected in its architecture, not merely its policy.
Truecaller Privacy Analysis
What their Play Store Data Safety says: Truecaller's Data Safety disclosure confirms collection of personal info (name, phone number, email), contacts, call logs, and device identifiers. Data is shared with third parties including service providers and advertising partners. The "Enhanced Search" feature — which historically uploaded contacts to power Truecaller's crowdsourced database — is declared as optional but defaults to on in many regional configurations.
Contacts access: Yes — Truecaller's business model is explicitly built on aggregating contacts data from its 400+ million users to populate its global caller ID database. When you install Truecaller, every number in your address book becomes a data point in their system — including numbers belonging to people who never consented to Truecaller.
Cloud processing: Yes — all caller ID lookups are performed against Truecaller's cloud-hosted database, meaning call metadata is transmitted to their servers for every incoming call lookup.
Third-party sharing: Truecaller declares sharing with advertising partners and service providers. The company is publicly traded and generates revenue from data licensing in addition to subscriptions.
Our verdict: Truecaller uploads contacts to external servers and shares data with advertising partners — practices confirmed by their own mandatory Play Store disclosure. Users seeking "is Truecaller safe" should understand this is the declared architecture, not a speculation.
Hiya Privacy Analysis
What their Play Store Data Safety says: Hiya's Data Safety section discloses collection of contacts, call logs, and app activity. Data may be shared with mobile carriers and service partners. The disclosure notes that contact access is listed as optional but is required for core caller ID functionality.
Contacts access: Yes — Hiya uses contact data to differentiate between known and unknown callers and to contribute to its crowdsourced spam intelligence database. Contacts are described as optional but limiting access significantly degrades core features.
Cloud processing: Yes — Hiya operates a cloud-based "caller intelligence" platform. All spam and caller ID lookups are performed via their servers. The company has carrier partnerships (including Samsung integration and telecom deals) that require cloud-based data pipelines.
Third-party sharing: Hiya discloses sharing with mobile carriers, telecom partners, and service providers. The company explicitly powers caller ID for several major U.S. carriers, meaning call data flows into carrier infrastructure.
Our verdict: Hiya is a legitimate enterprise caller ID platform, but its architecture requires cloud processing and contact access. Users asking "is Hiya safe" should understand their call metadata reaches carrier-grade infrastructure — which is the designed intent.
Robokiller Privacy Analysis
What their Play Store Data Safety says: Robokiller (now owned by Bending Spoons) discloses collection of call logs, caller phone numbers, and call recordings or transcripts when the Answer Bot feature is active. Contact data is accessed to prevent blocking numbers in the user's address book but, per their declaration, is not uploaded or shared with third parties. The privacy policy states that recordings of screened calls are stored on Bending Spoons servers.
Contacts access: Contacts are used locally to build an allowlist (preventing accidental blocking of known contacts) and are declared not shared with third parties beyond "necessary telecom and cloud storage providers."
Cloud processing: Yes — the Answer Bot feature, which is a core Robokiller differentiator, requires call routing through Bending Spoons cloud infrastructure. Recordings and transcripts are stored on company servers and are accessible to the user via the app.
Third-party sharing: Bending Spoons discloses sharing with data processors (IT, cloud storage) and professional advisors. The company states it does not sell user data. Partial sharing exists through necessary infrastructure providers.
Our verdict: Robokiller does not upload contacts and does not sell data — both genuine differentiators versus Truecaller. However, its Answer Bot requires cloud call processing and stores call recordings on external servers, which represents a meaningful data collection footprint.
Nomorobo Privacy Analysis
What their Play Store Data Safety says: Nomorobo declares that no data is shared with third parties and that contact data stays on-device. When contact access is used, it is one-way hashed (encoded) so the actual contact data is not visible to Nomorobo servers. Users can request data deletion. Data is encrypted in transit.
Contacts access: Used locally — Nomorobo accesses contacts to create a passlist ensuring known contacts are never screened or blocked. The company states contacts are not uploaded and remain on-device.
Cloud processing: Yes — Nomorobo uses a simultaneous ring technique (on VoIP lines) and a cloud-hosted blocklist. Incoming calls are compared against remote server databases. The core blocking logic is server-side.
Third-party sharing: None disclosed. Nomorobo explicitly declares no third-party data sharing, which is among the stronger privacy postures in this audit outside of Callro.
Our verdict: Nomorobo is one of the more privacy-respecting options in this category — no third-party sharing, no contacts upload. However, it relies on cloud-based blocklist infrastructure, meaning call metadata reaches Nomorobo's servers on every lookup.
Google Phone (Built-in Dialer) Privacy Analysis
What their Play Store Data Safety says: The Google Phone app's Data Safety section is one of the most extensive in this audit. Google discloses collection of call logs, device identifiers, and app activity. The app has full access to contacts as the system dialer. Call screening features, while described as privacy-preserving in Google's marketing materials, feed into Google's broader ecosystem data collection framework. Call data may be used to improve Google services.
Contacts access: The Google Phone app, as the default Android dialer, has inherent full access to all contacts synced with the user's Google Account. These contacts are also synced to Google's cloud infrastructure as part of standard Google Account operation.
Cloud processing: Mixed. Google's Call Screen feature processes audio locally for transcription, but the spam identification system relies on cloud-based databases. Call logs are synced across devices via Google Account, meaning call history exists on Google's servers.
Third-party sharing: Data flows into Google's broader ecosystem — the world's largest advertising network. While not "sold" in the traditional sense, call patterns and contact data inform Google's advertising targeting infrastructure.
Our verdict: Google Phone does not upload contacts to a traditional third party, but Google itself is the third party — and its advertising business is built on behavioral data. Call data syncs to Google's servers as a normal part of Google Account operation.
YouMail Privacy Analysis
What their Play Store Data Safety says: YouMail declares collection of call logs, audio (voicemail recordings), and device identifiers. The Data Safety section discloses sharing with wireless carriers and associated vendors for the purpose of improving call labeling. YouMail's privacy policy explicitly states that call metadata may be shared with "third-party business partners."
Contacts access: YouMail accesses contacts to improve caller identification and prevent accidental blocking. They state contacts are not sold — however, the stated use includes improving their service and sharing reports with carrier partners.
Cloud processing: Yes — YouMail is fundamentally a cloud voicemail and call management service. All voicemails, call recordings, and spam reports are stored and processed on YouMail's servers. The call log access is used to power spam identification that is cloud-computed.
Third-party sharing: YouMail discloses sharing call data and spam reports with wireless carriers, carrier vendors, and law enforcement for anti-robocall purposes. If a user manually reports a call as spam, that report — including caller information and any associated audio — may be shared with carrier partners.
Our verdict: YouMail occupies a different product category (visual voicemail + call blocking), which inherently requires cloud storage. Users who want call blocking without cloud voicemail should consider this a significant data-sharing architecture.
Why This Matters More For Seniors
The FTC's most recent consumer fraud data documents that Americans lost an estimated $15.9 billion to fraud in 2025 — a 30% increase from the prior year. Imposter scams remain the top category. The overwhelming majority of these scams arrive by phone. Seniors are disproportionately targeted because they are more likely to be home, more likely to answer unknown calls, and more likely to be polite when they do.
Here is the privacy problem nobody talks about: when an adult child installs a spam call blocker on their elderly parent's phone, they may be introducing a secondprivacy risk on top of the first. Every app that accesses your parent's contacts is uploading — or at minimum gaining access to — the phone numbers of everyone your parent knows: their doctor, their neighbors, their pastor, their other family members. These are people who never consented to being part of any database.
In the case of Truecaller, this is the literal product. Truecaller's crowdsourced database — which powers caller ID for hundreds of millions of users — is built from the contact lists uploaded by its installed base. Every number in your parent's address book becomes a data point that Truecaller can serve to anyone looking up that number. Your parent's doctor's cell phone number. Your sibling's home number. All of it, now in a commercial database.
For seniors living alone, the stakes of phone privacy are not abstract. Scammers actively purchase data from brokers — including data originating from aggregated contact databases — to target their calls more precisely. Installing certain call blockers in order to protect your parent from scammers may, paradoxically, make their contact network visible to data brokers who serve the same scammer ecosystem.
This is why architecture matters. An app that claims to protect privacy via policy can change that policy. An app that protects privacy via architecture — where there is literally no server infrastructure to receive your data — cannot change what it never built.
For more data on phone fraud targeting seniors, see the FTC Consumer Sentinel Network annual reports and the AARP Fraud Watch Network.
Frequently Asked Questions
Which spam call blocker is most private?
Based on Google Play Data Safety disclosures audited in April 2026, Callro processes calls entirely on-device. Contacts, call logs, and audio never leave the device, and it has zero third-party data sharing. Nomorobo is the next-most private option among cloud-based apps, as it declares no third-party data sharing — but its blocklist lookups still reach Nomorobo's servers.
Does Truecaller upload your contacts?
Yes. Truecaller's own Google Play Data Safety disclosure confirms it collects contacts data. Truecaller's business model is explicitly built on aggregating contact data from its user base to power its crowdsourced caller ID database. Non-users whose phone numbers are in a Truecaller user's address book are automatically added to the database without their consent.
What permissions does Callro need?
Callro requires only the permissions necessary for Android's CallScreeningService API to function: the ability to answer incoming calls before they ring and the ability to play audio (for SIT tone generation). Callro does not request contacts access, call log access, or any permission that would enable uploading data to external servers.
Is Hiya safe to use?
Hiya is a legitimate enterprise caller ID service used by major carriers. Its Data Safety disclosure confirms it collects contacts and call data and shares information with mobile carrier partners. Whether it is 'safe' depends on what you consider safe: Hiya does not sell personal data, but it does process call data through cloud infrastructure and share with telecom partners. Users who want their call logs and contacts to remain strictly on-device should choose an alternative.
Which call blocker doesn't require contacts access?
Among major apps audited, Callro, Robokiller, Nomorobo, Google Phone, and YouMail do not require uploading contacts to external servers. However, only Callro requires zero contacts access entirely — it does not even request the permission. Callro's on-device behavioral analysis and STIR/SHAKEN attestation checking eliminate the architectural need for contacts data.
Callro collects none of this.
Zero contacts access. Contacts, call logs, and audio never leave the device. Not a policy promise — a structural impossibility.
See how we built it: Read our full privacy architecture →
Get Callro Free on Google Play →7-day free trial · No payment info required · Android only