NoRing Privacy Policy

Last updated: July 5, 2026

NoRing runs locally on your Android device. It is designed to help decline repeated unwanted unknown calls without uploading your contacts, call history, or phone numbers.

NoRing's call protection is fully available for free. Free users may see restrained Google Mobile Ads banners on safe foreground screens, and may see an interstitial after opening NoRing from a declined-call notification to confirm a notification action, where ad configuration, Google ad serving, and required consent allow them. An optional NoRing Plus subscription, noring_plus, removes ads while the subscription is active. NoRing does not require an account, cloud spam scoring, or remote call-data processing.

Call history and phone numbers stay on this phone and are not supplied to advertisers.

NoRing uses internet access for optional install verification, purchase verification, Google Play in-app update checks, Google Mobile Ads, Google UMP consent and privacy options, Remote Config, Firebase Analytics, and Firebase Crashlytics. Internet access is not used to upload contacts, call logs, phone numbers, call screening decisions, or local spam learning data.

NoRing may use Google Play's in-app review prompt after the app has protected calls for you. If you choose to submit a rating or written review, that review data is handled by Google Play and may appear on NoRing's Play Store listing according to Google Play's review rules.

Information Used On Device

NoRing uses your call history to learn from repeated unknown calls you rejected or ended quickly and to let you choose recent call numbers for manual spam review. It uses that local learning to decide whether future calls from the same or tightly similar unknown numbers should ring.

NoRing uses your contacts to avoid blocking people you know. Contacts are always allowed unless you explicitly mark a specific number as spam inside the app.

NoRing uses notifications to alert you after NoRing declines a call, so you can quickly allow that number if it was not spam. NoRing can also send low-volume review prompts, activity summaries, and protection-health alerts when the related settings are enabled.

NoRing uses Android's call screening role to filter incoming calls before they ring. This does not replace your regular Phone app. Call filtering decisions are made on your device using your local contacts, local call history learning, and numbers you manually mark.

Information Not Uploaded

Ads And Ad Privacy

Free users may see restrained Google Mobile Ads banners on safe foreground screens. Free users may also see an interstitial after opening NoRing from a declined-call notification to confirm a notification action. Ads are never shown in call screening, notifications themselves, onboarding, setup recovery, purchase flows, diagnostics, or premium direct notification actions.

NoRing does not send contacts, call history, phone numbers, call durations, notification contents, protected-call reasons, local spam decisions, purchase tokens, or integrity data to Google Mobile Ads.

Google Mobile Ads and Google UMP may process documented technical and ad data, such as device and ad identifiers where available, IP-derived network information, consent signals, ad requests, impressions, clicks, diagnostics, and other data described by Google's advertising and consent documentation. Android and Google controls may also apply.

NoRing uses Google's User Messaging Platform to show ad consent forms when they are required for your device or region. NoRing shows an ad privacy options entry in Settings only when Google UMP says that entry point is required. If consent is required and not granted, NoRing remains fully usable and does not request ads for that attempt.

Analytics, Crash Reporting, And Remote Config

Usage analytics and crash reporting are enabled by default to help improve reliability and understand broad app behavior. You can disable either one at any time in Settings.

NoRing collects limited app-usage analytics through Firebase Analytics. NoRing does not attach your name, account, contacts, call history, phone numbers, exact call times, or exact call durations to analytics events.

NoRing analytics use a closed catalog of broad app events and safe categories, such as setup completion, feature-flag fetch status, ad placement category, notification type, review action category, and purchase status category. Analytics never include phone numbers, contacts, call history, exact call timestamps, exact call durations, notification text, purchase tokens, integrity tokens, or ad response identifiers.

NoRing may collect aggregate protection-quality analytics, such as broad call-screening outcomes, safe reason categories, count buckets, and whether a user later confirmed or corrected a protected-call decision. These analytics do not include phone numbers, contacts, call history contents, exact call times, exact call durations, call-log identifiers, pattern identifiers, or local spam-learning profiles.

NoRing uses Firebase Crashlytics for sanitized crash diagnostics. Crash reports do not include call logs, contacts, phone numbers, call decisions, purchase tokens, or integrity tokens.

Firebase Analytics and Crashlytics may process standard app, device, identifier, and diagnostics data needed for those services, including app-instance or installation identifiers documented by Firebase. NoRing disables advertising ID collection for analytics.

NoRing may fetch Firebase Remote Config values for ads, billing UI, upgrade-card visibility, notification UI rollout, update messaging, minimum supported app version, and similar foreground app behavior. Remote Config is not used for critical call-protection decisions such as whether a specific incoming call should ring.

Install And Purchase Verification

When install verification is enabled, NoRing may check whether the app install is an official Google Play copy. The app sends a Play Integrity token to NoRing's install verification endpoint. The endpoint uses Google's Play Integrity API to check app recognition, package identity, certificate identity, freshness, and related trust signals.

NoRing also verifies the optional noring_plus subscription before granting ad removal. Purchase verification sends the Google Play purchase token to NoRing's purchase verification endpoint and Android Publisher so the subscription state can be checked. Purchase tokens are not logged, displayed, or stored as raw tokens by NoRing.

The install and purchase verification endpoints do not receive contacts, call history, phone numbers, call screening decisions, or local learning data.

If enabled install verification fails because the install is unofficial or unrecognized, NoRing may block foreground app access and ask you to install the official app from Google Play. Call screening fails open rather than blocking calls when trust is unavailable.

Google Play Reviews

NoRing can ask Google Play to show an optional in-app review prompt after NoRing has protected repeated unwanted calls. NoRing does not receive your rating or review text through the app and cannot tell whether Google Play showed the prompt or whether you submitted a review.

Ratings and written reviews are submitted to Google Play, not to NoRing's local spam learning system.

Google Play Updates

NoRing may ask Google Play whether a newer app version is available and may show Google Play's in-app update flow or open the NoRing Play Store listing. Google Play may process standard app, device, account, and version metadata needed to decide update availability and install the update. NoRing does not send contacts, call history, phone numbers, call decisions, purchase tokens, or integrity tokens to the update check.

How Call History Is Used

NoRing reads call history on your device to identify repeated unknown calls you rejected or ended very quickly. Those events are used to build local learning profiles so repeat spam calls can be declined before they disturb you.

NoRing also uses outgoing call history locally so numbers you call are treated as safer and are not automatically learned as spam.

NoRing can also show recent call-log numbers inside the Spam List and protected-call review queue so you can choose whether to allow or keep blocking a number. The review queue focuses on recent protected calls, currently up to 14 days old and up to 20 items. A number is not added to the local spam list until you review and confirm it, or until local learning reaches NoRing's on-device threshold.

Call history is not supplied to advertisers, analytics, marketing, cross-user scoring, or sale to third parties.

Local Data Controls And Backup

You can delete local learning data from Settings. This clears learned spam profiles, protected call history, and processed call-log markers stored by NoRing.

NoRing excludes its local database from Android cloud backup and device transfer. Android may back up simple app preferences depending on your device, Google account, and Android backup settings. Since NoRing data stays local, uninstalling the app removes local app data according to Android behavior.

Permissions

Contact

For privacy questions, contact the NoRing developer through the app store listing or support channel where NoRing is distributed.