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

2. Data We Collect and Why

2.1 Call & Contacts Data — processed locally, not uploaded to us

DataWhy we access itWhere 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):

This data is not private. To let every CallSafe user benefit from up-to-date community protection, submitted reports (phone number, type, description, and anonymous reporter ID) are readable by all users of the app, and cannot currently be self-service edited or deleted once submitted. Please do not include your own or anyone else's personal information (name, address, etc.) in the free-text description field.

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:

We do not sell your data to third parties.

5. Data Retention & Deletion

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

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

PermissionPurpose
READ_CONTACTSRead-only, to let you sync device contacts into your in-app trusted contacts list.
READ_CALL_LOGRead-only, to show blocked/rejected calls in the "Blocked" tab.
WRITE_CALL_LOGRequired by the call-log library for all its calls (including read-only ones); not used to write or export data.
READ_PHONE_STATERequired 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_NUMBERSRequired by the call-log library; not actively used by CallSafe.
USE_FULL_SCREEN_INTENTLets a spam/scam warning open full-screen immediately when your phone is locked and a risky number calls. No data collection involved.
POST_NOTIFICATIONSShows call-screening result notifications (e.g. "Number blocked", "Warning: possible scam"). No data collection involved.
SYSTEM_ALERT_WINDOWSpecial 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.