Google Play message Spam policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for Apps that send messages, invitations, or referrals on a user's behalf.
A Share button isn’t enough if tapping it immediately sends messages the user hasn’t reviewed. Google requires users to be able to confirm both the content and intended recipients.
What to check
Follow every SMS, email, invitation, referral, and bulk-sharing path. Include contact import, preselected recipients, and background sending after signup.
Check the final confirmation screen. It should make the actual message and destination clear rather than hiding them behind a generic consent statement.
How to address the rejection
Add a deliberate review and confirmation step before sending, or use a suitable user-controlled sharing flow. Remove automatic messages to imported contacts and any SDK-driven unsolicited outreach.
Test cancelling the flow and changing recipients. Confirm that no message is queued before approval. In your response, show the full sequence from initiating the share to reviewing and confirming it; a screenshot of the initial Share button doesn’t prove the required control exists.
Messages this guide can help with
Message Spam; Message Spam policy violation; Message Spam rejection; Message Spam denied
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Google Play: Message Spam Checked 22 September 2026