Privacy Policy
Effective Date: 31 July 2026
This Privacy Policy explains how the Contacts application ("we", "our", or "us") collects, uses, and protects your information. Our app is designed to function as your primary phone dialer and contact manager. We prioritize your privacy and ensure that your sensitive personal communication data remains securely on your device.
1. Information Collection and Use
To provide core dialer and contact management functionality, our app requests access to specific device permissions. We do not upload, transmit, or store your contacts or call logs on any external servers. That specific data stays locally on your device.
A. Contacts Data (READ_CONTACTS, WRITE_CONTACTS)
Why we need it: To display your address book, allow you to search for contacts, and enable you to create, edit, or delete contact profiles within the app.
How it is handled: Your contact data is accessed and modified strictly locally on your device. We do not upload or share your contacts with any third party.
B. Call Logs (READ_CALL_LOG, WRITE_CALL_LOG)
Why we need it: To display your recent call history (incoming, outgoing, missed calls) and allow you to clear or manage these logs.
How it is handled: Call log data is processed entirely locally. We do not transmit this data over the internet.
C. Phone & Calling State (CALL_PHONE, ANSWER_PHONE_CALLS, READ_PHONE_STATE)
Why we need it: To allow the app to initiate outgoing calls, answer incoming calls, and detect when the phone is ringing or in an active call. This is required for the app to function as your default dialer.
How it is handled: This information is used in real-time to manage your phone calls and is never recorded or transmitted by us.
D. Device Display & System Alerts (USE_FULL_SCREEN_INTENT, SYSTEM_ALERT_WINDOW, POST_NOTIFICATIONS)
Why we need it: To display incoming call screens over other apps, allow the app to function correctly as a primary dialer, and provide persistent notifications during an ongoing call or for important alerts.
E. System & Hardware Functions (VIBRATE, RECEIVE_BOOT_COMPLETED)
Why we need it: To vibrate your device for incoming calls and to ensure background services (like call handling and notifications) initialize properly when you restart your phone.
F. Network & Advertising Access (INTERNET, ACCESS_NETWORK_STATE, AD_ID)
Why we need it: To connect to the internet to serve advertisements, collect anonymous crash reports, and gather app usage analytics. The AD_ID permission is used strictly to provide personalized or non-personalized advertising and to analyze ad performance.
2. Third-Party Services
While your personal communication data (Contacts and Call Logs) is never shared, we have integrated third-party SDKs and libraries to support app monetization, stability, and feature delivery. These services may collect certain device identifiers and usage data:
Google AdMob: We use Google AdMob to display advertisements within the app. AdMob may collect and use your device's Advertising ID (AD_ID), network state, and app interaction data to provide tailored advertisements and monitor invalid traffic.
Google Firebase: We use Firebase Analytics, Firebase Crashlytics, Firebase Remote Config, and Firebase Cloud Messaging. These services collect device identifiers, crash logs, diagnostic traces, and anonymous app interaction data. This helps us understand how the app is used, deliver push notifications, and quickly fix technical bugs.
These third-party services operate under their own privacy policies. For more information on how Google uses data when you use our app, please visit: Google’s Privacy & Terms.
3. Data Security
We value your trust in providing us with access to your phone’s core communication features. Because all processing of your contacts and call logs happens locally on your device, your sensitive personal data is as secure as the device itself. Data collected by third-party services (such as crash logs and device IDs) is transmitted securely and handled according to standard industry protocols. We recommend utilizing your device's built-in security features (like screen locks and encryption) to protect your device.
4. Children’s Privacy
Our application does not knowingly collect personally identifiable information from children under the age of 13. The app is a general utility designed for managing device communications.
5. Changes to This Privacy Policy
We may update our Privacy Policy from time to time. We will notify you of any changes by updating the "Effective Date" at the top of this policy. You are advised to review this Privacy Policy periodically for any changes.
6. Contact Us
If you have any questions or suggestions about our Privacy Policy, please contact us via mail.
This Privacy Policy explains how the Contacts application ("we", "our", or "us") collects, uses, and protects your information. Our app is designed to function as your primary phone dialer and contact manager. We prioritize your privacy and ensure that your sensitive personal communication data remains securely on your device.
1. Information Collection and Use
To provide core dialer and contact management functionality, our app requests access to specific device permissions. We do not upload, transmit, or store your contacts or call logs on any external servers. That specific data stays locally on your device.
A. Contacts Data (READ_CONTACTS, WRITE_CONTACTS)
Why we need it: To display your address book, allow you to search for contacts, and enable you to create, edit, or delete contact profiles within the app.
How it is handled: Your contact data is accessed and modified strictly locally on your device. We do not upload or share your contacts with any third party.
B. Call Logs (READ_CALL_LOG, WRITE_CALL_LOG)
Why we need it: To display your recent call history (incoming, outgoing, missed calls) and allow you to clear or manage these logs.
How it is handled: Call log data is processed entirely locally. We do not transmit this data over the internet.
C. Phone & Calling State (CALL_PHONE, ANSWER_PHONE_CALLS, READ_PHONE_STATE)
Why we need it: To allow the app to initiate outgoing calls, answer incoming calls, and detect when the phone is ringing or in an active call. This is required for the app to function as your default dialer.
How it is handled: This information is used in real-time to manage your phone calls and is never recorded or transmitted by us.
D. Device Display & System Alerts (USE_FULL_SCREEN_INTENT, SYSTEM_ALERT_WINDOW, POST_NOTIFICATIONS)
Why we need it: To display incoming call screens over other apps, allow the app to function correctly as a primary dialer, and provide persistent notifications during an ongoing call or for important alerts.
E. System & Hardware Functions (VIBRATE, RECEIVE_BOOT_COMPLETED)
Why we need it: To vibrate your device for incoming calls and to ensure background services (like call handling and notifications) initialize properly when you restart your phone.
F. Network & Advertising Access (INTERNET, ACCESS_NETWORK_STATE, AD_ID)
Why we need it: To connect to the internet to serve advertisements, collect anonymous crash reports, and gather app usage analytics. The AD_ID permission is used strictly to provide personalized or non-personalized advertising and to analyze ad performance.
2. Third-Party Services
While your personal communication data (Contacts and Call Logs) is never shared, we have integrated third-party SDKs and libraries to support app monetization, stability, and feature delivery. These services may collect certain device identifiers and usage data:
Google AdMob: We use Google AdMob to display advertisements within the app. AdMob may collect and use your device's Advertising ID (AD_ID), network state, and app interaction data to provide tailored advertisements and monitor invalid traffic.
Google Firebase: We use Firebase Analytics, Firebase Crashlytics, Firebase Remote Config, and Firebase Cloud Messaging. These services collect device identifiers, crash logs, diagnostic traces, and anonymous app interaction data. This helps us understand how the app is used, deliver push notifications, and quickly fix technical bugs.
These third-party services operate under their own privacy policies. For more information on how Google uses data when you use our app, please visit: Google’s Privacy & Terms.
3. Data Security
We value your trust in providing us with access to your phone’s core communication features. Because all processing of your contacts and call logs happens locally on your device, your sensitive personal data is as secure as the device itself. Data collected by third-party services (such as crash logs and device IDs) is transmitted securely and handled according to standard industry protocols. We recommend utilizing your device's built-in security features (like screen locks and encryption) to protect your device.
4. Children’s Privacy
Our application does not knowingly collect personally identifiable information from children under the age of 13. The app is a general utility designed for managing device communications.
5. Changes to This Privacy Policy
We may update our Privacy Policy from time to time. We will notify you of any changes by updating the "Effective Date" at the top of this policy. You are advised to review this Privacy Policy periodically for any changes.
6. Contact Us
If you have any questions or suggestions about our Privacy Policy, please contact us via mail.