Privacy Policy
Last Updated: December 22, 2025
This Privacy Policy describes how No Calls ("we," "our," or "us") collects, uses, and discloses your information. This policy is designed to comply with the Google Play User Data Policy.
1. Data Collection and Usage Overview
A. Call Screening Data (Core Functionality)
To fulfill its core purpose of blocking unwanted calls, No Calls utilizes the Android CallScreeningService.
- Data Collected: Incoming phone numbers.
- How it is used: The app processes incoming phone numbers locally on your device to compare them against your Whitelist.
- Data Sharing: This data is NEVER transmitted to our servers or any third parties. It is processed in real-time on your device.
- Storage: Blocked calls are logged in a local database on your device (SQLite) for your history. You can clear this history at any time.
B. Contact List (Optional Feature)
If you enable the "Whitelist Contacts" feature, the app requires the READ_CONTACTS permission.
- Data Collected: Phone numbers from your device's contacts.
- How it is used: To verify if an incoming caller is in your contacts list so the app relies on your address book to allow the call ("allow-listing").
- Data Sharing: Your contacts are NEVER uploaded, shared, or transmitted off your device. The check is performed 100% locally.
C. Device & App Data
We collect limited, non-personally identifiable data to ensure app stability and manage subscriptions.
- App Performance: Crash logs and diagnostics (via Firebase Crashlytics) to help us fix bugs.
- Device IDs: Ephemeral identifiers (e.g., App Instance ID) used solely for managing your Pro subscription status (via RevenueCat).
2. Third-Party Data Safety Section
For the purposes of the Google Play Data Safety Form, here is how our data handling maps to Google's definitions:
| Data Type | Collection? | Shared? | Purpose |
|---|---|---|---|
| Contacts | No (Accessed Locally Only) | No | App Functionality (Whitelisting). Data never leaves the device. |
| Phone Number | No (Accessed Locally Only) | No | App Functionality (Call Blocking). Data never leaves the device. |
| Device or other IDs | Yes | Yes (Trusted 3rd Party) | App Functionality, Fraud Prevention (RevenueCat, Firebase). |
| Crash Logs | Yes | Yes (Trusted 3rd Party) | Analytics (Firebase). |
Note: "Collected" in Google Play terms usually means data transmitted off the device. Since our contact and call processing is local-only, we do not "collect" this data in the traditional sense, but we access the permission.
3. Third-Party Services
We partner with the following providers, who adhere to strict data protection standards:
- Google Play Services: For billing and license verification.
- RevenueCat: For subscription infrastructure. Privacy Policy
- Firebase Analytics: For usage metrics. Privacy Policy
4. Permissions Disclosure
android.permission.BIND_SCREENING_SERVICE: Necessary to block calls.android.permission.READ_CONTACTS: Necessary to whitelist your friends and family.com.android.vending.BILLING: Necessary to process Pro subscriptions.
5. Data Retention
- Local Logs: Retained on your device until you uninstall the app or clear data.
- Analytics: Retained by Firebase for 14 months (standard retention).
6. Children’s Privacy
Our Service does not allow-list or target anyone under the age of 13. We do not knowingly collect personally identifiable information from children under 13.
7. Contact Us
If you have questions about this policy or our data practices, please contact us at: Email: [email protected]