How NoRing decides what rings and what stays quiet.

Manual choices come first. A number you allow stays allowed, and a number you explicitly mark as spam can be declined. Saved contacts and numbers you called are safe by default. Eligible recent repeat patterns can be declined before the ring. When those conditions do not support a block, NoRing allows the call.

• NoRing does not depend on a global caller-ID or remote spam database.
• Protected history and alerts give you a correction path after a declined call.
• Local pattern evidence ages out rather than becoming a permanent global reputation.

An explicit conversation or sender rule is the strongest user instruction. Without a rule, suspicious content receives the highest automatic caution. Contacts and active human conversations are protected, important categories stay in Inbox, and configured marketing or unrecognized business categories can stay in Quieted.

• Important categories include security codes, transactions, bills, deliveries, travel, appointments, health, and school messages.
• Marketing categories include shopping promotions, loan or credit-card offers, insurance or investment offers, and other marketing.
• When the classifier is uncertain, the message stays available in Inbox.

Contacts, call logs, phone numbers, SMS/MMS content, sender IDs, message metadata, local decisions, rules, protected history, and learning profiles stay on the Android device. NoRing does not send them to a cloud or cross-user scoring service.

NoRing cannot honestly promise perfect spam detection. It does not identify every unknown caller, and SMS Protection cannot operate unless NoRing is the default SMS app. NoRing supports SMS and MMS, not RCS. These limits are part of the product fit, not fine print.

This page describes the current NoRing product rules rather than generic spam-blocker advice. It is reviewed when protection behavior or Android role requirements change.