Blocks submissionGoogle Play

The app never sends a message on the user's behalf without showing content and recipients first

The question Does the app send SMS, email or other messages for the user (a share, an invite, an alert)? If so, does the user see the content and the recipients and confirm before it goes? Name the flow.

A person or a model answers it from the app's texts and screens; the answer is kept only while the facts it saw are unchanged.

Applies when permission:android.permission.SEND_SMS; listing:\b(invite|share|send (a )?message|sms)

Checked from built, not yet uploaded, on a test track, submitted and in review, published

The rule, in our words

• Spam: No sending messages on the user's behalf without letting them confirm content and recipients; no apps whose main purpose is affiliate traffic or a web view of someone else's site without permission; no repetitive apps that merely copy what exists or split one small experience into many apps.

Okkok never stores the stores' text. Each item above is our paraphrase, and the link is the page it rests on, verified unchanged by fingerprint on every run.

The other store

• none on principle. same
• none; Apple names refused categories (flashlights, timers, fortune telling); Google adds the messaging-on-behalf rule. same
• none; Apple explicitly bans a Select All control. same

Check your app

pip install git+https://github.com/petresandu-cloud/okkok
okkok audit path/to/app

The report names this rule as google.no-messages-without-confirmation and says what to do, who does it, where, and how it knows.