CallSafe Privacy Policy
Effective date: September 15, 2026
CallSafe ("we", "our", "the app") is a mobile application that helps you block spam calls, scam calls, and manage a personal blocklist and contacts on Android. This Privacy Policy explains what data CallSafe collects, how it is used, who it may be shared with, and the choices you have. It applies to the Android version of CallSafe (package name com.devpress.callsafe) and any other platform we may release in the future.
If you do not agree with this policy, please do not use the app.
1. Summary
- CallSafe screens and blocks calls entirely on your device using a local database — we do not see or receive the content or audio of your calls.
- We do not collect your name, email address, precise (GPS) location, SMS content, photos, financial information, or health information.
- We collect a small amount of data only when you choose to submit a community spam/scam report, and separately, standard advertising data through Google AdMob to show ads.
- You are not required to create an account. Reports are linked only to an anonymous, randomly generated device ID — never to your identity.
2. Data We Collect and Why
2.1 Call & Contacts Data — processed locally, not uploaded to us
| Data | Why we access it | Where it's stored |
|---|---|---|
| Incoming phone numbers (via Android's Call Screening system) | To check the number against your blocklist and community risk data on your device and decide whether to silently block it or warn you. | Never leaves your device. |
| Call log (blocked/rejected calls) | To show your "Blocked" history tab inside the app. | Local database on your device (SQLite). |
| Device contacts (only if you tap "Sync from device") | To let you mark contacts as trusted so they're never mistakenly blocked. | Copied into CallSafe's own local contact list on your device; your system contacts list is only read, never modified. |
2.2 Data You Submit — Community Spam/Scam Reports
When you choose to report a number as spam or scam (Report tab, or "Report to community" button), we send the following to our backend (Google Firebase / Cloud Firestore):
- The reported phone number (normalized)
- The report type/category you selected (e.g. Scam, Spam)
- An optional free-text description you type in
- The country automatically detected from the phone number's own country code (e.g. "VN") — you do not enter this yourself
- An anonymous, randomly generated ID tied to your device (via Firebase Anonymous Authentication) — this is not your name, email, phone number, or any other identity
2.3 Advertising
CallSafe shows ads (a banner, and an optional rewarded video ad you can choose to watch to manually refresh protection data) through Google AdMob. AdMob may collect and process device identifiers (such as the Android Advertising ID), general usage/interaction data, and IP address to serve and measure ads, and — on iOS — will request App Tracking Transparency permission before showing personalized ads. This data is collected and processed by Google, not by us directly. See Google's Privacy Policy.
You can opt out of personalized advertising at any time via your device settings (Android: Settings > Google > Ads > Opt out of Ads Personalization).
2.4 Device / Network Country Code
To automatically apply the correct country calling code when you add or block a number (instead of assuming one country for everyone), CallSafe reads your SIM card's country (via TelephonyManager.simCountryIso — no special permission required) or, if unavailable, your device's language/region setting. This value is used only for this local calculation and is never transmitted anywhere.
2.5 What We Do NOT Collect
We do not collect: your name, email address, physical/precise (GPS) location, SMS message content, photos or files, financial or payment information, health information, or any government ID. CallSafe does not currently read, filter, or have access to your SMS messages.
3. Local Storage
Most of CallSafe's data — your blocklist, call history cache, in-app contacts, and community risk data you've synced — is stored locally on your device in a private SQLite database, not accessible by other apps and not uploaded to our servers. Uninstalling the app or clearing its app data permanently deletes this local data.
4. Third-Party Services
CallSafe uses the following third-party services, each governed by its own privacy policy:
- Google Firebase (Cloud Firestore, Authentication) — stores community reports and issues anonymous device IDs. firebase.google.com/support/privacy
- Google AdMob (Google Mobile Ads SDK) — serves ads. policies.google.com/privacy
We do not sell your data to third parties.
5. Data Retention & Deletion
- Local data (blocklist, in-app contacts, cache) stays on your device until you delete it in-app or uninstall CallSafe.
- Community reports you submit are retained indefinitely to keep community protection data accurate, and cannot currently be deleted through the app itself. If you would like a report you submitted removed, contact us at the email below with the phone number and approximate date/time of the report, and we will make a reasonable effort to remove it.
6. Children's Privacy
CallSafe is not directed at children under 13 (or the relevant age of digital consent in your country), and we do not knowingly collect data from children. If you believe a child has provided us data, contact us and we will delete it.
7. Security
We rely on industry-standard practices — including Google Firebase's built-in security rules, which restrict clients to creating only their own reports and reading aggregate community data, never editing or deleting others' data — to protect data in transit and at rest. However, no method of transmission or storage is 100% secure.
8. International Data Transfers
Data sent to Firebase may be processed and stored on Google Cloud infrastructure located outside your country, including in the United States.
9. Your Choices
- You can deny, or later revoke, the Contacts/Call Log permissions in your device's app settings at any time; CallSafe's local blocking features will simply have less data to work with.
- You can delete any number from your blocklist or in-app contacts at any time from within the app.
- You can opt out of ad personalization via your device's ad settings.
10. Changes to This Policy
We may update this Privacy Policy from time to time. Material changes will be reflected by an updated "Effective date" above. Continued use of the app after changes means you accept the revised policy.
11. Contact Us
If you have questions about this Privacy Policy, or wish to request deletion of a report you submitted, contact us at:
[YOUR-SUPPORT-EMAIL@example.com]
Appendix — Android Permissions Reference
| Permission | Purpose |
|---|---|
READ_CONTACTS | Read-only, to let you sync device contacts into your in-app trusted contacts list. |
READ_CALL_LOG | Read-only, to show blocked/rejected calls in the "Blocked" tab. |
WRITE_CALL_LOG | Required by the call-log library for all its calls (including read-only ones); not used to write or export data. |
READ_PHONE_STATE | Required by the call-log library; also used to read the SIM's country code for default calling-code detection (see §2.4). No call/audio content is read. |
READ_PHONE_NUMBERS | Required by the call-log library; not actively used by CallSafe. |
USE_FULL_SCREEN_INTENT | Lets a spam/scam warning open full-screen immediately when your phone is locked and a risky number calls. No data collection involved. |
POST_NOTIFICATIONS | Shows call-screening result notifications (e.g. "Number blocked", "Warning: possible scam"). No data collection involved. |
SYSTEM_ALERT_WINDOW | Special permission you must grant manually in Settings; lets the spam/scam warning appear on top of other apps when your screen is unlocked. No data collection involved. |
| Advertising ID (via Google AdMob SDK) | Used by Google to serve and measure ads — see §2.3. |