Google Play Policies

Overview

Understanding Google Play policies before submission helps avoid rejection and account suspension. Violations can lead to app removal or permanent developer account termination.

Content Policy

  • No deceptive behavior, malware, or inappropriate content allowed
  • Apps must not facilitate illegal activities of any kind
  • Intellectual property rights must be respected — no trademark or copyright infringement
  • User-generated content requires moderation mechanisms and reporting tools

Privacy & Data

  • Privacy policy URL required for all apps collecting any user data
  • Data Safety section must be accurate and complete — review all third-party SDKs
  • Sensitive permissions (location, camera, contacts) require clear justification
  • Data collection must have clear user consent and lawful basis
  • Comply with GDPR, COPPA, CCPA as applicable to your target markets

Monetization

  • In-app purchases for digital goods must use the Google Play billing system
  • Subscription terms, pricing, and billing cycles must be clearly disclosed to users
  • Refund policies must comply with local consumer protection laws
  • No misleading "free" claims if core features require payment or subscription

Technical Quality

  • App must be stable — no excessive crashes or ANRs above threshold (0.47% ANR rate)
  • 64-bit support is required for all native libraries since August 2019
  • Apps must function correctly on all declared device types and form factors
  • Performance must be tested across a representative range of Android devices

Ads Policy

  • Ads must not interfere with app functionality or user experience
  • Ad content must comply with Google Ads policies (no deceptive or inappropriate ads)
  • Disruptive ad formats (unexpected interstitials, ads on lock screen) are prohibited

Account & Identity

  • Developer identity verification is required before publishing
  • Account details must be accurate and kept up to date
  • Multiple accounts for the same entity may be suspended under policy circumvention rules
  • Developer name displayed publicly must match verified identity