AppReviewFix
Guideline library
Google Play — Technical Compliance

Strikes System — Policy strikes and enforcement escalation

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

Google Play tracks policy violations at the developer account level. A single violation is usually a warning or app-level suspension, but repeated or severe violations accumulate as "strikes" that can lead to app removal, feature restrictions, and eventually full developer account termination.

Why apps actually get flagged

Developers are often surprised to learn that violations across unrelated apps under the same account contribute to the same strike count, so a minor issue in an old app can affect a new app's account standing.

A real example

"Your developer account has received a strike due to a policy violation. Additional violations may result in the suspension of your Google Play Developer account, per Google Play's enforcement policy."

The short version, in more detail

Google Play tracks violations at the developer account level. A first violation usually results in a warning or the suspension of one app, but repeated or severe violations accumulate as strikes that can lead to app removal, feature restrictions and eventually termination of the developer account. Many developers are surprised that violations across unrelated apps count toward the same total.

Why this rule exists

Policy only works if there are consequences that increase with repeated behaviour. Account-level tracking prevents developers from treating each app as a separate chance and encourages consistent compliance across a portfolio. It also gives developers a clear picture of where they stand. Because strikes attach to the account, an older app that is no longer maintained can still affect the standing of newer ones.

What this guideline covers

  • Warnings, app suspensions and account-level penalties.
  • How violations accumulate across apps.
  • Escalation from warning to termination.
  • Notifications and the appeal process.

What usually triggers this rejection

  • Violations in an old app that is no longer maintained.
  • Repeated warnings across several apps.
  • A severe violation that skips the warning stage.
  • Ignoring policy notices in Play Console.
  • Operating linked accounts to avoid enforcement.

How reviewers evaluate it

  • Violations are recorded against the developer account.
  • Severity and history affect the action taken.
  • Notices are sent through Play Console and email.
  • Appeals are reviewed separately.

Common misunderstandings

  • Strikes are not limited to a single app.
  • Removing the offending app does not necessarily erase the record.
  • Severe violations can result in immediate action.

Common questions

Does every violation count as a strike?

Not necessarily. Severity and the type of violation affect what happens.

Where do I see notices?

In Play Console and the developer contact email.

Can I appeal?

Yes. Google provides an appeal process for enforcement decisions.

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
1.5 — Developer informationAccount Integrity — Developer account integrityApp Promotion — App promotion and incentivized installsRatings & Reviews — User ratings, reviews, and installsMisrepresentation — Store listing and ratings misrepresentation
AppReviewFix
ProductDecoderPricingGuideline library
CompanyAboutFAQContact
ResourcesGuidesTopic overviewsCommon rejection reasons
LegalTermsPrivacy
© 2026 AppReviewFixBuilt by a developer, not a committee.