Google Play Google Play Protect policy: fixes and checks

By The Draftbit team · Updated
Sources checked

This guide is for Developers investigating harmful-app warnings or device-level blocking.

A Play Protect warning is different from an ordinary review rejection. Play Protect checks installed apps and can warn users, disable an app, or remove it when it detects potentially harmful behavior.

What to check

Capture the exact warning and identify the installed package, version, and source. Compare it with the artifact submitted to Play. Check whether the finding concerns the app itself, a linked URL, or a privacy alert following removal from the store.

Review dependencies and downloaded content. A device-level finding may appear after installation, so include background and remotely activated behavior in your investigation.

How to address the finding

Investigate and remove the harmful behavior or use the relevant Google appeal path if you believe the detection is mistaken. Provide the artifact identity and a specific explanation of the flagged component.

Don’t ask users to disable Play Protect as a workaround. The Mobile Unwanted Software policy prohibits requesting or rewarding that action. Verify the corrected build and distinguish a fresh result from a warning associated with an older installed version.

Messages this guide can help with

Google Play Protect; Google Play Protect policy violation; Google Play Protect rejection; Google Play Protect 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.

Your next stepSubmit a Google Play release with working review access