Elite Dialer Privacy Policy
Privacy Policy for Elite Dialer: Phone & Contacts
Last Updated: October 14, 2026
Elite Dialer (“we,” “our,” or “us”) develops the Elite Dialer: Phone & Contacts mobile application (the “App”). This Privacy Policy explains what the App accesses on your device, why, and — just as important — what we do not do with it.
Elite Dialer is a local-first utility: it replaces your phone’s default Phone and Contacts apps, and almost everything it does happens entirely on your device. The exceptions are the spam-number list (Section 2) and Google’s AdMob and Firebase services (Section 3), each described there in full.
1. Information the App Accesses, and Why
The App requests the Android permissions below because it is designed to be used as your device’s default Phone and Contacts app — each permission maps to a specific feature. None of these permissions is used to send your contacts, call history, voicemail, or messages anywhere; the only data that leaves your device is the limited advertising, analytics, and device data collected by Google’s AdMob and Firebase services (Section 3) and the one-way spam-number download (Section 2).
Contacts and accounts — READ_CONTACTS, WRITE_CONTACTS, GET_ACCOUNTS
To show your contact list, let you create, edit, merge duplicate, and organize contacts, and to read which account (Google, SIM, local, etc.) each contact belongs to so account-specific contacts display and sync correctly. All read and write operations happen through Android’s own Contacts Provider on your device.
Phone and call log — READ_PHONE_STATE, CALL_PHONE, ANSWER_PHONE_CALLS, MANAGE_OWN_CALLS, READ_CALL_LOG, WRITE_CALL_LOG
To place calls when you tap a number, detect and display incoming calls with your chosen call screen, let you answer/decline/manage calls from the App, and show your call history. Call state and call log data are read and written locally and are never transmitted off your device.
Voicemail — com.android.voicemail.permission.ADD_VOICEMAIL, READ_VOICEMAIL, WRITE_VOICEMAIL
To show your visual voicemail list and play back messages your carrier delivers. Voicemail audio and metadata are handled locally between the App and your carrier’s voicemail system.
Camera — CAMERA
Only used if you choose to take a new photo for a contact. The App never accesses the camera on its own, and photos you take this way are saved as that contact’s photo, locally.
Bluetooth — BLUETOOTH, BLUETOOTH_CONNECT
To route call audio to a connected Bluetooth headset or car kit during a call. No data is shared with the Bluetooth device beyond the audio of the call itself, exactly as a phone call normally works.
App Lock / Call Lock (biometrics, PIN, password) — USE_BIOMETRIC, USE_FINGERPRINT
If you turn on App Lock or Call Lock in Settings, the App can require your fingerprint/face (via Android’s own Biometric system, which never shares your biometric data with the App itself — the App only receives a yes/no result) or a PIN/password you set. A PIN or password you set is stored in the App’s private on-device storage and is never transmitted anywhere. We recommend using a PIN/password you don’t reuse elsewhere, and system biometrics (fingerprint/face) where your device supports it, since that avoids storing a secret at all.
Display over other apps — SYSTEM_ALERT_WINDOW
Used for optional floating features you can enable: the floating call-notes bubble during a call, and the missed-call popup. Both are local UI drawn over other apps while active; neither sends data anywhere.
Sensors — proximity, accelerometer, and (on devices that have one) magnetometer
The proximity sensor dims the screen during a call to prevent accidental touches. If you turn them on in Settings, the same sensors also power two optional hands-free gestures: Raise to Answer / Flip to Decline (answer or silence a ringing call by lifting or flipping the phone) and Rain Mode (shake the phone to answer, decline, or end a call — built for when your hands are wet, cold, gloved, or busy). All of this sensor listening runs only while a call is active, inside the App’s own call-handling component, and every reading is used immediately on-device and never stored or transmitted.
Accessibility Service — Volume key & Do Not Disturb control (BIND_ACCESSIBILITY_SERVICE, a special permission granted separately in Android’s own Accessibility settings, not a normal app permission)
If you turn this on in Call Settings, the App can recognize a specific volume-button combination and use it to toggle Do Not Disturb. This service exists for that one purpose only: it does not read, record, log, or react to anything displayed on your screen or inside any other app, and Android requires every accessibility service to be enabled manually, one at a time, in system settings. Before the App sends you to Android's Accessibility settings it shows a separate on-screen disclosure explaining what the service does, why it is needed and what it can and cannot see, and it only continues if you tap "Agree and continue"; if you tap "No thanks" (or "Not now"), nothing is enabled and the rest of the App works exactly as before. No data from this service is collected, stored or shared.
Notifications and alarms — POST_NOTIFICATIONS, SCHEDULE_EXACT_ALARM, RECEIVE_BOOT_COMPLETED, WAKE_LOCK, VIBRATE, ACCESS_NOTIFICATION_POLICY
To show call, missed-call, voicemail, and “Remind me to call” notifications; to fire Call Reminders and Fake Calls at the exact time you set, including after a device restart; and to vibrate for notifications and (if you use Do Not Disturb controls) check or adjust your device’s interruption policy. None of this involves sending data anywhere.
Storage — WRITE_EXTERNAL_STORAGE (used only on Android versions where this permission is required for the features below; on newer Android versions the App uses scoped storage instead)
To let you export and import contacts as vCard (.vcf) files, and to create local backups of your contacts and call-related settings that you explicitly choose to create. These files are written to and read from your own device’s storage; we do not upload them anywhere.
Internet — INTERNET
Used for downloading the community-maintained spam-number list described in Section 2, serving ads via AdMob, and supporting Firebase services (Analytics and Messaging).
A permission appearing in the App’s manifest does not mean it is always active — several of the above (camera, Bluetooth, overlay display, biometrics) are only ever used when you actively use the corresponding feature.
2. Spam Number List
To flag likely spam calls, the App periodically downloads a public, community-maintained list of reported spam numbers from the open-source CallShield project (covering the US and Canada). This is a one-way download: the App fetches the published list and checks incoming numbers against it entirely on your device. Your phone number, your contacts, and your call history are never sent to CallShield, to us, or to any other server as part of this or any other feature.
3. Third-Party Services
Elite Dialer includes Google’s AdMob SDK to show ads that support the App’s continued development. AdMob (and the Google Play services it relies on) can collect and process data such as your advertising ID, device and app information, IP-based approximate location, and ad interaction data to show and measure ads; it may also set a limited amount of this information in line with Google’s own data practices — see Google’s Ads Privacy & Terms for the full detail, which Elite Dialer itself does not control. Showing ads through AdMob is disclosed in the App’s Data Safety section on Google Play.
The App also uses Firebase Analytics and Firebase Messaging (by Google) to collect app interaction data (such as screens viewed and features used), diagnostic and performance information, and device identifiers (including a Firebase installation ID and push token), and to manage push notifications. Firebase processes this data in accordance with Google’s Privacy Policy to help us analyze app performance and improve the user experience.
Elite Dialer does not use Crashlytics or any third-party ad networks beyond AdMob.
4. Data Security
Your contacts, call logs, voicemail, and settings are stored using Android’s standard per-app encrypted storage, the same protection every properly-built Android app relies on. Because none of this data is transmitted to or stored on any server we control, there is no remote database of your information that could be breached. If you enable a PIN or password for App Lock / Call Lock, it is stored in the App’s private on-device storage, inaccessible to other apps.
5. Data Sharing
We do not sell your personal data. Your contacts, call history, voicemail, and messages stay on your device: the App has no mechanism to transmit them anywhere, and no such feature is planned. The limited data described in Section 3 (approximate location derived from your IP address, app interactions, diagnostics, and device or advertising identifiers) is collected by Google’s AdMob and Firebase SDKs and shared with Google for advertising, analytics, and fraud prevention, security, and compliance. This collection is required for those services to function and is encrypted in transit. You can reset or delete your advertising ID, or opt out of ads personalization, in your Android settings (Settings > Privacy > Ads).
6. Children’s Privacy
The App is a general-purpose phone and contacts utility and is not directed at children under 13 (or the relevant minimum age in your region). We do not knowingly collect personal data from children; the only data collected is the limited advertising, analytics, and device data described in Section 3, which is collected from all users in the same way. If you believe a child has provided personal data through the App, contact us at the email address above and we will help resolve it.
7. Changes to This Privacy Policy
We may update this Privacy Policy to reflect future app changes or platform policy changes. Any update will change the “Last Updated” date above; material changes will also be called out in the app’s update notes on Google Play.
8. Open-Source Notices
Elite Dialer includes code and data from the following open-source projects.
CallShield (spam-number data)
Community-reported spam numbers (US & Canada), from the CallShield project.
MIT License
Copyright (c) 2026 SysAdminDoc
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
libphonenumber (phone number parsing)
Google’s library for parsing, formatting, and validating international phone numbers, from the libphonenumber project.
Copyright (C) 2009 The Libphonenumber Authors
Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
9. Contact Us
Questions about this Privacy Policy or how the App handles data can be sent to:
Email: mohit.d.can@gmail.com
Comments
Post a Comment