Developer: Krepel Studio
Effective date: September 3, 2026
InBlacklist: Call Blocker is designed with a simple purpose: to help users block unwanted incoming phone calls while keeping personal call and contact information on the device.
This Privacy Policy explains what information the app accesses, how that information is used, and how it is protected.
InBlacklist may request permission to access the contacts stored on your device.
This access is required for the app's core call-blocking functionality, including:
determining whether an incoming phone number belongs to a saved contact;
allowing saved contacts when “Block unknown callers” is enabled;
allowing users to add contacts to the Blacklist or Whitelist;
correctly applying user-defined call-blocking rules.
Contact information is processed locally on the device.
InBlacklist does not upload, sell, publish, or share your contacts with Krepel Studio or advertising providers.
Android provides InBlacklist with limited information about incoming telephone calls through the official Android CallScreeningService.
The app uses the incoming phone number only to determine whether the call should be:
allowed;
blocked because it is included in the Blacklist;
allowed because it is included in the Whitelist;
blocked because it is from an unknown caller when that option is enabled.
Incoming phone numbers used for call screening are processed locally on the device.
InBlacklist does not upload incoming phone numbers to Krepel Studio servers or use them for advertising purposes.
The app does not require access to the user's complete call history.
Android itself may record blocked calls in the device's system call log according to the operating system's normal behavior.
Phone numbers explicitly added by the user to the Blacklist or Whitelist are stored locally on the device.
These lists are used only to provide the call-blocking functionality requested by the user.
They are not uploaded to Krepel Studio servers and are not shared with advertising providers.
Users can remove individual entries at any time.
Local app data can also be removed by clearing the app's storage or uninstalling the application.
InBlacklist uses Android's official Call Screening role.
The user must explicitly authorize InBlacklist to act as the device's call-screening application.
InBlacklist does not become the default phone application and does not replace the user's existing dialer.
The role is used only to evaluate incoming calls and apply the blocking rules configured by the user.
The free version of InBlacklist may display advertisements provided through Google AdMob / Google Mobile Ads SDK.
Google's advertising services may process information such as:
IP address;
device or advertising identifiers;
interactions with advertisements or the app;
diagnostic and performance information;
information used for advertising, analytics, security, and fraud prevention.
Where required, Google's User Messaging Platform (UMP) is used to request and manage advertising consent.
Contact information, Blacklist entries, Whitelist entries, and incoming caller phone numbers are not provided to Google AdMob for advertising purposes.
Google processes advertising information according to its own privacy policies and applicable consent settings.
InBlacklist may offer an optional Pro purchase through Google Play.
Payments are processed by Google Play Billing.
Krepel Studio does not receive or store the user's payment card number or other complete payment credentials.
Google Play may provide the app with information necessary to determine whether the Pro entitlement has been purchased.
Core call-blocking data is stored locally in the application's private storage on the user's Android device.
Krepel Studio does not operate a server for storing users' contacts, Blacklists, Whitelists, or incoming call information.
Local data remains on the device until:
the user deletes it within the app;
the user clears the app's storage;
or the application is uninstalled.
Information processed independently by Google services is subject to Google's own retention and deletion policies.
InBlacklist minimizes access to personal information and requests only access required for its core functionality.
Sensitive call-screening and contact information is processed locally and is not intentionally transmitted to Krepel Studio.
Application data is stored within Android's application-private storage and protected by Android's application sandbox.
Krepel Studio does not sell users' contacts, phone numbers, Blacklist information, Whitelist information, or call-screening information.
Third-party Google services integrated into the application, including Google AdMob, UMP, and Google Play Billing, may process their own technical, advertising, consent, or transaction-related information as described above.
Users control whether InBlacklist receives access to contacts and whether it holds the Android Call Screening role.
Permissions and roles can be revoked through Android system settings.
Revoking required access may prevent some or all call-blocking functionality from working correctly.
Users can also modify or delete Blacklist and Whitelist entries directly within the application.
InBlacklist does not require users to create an account with Krepel Studio.
There is therefore no server-side InBlacklist account or associated account data to delete.
This Privacy Policy may be updated if the application's functionality, permissions, third-party services, or legal requirements change.
Any updated version will be published on this Privacy Policy page with a revised effective date.
For privacy questions or requests regarding InBlacklist: Call Blocker, users may contact Krepel Studio using the developer contact information provided on the application's official Google Play listing.
InBlacklist is designed around data minimization.
Contacts and incoming phone numbers are used only to make local call-blocking decisions. Blacklist and Whitelist data remain on the device. The app does not upload or sell this information.