Google Play rooting policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for Apps containing code that roots Android devices.
Google distinguishes rooting that users knowingly request from malicious rooting. Disclosure alone isn’t enough if the app also performs other potentially harmful actions.
What to check
Identify every rooting component, exploit, downloaded binary, and SDK that can elevate privileges. Confirm when it runs and what the user sees beforehand. Inspect the actions performed after root access is obtained.
A library described as a compatibility helper may still include rooting behavior. Review the shipped binary and dependencies instead of relying only on package names.
How to address the rejection
Remove undisclosed rooting and any harmful follow-on behavior. Prefer supported Android capabilities for the actual feature your app needs.
If you believe a classification is wrong, explain the specific rooting flow, advance disclosure, user action, and absence of the harmful behavior named in the notice. Google’s distinction between malicious and non-malicious rooting isn’t a promise that every disclosed rooting app meets all other Play policies. Check device abuse and elevated privilege rules too.
Messages this guide can help with
Rooting; Rooting policy violation; Rooting rejection; Rooting 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: Rooting Checked 22 September 2026