Privacy Policy

Effective date: July 13, 2026  ·  Last updated: July 13, 2026

This Privacy Policy explains how Caller ID: Block Spam Calls ("the App", "we", "us", or "our") handles information when you use our Android application distributed on Google Play (package com.traceo.callerid.message.tracker). By installing and using the App, you agree to the practices described here.

1. Information we process directly

Notification content (with your permission)

When you grant Notification Access, the App reads the notifications posted by other apps on your device so it can show you unread messages, build a notification timeline, and let you review recently dismissed alerts. This content is processed on your device to provide these features. We do not upload the body of your notifications to our own servers.

Caller and call information (with your permission)

When you grant Phone permission and (optionally) set the App as your default phone app, the App reads the incoming phone number so it can identify the caller and flag potential spam. To look up who is calling, the App sends that phone number, your country code, and a device identifier (Android ID) to our caller-ID service over an encrypted (HTTPS) connection, which returns the caller's name and any spam classification. This powers the on-call and caller-ID screens. The App does not upload your call history / call log.

Contacts you contribute (optional, with your permission)

The App includes an optional contact-contribution feature. If you enable it, the App uploads the names and phone numbers stored in your device's address book to our caller-ID service in order to build and improve caller identification and spam detection for you and other users. You are asked about this separately, and you can decline it while still using the rest of the App. To stop future uploads, turn the feature off or revoke the Contacts permission in Android Settings; to have previously uploaded contact data deleted, contact us using the details in Section 12. We do not upload contact email addresses or any other contact fields — only names and phone numbers.

Permissions the App requests

• Phone (READ_PHONE_STATE, READ_PHONE_NUMBERS, CALL_PHONE, ANSWER_PHONE_CALLS and related) — to place and receive calls as a phone app and to display caller identification during incoming calls.
• Contacts (READ_CONTACTS / WRITE_CONTACTS) — to show caller names, let you save numbers, and (optionally) contribute contacts to improve caller identification.
• Notification Access (BIND_NOTIFICATION_LISTENER_SERVICE) — to collect and display notifications so you can review unread messages and notification history.
• Advertising ID (com.google.android.gms.permission.AD_ID) — used by our analytics and, in ad-supported versions, our advertising and attribution partners as described below (required to be declared on Android 13+).
• Internet / Network state — to communicate with our caller-ID service and the SDK services listed below.

Permissions are only used to provide the features described in the App. Some features depend on your Android version, manufacturer customization, and device compatibility.

Local storage

The App stores your preferences (such as your chosen theme) and cached items locally on your device so it can function between sessions.

Support communications

If you email us for support, we receive your email address and the content of your message so we can respond.

2. Third-party SDKs we use

To understand stability, measure app usage, and — in ad-supported versions of the App — serve ads and measure installs, we embed the following third-party software development kits (SDKs). Each operator processes data under its own privacy policy. Separately, the App communicates with our own caller-ID service (described in Section 1) to identify callers and detect spam.

For advertising, we use Google's User Messaging Platform (UMP) consent flow where required (for example, for users in the EEA, UK, and Switzerland). Whether you see personalized or non-personalized ads depends on the consent choices you make in that flow.

Your choices regarding these SDKs

• Reset or delete your Advertising ID in Android Settings → Privacy → Ads (path may vary by device).
• Opt out of personalized ads through the in-app consent prompt or your Android ad settings.
• Withdraw consent at any time by emailing us at dumaserin100918@gmail.com.

3. What we do NOT collect

• We do not read or send your SMS text messages.
• We do not upload your call history / call log, and we do not upload your contacts unless you turn on the optional contact-contribution feature described in Section 1.
• We do not collect precise (GPS) location.
• We do not access your camera or microphone.
• We do not handle or store payment card data (the App has no in-app purchases).
• We do not sell or rent your personal data to data brokers.

Because the App is ad-supported, the advertising and attribution partners listed in Section 2 are considered our third-party partners and receive the data described there. We do not share your notification content or call data with them.

4. How we use information

• To identify callers and flag potential spam during incoming calls.
• To build and improve caller identification and spam detection, including from contacts you choose to contribute.
• To display unread messages, a notification timeline, and notification history.
• To serve ads in ad-supported versions of the App.
• To measure app stability and fix crashes.
• To measure installs and prevent fraudulent or invalid activity.
• To respond to your support requests.

5. Sharing & third parties

We share information only with the parties needed to operate the App:

• Our caller-ID service — operated by us on cloud hosting infrastructure. It receives the phone numbers you look up, your country code, your device identifier (Android ID), and, if you enable contact contribution, the names and phone numbers in your address book, in order to identify callers and detect spam.
• Google — Google Play distribution, Firebase (analytics & crash reporting), and, in ad-supported versions, AdMob (advertising).
• Adjust GmbH — install attribution and fraud prevention (ad-supported versions).
• Legal compliance — where required by law, legal process, or to protect rights and safety.

6. Data retention

• Firebase Analytics data: up to 14 months (Google default, configurable).
• Firebase Crashlytics individual records: up to 90 days.
• Adjust attribution data: up to 24 months.
• AdMob data: per Google's advertising-platform defaults.
• Caller-lookup and contributed contact data on our servers: retained while your installation is active and deleted on request (see Section 12) or when no longer needed to operate the service.
• Support emails: up to 24 months.
• On-device data (preferences, cached items) remains until you clear it or uninstall the App.

7. Your rights & choices

Depending on where you live, you may have rights under the GDPR (EEA/UK) or CCPA/CPRA (California), including the right to access, correct, delete, or port your personal data, and to opt out of cross-context behavioral advertising.

• You can manage ad personalization in Android Settings → Privacy → Ads and via the in-app consent prompt.
• You can revoke Notification Access, Phone, or Contacts permission at any time in Android Settings → Apps → Caller ID → Permissions. Revoking Contacts (or turning off contact contribution) stops further contact uploads.
• To exercise any right, email dumaserin100918@gmail.com. We aim to respond within 30 days.

8. Children's privacy

The App is intended for users aged 13 and older (or the minimum age required in your country). We do not knowingly collect personal information from children, and the third-party SDKs we use are not configured for child-directed treatment. If you believe a child has provided us with personal information, contact us and we will delete it.

9. International users

The App's service providers (Google, Adjust) may process data in the United States, the European Union, and other regions. Where required, these providers rely on safeguards such as the EU Standard Contractual Clauses (SCCs) for international data transfers.

10. Security

We rely on the Android application sandbox, scoped storage, and encrypted HTTPS connections to SDK endpoints to protect information. No method of transmission or storage is 100% secure, but we work to protect your data using industry-standard practices.

11. Changes to this policy

We may update this Privacy Policy from time to time. Material changes will be reflected by updating the "Last updated" date above and, where appropriate, through in-app notice or Google Play release notes. Continued use of the App after changes take effect constitutes acceptance of the revised policy.

12. Contact us

Questions about this Privacy Policy, or want to request deletion of data held by our caller-ID service? Email dumaserin100918@gmail.com, call (+84) 945 470 638, or visit our Support page.

Caller ID: Block Spam Calls does not claim to provide official caller information from telecom providers and only displays information available through supported Android APIs and the permissions you grant.