NoRing

NoRing Privacy Policy

Last updated:

NoRing is a local-first Android communication-protection app with independently usable Call Protection and SMS Protection. It helps unwanted calls and spam or marketing SMS/MMS stay quiet while important communication gets through.

SMS Protection works only while NoRing is your default SMS app. This release supports SMS and MMS, not RCS. NoRing does not require an account or use cloud or cross-user communication scoring.

NoRing's protection is fully available for free. Free users may see restrained Google Mobile Ads native ads on approved Home and Calls foreground surfaces where ad configuration, Google ad serving, and required consent allow them. An optional NoRing Plus support subscription, noring_plus, funds continued development and removes ads while the subscription is active. It does not unlock or strengthen protection.

NoRing's local copies of contacts, call history, phone numbers, SMS/MMS content, sender information, message metadata, and protection data are processed on this phone and are not supplied to NoRing servers or 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. Those services do not receive communication content, contacts, call logs, phone numbers, call screening decisions, message identifiers, or local protection data from NoRing.

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 call management. It uses confirmed local feedback and on-device 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 block a specific number inside the app.

NoRing uses notifications for important Inbox messages, declined-call correction, low-volume call-feedback or protection summaries, message problems, and protection-health alerts when the related permission and settings allow. Messages placed in Quieted do not create normal SMS notifications or inflate Inbox unread or launcher-badge counts.

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.

SMS Protection And The Default SMS Role

When NoRing is the default SMS app, it receives, writes, displays, organizes, searches, and sends SMS/MMS. It can import existing message history, build local Inbox and Quieted views, maintain threads and drafts, handle send or download retries, and apply local Sender Rules and protection decisions.

NoRing supports SMS and MMS in this release. It does not support or protect RCS conversations.

SMS/MMS bodies, attachments or local attachment references, sender IDs, recipients, participants, timestamps, provider identifiers, search queries, drafts, rules, classifications, and protection decisions are processed on the device. NoRing does not upload them for protection, analytics, advertising, marketing, or cross-user scoring.

Messaging necessarily involves third-party delivery: when you send a message, Android and your mobile carrier transmit its content and addressing information to the intended recipient; incoming SMS/MMS is delivered or downloaded through the carrier. Carrier, recipient, and Android messaging practices are separate from NoRing's local protection and developer-operated services.

If NoRing is no longer the default SMS app, it stops claiming that SMS Protection, message receive, message write, or message send is operational. Locally indexed history may remain until you delete it or uninstall the app.

Information Not Uploaded To NoRing Services, Ads, Or Diagnostics

Ads And Ad Privacy

Free users may see restrained Google Mobile Ads native ads on approved Home and Calls foreground screens. Ads are never shown in Messages, call screening, notifications, onboarding, setup recovery, purchase flows, diagnostics, or notification actions.

NoRing does not send contacts, call history, phone numbers, call durations, SMS/MMS content or metadata, sender or recipient identifiers, notification contents, local protection 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 off until you choose whether to enable them in Settings. You can change either choice at any time.

When analytics is enabled, NoRing uses Firebase Analytics for limited app-usage measurement. NoRing-authored events use a closed catalog of broad app events and safe categories, such as setup completion, feature-flag fetch status, ad placement category, notification type, protected-call feedback source, and purchase status category. NoRing does not attach your name, account, communication content or identifiers, exact communication times, notification text, purchase tokens, integrity tokens, or ad response identifiers to those events.

The Firebase Analytics SDK can also collect its own standard app lifecycle, session, device, app-instance identifier, coarse IP-derived location, and performance-related events while analytics is enabled. Those SDK-defined events do not pass through NoRing's custom-event validator. NoRing disables advertising ID collection for analytics and does not supply communication content or communication identifiers to Firebase Analytics.

NoRing's Firebase Android app is linked to Google AdMob. Google states that, while this link remains active, Analytics data collected after you enable usage analytics can be available to AdMob for user metrics and monetisation reporting even when NoRing's Remote Config ad switch is off. This does not make communication content or communication identifiers available to AdMob because NoRing does not send them to Analytics.

NoRing keeps coarse protection-quality counters, such as broad call-screening outcomes and count buckets, only on the device with local retention maintenance. The current app does not export those local protection counters to Firebase Analytics.

When crash reporting is enabled, Firebase Crashlytics can collect SDK-generated fatal crash and ANR reports as well as sanitized non-fatal reports submitted by NoRing. NoRing validates its own non-fatal reports and does not add contacts, call logs, phone numbers, message content or identifiers, local protection decisions, purchase tokens, or integrity tokens as crash keys or logs. SDK-generated reports can include technical stack traces, exception messages, device and app metadata, and other diagnostics documented by Firebase; those automatic reports do not pass through NoRing's non-fatal validator.

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. Turning crash reporting off also deletes unsent Crashlytics reports held by NoRing on the device.

NoRing may fetch Firebase Remote Config values for ads, notification UI rollout, update messaging, minimum supported app version, and similar foreground app behavior. Firebase Remote Config and Firebase Installations process a Firebase installation identifier plus standard request properties such as country, language, time zone, operating-system or platform metadata, app identifier, and app version to deliver those values. The single ads-enabled value controls both approved ad placements. Remote Config is not used for critical call- or message-protection decisions such as whether a specific incoming call should ring or an SMS/MMS should remain in Inbox.

Firebase states that it retains a Firebase installation identifier until the developer requests its deletion through the Firebase Installations API. After that request, associated data can take up to 180 days to be removed from live and backup systems. NoRing does not currently expose a user-facing cloud-data deletion control.

Website Performance Measurement

The public noringapp.com website uses Cloudflare Web Analytics to measure broad traffic and page-load performance. Cloudflare supplies the performance beacon and states that it does not track individual visitors across customer websites. This website measurement is separate from the Android app and does not receive contacts, call logs, phone numbers, SMS/MMS content or identifiers, call or message decisions, local learning data, purchase tokens, or integrity tokens.

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, SMS/MMS content or identifiers, local protection 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, and install verification does not gate the default-SMS receive or send path.

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 call-protection learning.

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 logs, phone numbers, SMS/MMS content or identifiers, local protection 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 support local feedback and learning so repeat unwanted 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 unwanted.

NoRing can show recent call-log numbers under Calls > Manage > Pick from recent calls so you can block or allow a number. Calls > Protected history shows recent calls NoRing kept quiet and offers corrections such as Allow future. Blocked & Allowed numbers contains the manual dispositions you choose; separate on-device learning can identify repeat unknown-call patterns under NoRing's local thresholds.

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

Local Data Controls And Backup

You can separately delete local Call Protection data, the local SMS Protection index/classifications/rules, or all local protection data from Settings. Deleting NoRing's SMS Protection index does not silently delete messages from Android's SMS/MMS provider. While NoRing is your default SMS app, you can separately select one or more messages or conversations and confirm permanent deletion; that removes the selected SMS/MMS from Android's provider and cannot be undone.

NoRing excludes its local database, message drafts, retry payloads, and other communication-protection state from Android cloud backup and device transfer. Android may back up simple app preferences depending on your device, Google account, and Android backup settings. Uninstalling the app removes NoRing's 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.

Back to top