SMSniper Privacy Policy

Last updated: October 6, 2026

SMSniper is provided by Statweer. This policy explains how SMSniper handles filter rules, messages, purchases, and support requests. Contact us at [email protected] with questions about privacy.

Your filter rules and messages

When you enable SMSniper in iPhone settings, Apple's message filtering framework provides the sender and text of eligible messages to the SMS filter extension. iOS controls which messages are eligible. SMSniper does not have access to your entire Messages history.

The rules you create — words, phrases, senders, and regular expressions — are stored on your device, in a container shared between the app and its SMS filter extension. SMSniper does not upload your rules to our classification service. If you choose to export or share rules, the exported file goes to the destination you select.

Your rules are checked on your iPhone first. A message matching a rule receives that rule's decision and is not sent to Cloud AI Filtering. SMSniper does not maintain a copy of your SMS inbox or a server-side message history.

Cloud AI Filtering: optional and off by default

Cloud AI Filtering requires a Pro AI purchase and your explicit consent. Purchasing Pro AI alone does not enable it. You can turn it off in the app at any time.

What is sent. For eligible messages that none of your local rules match, the sender and message text are sent over an encrypted connection to our classification service at smsniper.statweer.com. In the app's test screen, choosing a cloud-enabled test can send the sender and text you enter through the same service after the local rules are checked.
Where processing happens. Our service uses Cloudflare Workers and Workers AI on Cloudflare's global network. Processing may occur outside your country; we do not promise processing in a particular country or region. Cloudflare processes the information to provide this service.
Why it is sent. To return a message category and, when available, a subcategory, which iOS uses for message filtering. Automatic classification can make mistakes.
Message retention. Our classification code does not store sender information or message text in a database, application logs, or a message cache. Classification requests bypass AI Gateway caching. Our classification requests explicitly disable AI Gateway content logging. We do not use messages to train models. Cloudflare's Workers AI data terms explain its handling of model inputs and outputs: Cloudflare Workers AI data usage.
Operational records. Our service logs a random request identifier, app version when supplied, outcome and failure reason, returned category and subcategory, model and deployment identifiers, token counts, inference attempt count, and processing time. These records exclude message text and sender information and are retained according to our Cloudflare logging configuration. Network providers necessarily process connection information, such as IP addresses, to deliver and protect the service.
Failure behavior. If Cloud AI cannot return a valid classification — including transport errors, timeouts, service limits, or unavailable service — SMSniper returns no filtering decision. iOS then handles the message according to its normal behavior.
Your control. Turning Cloud AI Filtering off prevents new cloud classification requests. It does not undo requests already in progress. You can use local rules without enabling Cloud AI Filtering.

The SMS filter extension uses Apple's IdentityLookup network deferral. It does not use a separate direct network connection. The app's optional test screen uses an encrypted network connection directly.

Purchases and subscriptions

Apple processes in-app payments. SMSniper uses RevenueCat to verify purchases, restore purchases, and determine whether Pro or Pro AI features are available.

RevenueCat processes purchase and subscription records together with a generated anonymous app user identifier. This identifier lets RevenueCat associate purchase records with the app installation; it is not your name or email address. SMSniper does not require an account and does not provide RevenueCat with your SMS messages or local filter rules. We do not receive your payment card details.

Purchase records may be retained separately from message processing so that purchased features and restores continue to work. RevenueCat also provides purchase reporting. See RevenueCat's privacy policy and Apple's privacy policy for their practices. Subscription renewal and cancellation are managed through your Apple account.

Support and privacy requests

If you email us, we receive the email address and the information you include, and use them to respond and resolve your request. Do not include sensitive message content unless necessary for the help you request. We retain support correspondence as needed to handle your request and meet applicable obligations.

You can delete rules in the app and disable SMSniper in iPhone settings. Removing the app removes its local app data according to iOS behavior; this does not cancel an active subscription. For questions about access to or deletion of information held by us or our purchase service, contact [email protected]. Some purchase records may need to be retained for transaction, fraud prevention, or legal requirements.

Updates

We may update this policy when the app or our service changes. The date above identifies the latest revision. If a change requires additional consent for Cloud AI Filtering, the app will ask for that consent before enabling the changed processing.