AppReviewFix
Guideline library
Google Play — Privacy & Security

Device Abuse — Device and network abuse

Official source: Google Play Developer Program PoliciesTopic overview: The review process, app quality and enforcement
What this guideline means

This covers apps that download and execute code outside Play's update mechanism, interfere with other installed apps, or run background processes that drain battery/data without disclosure.

Why apps actually get flagged

Commonly caused by an SDK that fetches remote configuration or ad creative in a way Google's scanners interpret as dynamic code loading.

A real example

"Your app downloads executable code from a source other than Google Play, which violates the Device and Network Abuse policy."

The short version, in more detail

The device and network abuse policy covers apps that download and run code outside Play's update mechanism, interfere with other installed apps or run background activity that drains battery and data without disclosure. It is often triggered by an SDK that fetches configuration or ad creatives in a way Google's scanners read as loading code dynamically.

Why this rule exists

Google Play can only protect users from what it reviews. If an app can fetch and run new code later, it can change its behaviour after approval, which defeats scanning and safety checks. Similarly, apps that interfere with other software or consume resources secretly harm the device as a shared environment. The policy keeps behaviour visible and contained within what was reviewed.

What this guideline covers

  • Downloading and executing code from outside Play.
  • Interference with other apps, services or networks.
  • Hidden background processes.
  • Use of device resources without disclosure.

What usually triggers this rejection

  • An SDK that loads code at runtime.
  • Remote configuration that changes behaviour significantly.
  • Background activity that drains battery or data.
  • Interfering with other apps' operation.
  • Unauthorised use of the device or its network.

How reviewers evaluate it

  • Automated scanners look for dynamic code loading.
  • Reviewers examine background behaviour.
  • Network patterns can signal abuse.
  • SDK behaviour counts as the app's behaviour.

Common misunderstandings

  • Remote configuration is common, but changing executable behaviour is a problem.
  • A false positive from an SDK is still reviewed as a violation.
  • Resource misuse counts even if each action is small.

Common questions

Is downloading content allowed?

Content and assets, yes. Executable code from outside Play is restricted.

How do scanners tell the difference?

They look for patterns such as loading and executing downloaded code.

Does this affect SDK updates?

Yes, because updated SDK behaviour can change the app's compliance.

Platform rules change often. This page is a plain-language explanation written by AppReviewFix, not official guidance. Check the current Google Play Developer Policy Center for the exact wording.

Got this exact rejection?Paste it in and get a diagnosis specific to your app, free.
Decode my rejection
Related guidelines
2.5.1 — Public APIs only2.5.2 — Self-contained apps2.5.3 — Malware transmission2.5.4 — Multitasking background servicesMalware — Malware policy
AppReviewFix
ProductDecoderPricingGuideline library
CompanyAboutFAQContact
ResourcesGuidesTopic overviewsCommon rejection reasons
LegalTermsPrivacy
© 2026 AppReviewFixBuilt by a developer, not a committee.