Google Play mobile Unwanted Software policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for Apps with deceptive installation, unexpected behavior, intrusive ads, or unsafe data handling.
Google’s Mobile Unwanted Software policy covers software that undermines the experience users agreed to. Examples include hidden functions, misleading security claims, undisclosed collection, and interference with normal device use.
What to check
Follow installation through uninstall. Compare promises with delivered features, inspect bundled software, and check every significant device change. Review ads outside the app and notifications that imitate system warnings.
Check whether your app asks users to disable Play Protect or rewards them for doing so. That is specifically prohibited. Inspect SDKs as well as your own code.
How to address the rejection
Remove unwanted behavior and make legitimate changes explicit and user-controlled. Keep uninstall straightforward. Secure personal data in transit and align collection with the applicable data and permissions policies.
Test the release build while idle and when interacting with ads. Your response should address the specific unwanted action, rather than only listing the app’s useful features. Use the linked child policies when the notice names ad fraud, system imitation, or a hostile downloader.
Messages this guide can help with
Mobile Unwanted Software; Mobile Unwanted Software policy violation; Mobile Unwanted Software rejection; Mobile Unwanted Software 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: Mobile Unwanted Software Checked 22 September 2026