Privacy Policy for CallersHunt
Effective Date: July 2026
1. Introduction Welcome to CallersHunt. We are committed to protecting your privacy and ensuring transparency regarding how we handle your data. This Privacy Policy explains what information we collect, how we use it, and the choices you have when using the CallersHunt mobile application.
CallersHunt operates as a default dialer and SMS handler application. To provide our core functionalities—real-time caller identification, spam blocking, and direct messaging—we require access to sensitive device permissions. We do not sell, rent, or share your personal communication data with unauthorized third parties.
2. Information We Collect and the Permissions We Request To provide you with a functional and seamless experience, CallersHunt requires access to specific device data. We only request permissions that are strictly necessary for the app’s core functionality.
A. Call Log Data (READ_CALL_LOG, WRITE_CALL_LOG, PROCESS_OUTGOING_CALLS)
-
Why we need it: To function as your default phone handler, display your recent call history, identify incoming missed or suspicious calls, and enable our spam call blocking features.
-
How we use it: This data is processed locally on your device to display your call history and check incoming numbers against spam filters. We do not upload, store, or share your complete call history on our servers.
B. SMS and Messaging Data (READ_SMS, SEND_SMS, RECEIVE_SMS, WRITE_SMS)
-
Why we need it: To function as your default SMS handler, allowing you to seamlessly send, receive, and read text messages directly within the CallersHunt interface.
-
How we use it: We only access this permission to provide the user-facing messaging interface. We do not use SMS data for background analytics, account verification scraping, or advertising. This permission is only utilized when CallersHunt is set as your default SMS app.
C. Contact List (READ_CONTACTS, WRITE_CONTACTS)
-
Why we need it: To display the saved names of your friends and family when they call or text you, and to allow you to easily initiate calls and messages to your contacts.
-
How we use it: Contact data is used strictly within the app interface to improve caller identification accuracy. It is not sold or shared with third-party marketers.
D. Phone State (READ_PHONE_STATE)
-
Why we need it: To detect when an incoming call is ringing so the app can trigger the caller identification screen and block known spam numbers before you answer.
3. How We Use Your Information & Spam Protection We use the data accessed via the permissions above exclusively for the following purposes:
-
To enable the core functionalities of dialing, messaging, and caller identification.
-
To accurately filter and block identified spam or telemarketing numbers.
-
To provide an optimized and responsive communication interface.
Spam Number Hashing: We take your privacy seriously. Any phone numbers identified, reported, or processed as spam by our system are one-way hashed. This means the data is cryptographically scrambled. No CallersHunt developer, employee, or third party can view the raw phone numbers associated with spam reports.
4. Third-Party Advertising and Analytics CallersHunt utilizes Google AdMob to display advertisements within the application. AdMob is a third-party service provided by Google that may collect and use data to serve personalized ads.
-
Advertising ID: AdMob may collect your device’s Advertising ID and location data to provide relevant advertisements. You can opt out of personalized advertising by navigating to your device’s Settings > Google > Ads and selecting “Opt out of Ads Personalization” or “Delete advertising ID”.
-
For more information on how Google uses this data, please review the Google Privacy Policy.
5. Prominent Disclosure and User Consent In accordance with Google Play Developer Program Policies, CallersHunt will present a prominent in-app disclosure explaining why we need access to your Call Logs, SMS, and Contacts before prompting you for these permissions. You have the right to deny these permissions; however, doing so will prevent the app from functioning as a default dialer or SMS handler. If you remove CallersHunt as your default handler, the app will immediately stop accessing these restricted permissions.
6. Data Security and Storage We implement reasonable technical and administrative security measures to protect the data processed by CallersHunt.
-
No Server Storage: We do not store your personal communication data, text messages, or call logs on our servers. Your personal communication data remains securely on your local device.
-
While we prioritize the security of your local data, please be aware that no method of electronic storage or transmission over the internet is entirely secure.
7. Your Privacy Choices and Data Deletion You have full control over the permissions granted to CallersHunt.
-
Revoking Access: You can revoke access to SMS, Call Logs, or Contacts at any time by navigating to your device’s Settings > Apps > CallersHunt > Permissions.
-
Data Deletion: Because CallersHunt does not require a user registration account and processes call and SMS data locally on your device, you can instantly delete all app-related data by clearing the app’s cache/storage in your device settings or by uninstalling the application.
-
If you have contacted our support team via email and wish for your email correspondence to be deleted from our records, please send a deletion request to ayotekbiz@gmail.com.
8. Changes to This Privacy Policy We may update this Privacy Policy periodically to reflect changes in our app’s features or legal requirements. We will update the “Effective Date” at the top of this policy when changes occur. We encourage you to review this policy regularly.
9. Contact Us If you have questions, comments, or concerns about this Privacy Policy or how your data is handled, please contact us at:
-
Email: ayotekbiz@gmail.com