Privacy Policy
Privacy Policy
This Privacy Policy explains what Caller ID does with information when you use it. It applies to the iOS app published under the bundle identifier get.caller.id.spam.blocker by Yoto Kimura (“we”, “us”).
1. Information the app uses on your device
Contacts
With your permission (iOS asks once, and you can change the answer any time in Settings → Privacy & Security → Contacts), the app reads your iPhone address book to:
- show a saved name instead of an unknown number;
- find duplicate, incomplete and unsaved entries in Clean up;
- match contacts while you type on the keypad;
- create a
.vcfbackup file that you choose to share.
When you add, edit, merge or delete an entry, the app writes that change directly to the iPhone address book through Apple’s Contacts framework. Contact data is not transmitted to us or to anyone else. It is not used for advertising. There is no upload step, no sync and no copy on any server.
The app never requests the contact notes entitlement; notes you write about a number are stored privately by the app instead.
Numbers you check
Number identification is entirely offline. Published numbering-plan data (country and area codes, telecom circles, original operator allocations, line types, time zones, known nuisance ranges) is compiled into the app binary. Looking up a number performs no network request, so no server of ours — and no third party — is told which numbers you check, call or block.
Data the app stores on your device
| What | Why |
|---|---|
| Block list and prefix rules | To block calls and to hand the list to iOS |
| Numbers you reported as spam | To show the verdict on future calls |
| Private notes and your history with a number | Shown on the number report screen |
| Reminders | Scheduled as local notifications |
| Preferences (theme, haptics, dialling region, language) | App settings |
All of it is kept in the app’s own sandbox on the device. The block list is additionally written into a shared App Group container so that the iOS Call Directory extension can read it. Deleting the app deletes all of this data. We hold no copy, so there is nothing for us to return or erase on request.
Call blocking
An iPhone app cannot listen to, record or intercept calls, and this one does not try. iOS allows an app to hand over a list of numbers through a Call Directory extension; iOS then does the blocking and identification itself. iOS never tells the app who called you, and no call information is sent anywhere.
2. Information processed by third parties
To keep the app free and working, it uses the services below. Each acts as an independent controller of the data it collects, under its own privacy policy.
Advertising — Google AdMob, Meta Audience Network, Meta (Facebook) SDK
The app shows banner, native, interstitial and app-open ads through Google AdMob, with Meta Audience Network served through AdMob mediation. These services may process your device’s advertising identifier (IDFA), an app-scoped identifier, IP address, coarse location derived from the IP address, device model, OS version, language and ad interaction events in order to select, deliver, cap and measure ads, and to detect invalid traffic. Apple’s SKAdNetwork is used for privacy-preserving install attribution.
- App Tracking Transparency. The IDFA is used only if you allow tracking when iOS asks. If you decline, ads still appear but are non-personalised. You can change this at any time in Settings → Privacy & Security → Tracking.
- Consent in the EEA, UK and Switzerland. Google’s User Messaging Platform shows a consent form before any ad loads, and your choices are passed to the ad networks. You can reopen that form from the app’s settings where offered.
- Never used for ads: your contacts, your call and lookup history, your block list, your reports and your notes. They are not shared with advertising partners, because they never leave the device.
Analytics and stability — Google Firebase
Firebase Analytics records anonymous usage events (screens opened, features used, session counts) together with device model, OS version, language, coarse country and an app-instance identifier. Firebase Crashlytics collects crash reports: stack traces, device state and OS version at the moment of a crash. Firebase Remote Config fetches the app’s configuration (ad unit IDs, pacing, legal links, support address). None of these carry your contacts or the numbers you look up.
Push notifications — OneSignal
If you allow notifications, OneSignal receives a push token together with device model, OS version, language, time zone and basic app-usage signals so that a notification can be delivered to your device. Reminders you create are local notifications scheduled by iOS and involve no server at all. Turning notifications off in iOS Settings stops both.
Purchases — Apple and RevenueCat
If in-app purchases are offered, payment is handled entirely by Apple; we never see your payment details. Purchase receipts and an anonymous purchase identifier may be processed by RevenueCat to determine whether your ad-free entitlement is active.
Their policies
- Google (AdMob, Firebase) — policies.google.com/privacy
- Meta (Audience Network, SDK) — facebook.com/privacy/policy
- OneSignal — onesignal.com/privacy_policy
- RevenueCat — revenuecat.com/privacy
- Apple — apple.com/legal/privacy
3. What we do not do
- We do not upload, copy or crowd-source your address book, and the app’s directory is not built from anybody’s uploaded contacts.
- We do not sell or rent personal information, and we do not “share” it for cross-context behavioural advertising as those terms are defined under US state privacy laws, beyond the advertising described in section 2.
- We do not track your location. A map on the number report shows where a number range is registered — not where a phone is.
- We do not record, listen to or intercept calls or messages. iOS does not permit it and the app contains no such capability.
- We do not ask you to create an account, and we do not collect your name, email address or phone number.
4. Legal bases (EEA / UK)
Where the GDPR or UK GDPR applies: on-device processing of your contacts and lookups is carried out to perform the service you asked for (Art. 6(1)(b)) and is confined to your device. Personalised advertising and analytics rely on your consent (Art. 6(1)(a)), collected through the consent form and Apple’s tracking prompt, and withdrawable at any time. Non-personalised advertising, crash reporting and security rely on our legitimate interest in keeping a free app running and stable (Art. 6(1)(f)).
5. Your choices and rights
- Contacts access — grant or revoke in Settings → Privacy & Security → Contacts. Revoking stops the address-book features; the rest of the app keeps working.
- Tracking — Settings → Privacy & Security → Tracking.
- Advertising consent — reopen the consent form from the app’s settings, or reset it by reinstalling.
- Notifications — Settings → Notifications → Caller ID.
- Erasure — deleting the app removes every piece of on-device data described in section 1, permanently. Because we store nothing on a server, this is complete deletion.
- Access, correction, portability, objection, complaint — for anything held by the third parties in section 2, contact them directly using the links above, or write to us and we will help. You may also complain to your local data protection authority.
If you are in California, Virginia, Colorado, Connecticut or a state with comparable law, you may exercise the rights that law gives you by writing to the address below. We do not discriminate against anyone who exercises a privacy right.
6. Children
Caller ID is not directed to children under 13 (or under the minimum age of digital consent in your country), and we do not knowingly collect their personal information. If you believe a child has provided personal information through the app, contact us and we will act on it.
7. International transfers
The third-party services in section 2 operate globally and may process data in the United States and other countries. Where required, those transfers rely on the European Commission’s Standard Contractual Clauses or an equivalent mechanism put in place by the provider.
8. Retention and security
On-device data stays until you delete it in the app or delete the app. Third-party data is retained under each provider’s own schedule. On-device data is protected by iOS app sandboxing and device encryption; keep a passcode enabled on your iPhone. No method of electronic storage is completely secure, but keeping your data on your own device removes the largest risk that caller-ID apps normally carry.
9. Changes
We may update this policy as the app changes. The “last updated” date at the top always reflects the current version, and material changes will be announced in the app or on the App Store listing.
Comments