Effective date: August 13, 2026
This policy explains what information the FaceCall Android app ("FaceCall", "the app", "we") accesses, how it is used, and what is shared with third parties. FaceCall is a phone-dialer replacement app that lets you call your contacts using their photo instead of remembering names or numbers.
FaceCall does not operate a server, does not require you to create an account, and does not transmit your contacts, call history, or photos anywhere. Everything the app needs to function is stored only on your device. The one exception is advertising: FaceCall shows ads through Google AdMob, and Google's advertising SDKs collect a limited set of data on their own behalf, described below.
To provide its core features, FaceCall accesses the following, all of which stay on your device:
This data is stored in a local database and local file storage on your device. It is explicitly excluded from Android's automatic cloud backup and device-transfer features, so it does not leave your device even through those Android system features. It is deleted if you clear the app's data or uninstall FaceCall.
| Permission | Purpose |
|---|---|
| Contacts | Show your contacts and their photos so you can call them. |
| Camera | Take a photo to use as a contact's picture. |
| Call phone / Answer calls / Read call log / Read phone state | Place calls, and — if you set FaceCall as your default phone app — detect, answer, and manage incoming and outgoing calls, and show recent call history. |
| Notifications / Full-screen intent | Show the incoming-call screen and caller photo, including over the lock screen. |
| Internet / Network state | Used only to load banner ads (see below). No other feature in the app needs internet access. |
FaceCall shows banner ads using Google AdMob (Google Mobile Ads SDK) and manages ad-related consent using Google's User Messaging Platform (UMP). To show and measure ads, these Google SDKs may collect:
This data is collected and processed by Google, not by us, under Google's Privacy Policy and Google's advertising technology policy. FaceCall does not pass your contacts, call history, or photos to AdMob or any advertising service — those never leave the app's local storage.
If you are in the UK, EEA, or another region where a consent form is required, FaceCall shows Google's consent form before requesting ads, and your choice controls whether ads are personalized. You can change your ad consent choice at any time by reopening that form (via the app), or manage ad personalization for your device generally in your Google Account's Ad Settings.
Locally stored data (contacts cache, call history, photos, preferences) is kept until you clear FaceCall's app data or uninstall the app, either of which permanently deletes it from your device. Because FaceCall has no server, there is no separate copy for us to delete on request — clearing app data or uninstalling is the complete deletion.
FaceCall is not directed at children under 13 and we do not knowingly collect personal information from children. If you believe a child has provided personal information through the app, contact us using the details below and we will address it.
Depending on where you live, you may have rights to access, correct, or delete personal data, and to object to or restrict certain processing (for example under the GDPR or CCPA/CPRA). Because FaceCall stores your contacts, call history, and photos only on your device, you exercise these rights directly by using the app's own settings or by clearing app data / uninstalling. For data collected by Google's advertising SDKs, see Google's own privacy controls linked above.
We may update this policy as the app changes. Changes will be posted on this page with a revised effective date.
Questions about this policy or FaceCall's data practices can be sent to:
purushotham541@gmail.com