Google Play device and Network Abuse policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for Apps that interact with devices, networks, other apps, or downloaded code.
A Device and Network Abuse rejection can come from your own code or a library. Google prohibits unauthorized interference with devices and services, unsafe code, and updates that bypass Play’s update mechanism.
What to check
Inspect update loaders, WebViews, proxy features, background services, and SDKs. Downloading native executable code from your server is different from downloading an image or other ordinary content. The exception for interpreted code doesn’t exempt that code from Play policies.
Check whether WebViews expose a JavaScript interface to untrusted content. Review API access against the service’s terms, and confirm that your app respects Android’s power management and sandbox protections.
How to address the rejection
Remove the offending loader, unauthorized access, or interference. Deliver executable app updates through Google Play. Restrict privileged WebView bridges to content you can trust and validate incoming URLs.
Test the release build with remote configuration enabled. Record the affected dependency version, what changed, and which feature now runs through an allowed mechanism. Updating the listing alone won’t fix behavior inside an SDK.
Messages this guide can help with
Device and Network Abuse; Device and Network Abuse policy violation; Device and Network Abuse rejection; Device and Network Abuse 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: Device and Network Abuse Checked 22 September 2026