Truong Phat Fruits
Caller ID & Spam Call Blocker
Effective date: September 16, 2026 · Last updated: October 6, 2026
This Privacy Policy explains what Caller ID & Spam Call Blocker (the "app"), developed by Truong Phat Fruits ("we", "us"), accesses on your device, why it needs it, and what leaves your phone. It covers this app only.
Caller ID & Spam Call Blocker is a phone app that can act as your device's default dialer, default SMS app, and call screening app. Its features are:
These features are the only reason the app asks for the permissions listed below.
Android grants call and message handling through default handler roles, which you choose in a system dialog and can revoke at any time in Settings → Apps → Default apps:
The app works without these roles, with the corresponding features unavailable. The Call Screening and SMS roles require no separate runtime permission — Android grants them through the role itself.
The app never asks for SMS or call log permissions before you have made it your default SMS or phone app. If you later choose a different default SMS or phone app, the app stops reading your messages or call log; its Messages or Recent screen then only offers to make it the default again.
| Permission | Why the app needs it | Leaves your device? |
|---|---|---|
CALL_PHONE | Place a call when you tap a number or use the dial pad. | No |
READ_CALL_LOG | Show your Recent calls list, the call history of a single number, and call statistics — only while the app is your default phone app. The app does not write to or delete from your call log; its own list of blocked calls is kept separately, as described in section 3. | No |
READ_CONTACTS | Show saved contact names and let you select a contact for calling, favorites, or blocking. If access has not been granted, the Contacts screen explains why and opens Android's app settings only when you tap Grant access. | No |
WRITE_CONTACTS | Delete a saved contact from Android's contacts provider when you choose and confirm Delete contact. The app requests this permission if it has not already been granted. Denying it prevents the deletion. | The app does not upload the contact. Any synchronization of this change is controlled by your device's contacts account settings. |
READ_SMSRECEIVE_SMSSEND_SMSRECEIVE_MMS | Receive, display, organize, and send messages — only while the app is your default SMS app — and send a quick reply you choose when you decline a call. | No |
SYSTEM_ALERT_WINDOW | Draw the caller ID card over the incoming call screen. Optional — the app checks whether you granted it and simply shows nothing if you did not. | No |
POST_NOTIFICATIONS | Show notifications for calls, missed calls, and new messages. Optional — without it the app records the event but shows no notification. | No |
ACCESS_NOTIFICATION_POLICY | Let you reach the Do Not Disturb setting from the app's Sound screen. The app never changes your Do Not Disturb state on its own. | No |
WRITE_SETTINGS | Apply the ringtone you pick in the app's Sound screen as your device's default ringtone. Optional — the app writes only the one value you chose and changes nothing else in your system settings. | No |
ACCESS_NETWORK_STATE | Tell "no internet connection" apart from other failures when opening the store page for updates or ratings. | No |
AD_ID | Required by Google for apps whose advertising SDK reads the advertising identifier. See section 6. | Yes — see section 6 |
The app does not request location, camera, microphone, photo or file access, nor READ_PHONE_STATE, READ_PHONE_NUMBERS, WRITE_CALL_LOG or WRITE_SMS. If a future version needs any of them, this policy will be updated before that version ships.
All call, message, and contact processing happens locally. Specifically:
None of the above is backed up to our systems, and the app disables Android's automatic cloud backup for its own data.
To be explicit, we do not collect, upload, store on our systems, sell, or share for advertising purposes:
The app uses Google Firebase (Analytics, Crashlytics, and Remote Config) to understand how the app is used, to be notified when it crashes, and to enable or disable features remotely without shipping an update. Firebase may collect:
This data is processed by Google under Firebase's privacy terms and Google's Privacy Policy.
The app is free and supported by advertising, served through Google AdMob. Ads appear on onboarding, home, settings, and results screens.
No ad is ever shown during a call. The in-call screen, the caller ID overlay, and the screen shown after a call end are kept free of advertising by design. If the app is opened because your phone is ringing, it skips its start-up screen and any ad on it, and goes straight to the call.
The app uses Google's User Messaging Platform (UMP) to check whether ads may be requested and to display a consent form when required by its configured messages. This check may use a choice saved from a previous session. Permission to request an ad does not necessarily mean that you agreed to personalized advertising or to every partner's data use.
Where UMP requires a privacy options entry, you can reopen its form from Settings → Privacy options inside the app. Current limitation: changing your choice there does not immediately update the app's advertising controls or reconfigure attribution services already running in the current session. The app checks UMP again when it next starts; this is not a guarantee that all partner tracking stops after a change. The attribution behavior described below also applies.
To serve ads and to measure which marketing campaign led to an install, the app includes software from the following partners. These SDKs may access your device's advertising identifier, IP address, and coarse device information — never your contacts, calls, or messages:
Each partner handles that data under its own privacy policy, linked above. The app starts configured attribution services after its UMP check returns, including when that check does not allow ad requests. In that case, the app supplies negative consent flags to AppsFlyer, enables Meta's Limited Data Use setting and disables its automatic app-event logging and advertising ID collection, and disables TikTok's advertising ID collection. These settings do not stop all data processing: attribution services can still run and receive app usage events.
In the current version, the app also uses UMP's permission to request ads to choose these attribution settings. It does not separately evaluate consent for each attribution partner or purpose. The UMP flow described here does not control Firebase analytics or crash reporting in section 5.
You can limit advertising tracking on your device at any time through Settings → Privacy → Ads, where Android lets you delete or reset your advertising ID and opt out of personalized advertising.
We use the limited information described in sections 5 and 6 only to:
We do not use your information to build a profile of you as an individual, and we do not make automated decisions about you that have legal effects.
We do not sell your personal information, and we do not share it with data brokers.
The only parties that receive data are the service providers listed in sections 5 and 6, each acting for the purpose stated there. Beyond that, we may disclose information if we are legally required to — to comply with a valid court order, subpoena, or other lawful request — or where necessary to protect the rights, property, or safety of our users, the public, or us.
If our business is ever merged, acquired, or its assets sold, any information we hold may be transferred as part of that transaction; this policy would continue to apply to it until replaced by a policy you are notified of.
The strongest protection here is structural: the sensitive data — your contacts, calls, and messages — never travels anywhere, so it cannot be intercepted in transit or exposed in a breach of our systems. It is stored in the app's private storage, which Android isolates from other apps on your device.
Data sent to our analytics and advertising partners travels over encrypted connections. No method of transmission or storage is completely secure, however, and we cannot guarantee absolute security. Keeping your device's operating system up to date and protected by a screen lock is the most effective step you can take.
You are in control of every permission the app uses:
Depending on where you live, you may also have the right to access, correct, delete, or restrict the processing of your personal data, or to object to it, under laws such as the GDPR or the CCPA. Write to us at the address in section 15 and we will respond within the period required by the applicable law.
This app is not directed to children under 13, and we do not knowingly collect personal information from them. If you believe a child has provided us with personal information, contact us and we will delete it.
The app may open external pages — the Google Play store listing, or an advertiser's page when you tap an ad. Those destinations are not operated by us and are governed by their own privacy policies. We have no control over, and take no responsibility for, their content or practices.
We may update this Privacy Policy as the app changes. The revised version will be posted at this address with a new "Last updated" date, and any change that materially affects how we handle your data will be made before the version introducing that change is released. We encourage you to review this page from time to time.
If you have any question about this Privacy Policy, or want to exercise any of the rights described above, contact us:
Truong Phat Fruits
Email: collinswood769927@gmail.com
Policy URL: https://truongphatfruits.netlify.app/trusted-call-block-privacy-policy.html