Official app website
This website is the official developer website for Mobile Call Rejecter and provides public information, support details, privacy information, and access to app-related resources.
Official developer website
Mobile Call Rejecter helps reduce unwanted calls by allowing you to reject or silence unknown numbers, complete the required setup in minutes, and review recent call activity from a simple interface.
This website is the official developer website for Mobile Call Rejecter and provides public information, support details, privacy information, and access to app-related resources.
The production domain for this website should host the required app-ads.txt file at the
domain root so ad platforms can verify authorized sellers for the app.
Users can learn what the app does, which permissions may be used, how to enable protection, and how to contact support.
Core functionality
The website explains the app clearly for users, stores, and advertising verification while keeping the message simple and trustworthy.
Configure how the app responds to unknown callers. Depending on your settings, calls can be rejected or silenced.
The app provides a Permissions / Setup flow to help users enable the required call screening role and related permissions.
Protection must be enabled by the user. If protection is off, the app will not screen or block unknown calls.
Users can review recent call activity, including the action taken and repeated attempt counts when available.
Some allow-list or matching features may rely on contacts, but only when the user grants that permission.
This site centralizes support contact information, privacy details, usage expectations, and store-facing information.
Quick start
Setup is simple, but the required Android role must be enabled correctly for the app to work as expected.
From the Home screen, open the setup section to begin enabling the required configuration.
Allow Android to use Mobile Call Rejecter as the call screening / caller ID and spam app.
Select the app when Android asks which app should handle call screening behavior.
Complete the confirmation step so the system can apply the app’s screening decisions.
The protection toggle is essential. If it remains off, no rejection or silencing will happen.
Rejected or screened unknown calls can be reviewed later from the call activity screen.
Users who want a straightforward way to reduce interruptions from unknown callers and keep a simple record of screening actions.
Privacy and transparency
Mobile Call Rejecter is designed around call screening functionality. Depending on device capabilities, operating system support, and permissions granted, the app may process only the information needed to make screening decisions and provide local history.
The app may process incoming phone number information or unknown/private caller states, call timing, the action taken, and related metadata required by call screening APIs.
Contacts are only relevant when the user enables features that depend on them, such as matching callers against known contacts.
Preferences such as protection state and unknown-call action, along with local call activity history, may be stored on the device.
If enabled, third-party services such as Google AdMob may process advertising identifiers, device signals, approximate location, ad impressions, or clicks under their own policies.
The app is intended to help screen incoming calls and reduce unwanted interruptions. It does not claim perfect accuracy, does not sell personal data, and lets users control permissions through device settings.
Support
Use the contact details below for support requests, privacy questions, app feedback, or general store and website inquiries related to Mobile Call Rejecter.
Support email
spptmobilecallrejecter@gmail.comFAQ
No. Results can vary depending on Android version, device restrictions, carrier behavior, and available call information.
Yes. Users must complete the Android call screening setup and turn Protection ON inside the app.
Contacts access is only needed for features that rely on contact matching. It is not required for every use case.
The developer website is used to publish the app’s app-ads.txt file at the site root, which
advertising platforms use to verify authorized sellers for the app.
On the production domain root for this website, accessible as /app-ads.txt.