Google Play Rejections and Suspensions: Causes and Appeals

Google Play rejected or blocked about 1.75 million policy-violating apps in 2025 and banned more than 80,000 developer accounts, so enforcement is a fact of life for Android developers. Unlike Apple, Google escalates quickly from a single app to the whole account, which makes understanding the ladder of actions more important than memorising any one policy.

The numbers behind enforcement

Google's February 2026 safety report says that in 2025 it stopped roughly 1.75 million apps from reaching the store, banned over 80,000 developer accounts, blocked more than 255,000 apps from requesting excessive access to sensitive data, and filtered around 160 million spam ratings and reviews ⁷. The 2024 figures were higher at 2.36 million apps and 158,000 accounts ⁸. Google does not publish a per-policy breakdown, so any ranking of "most common" violations is drawn from developer reports and third-party trackers rather than official data unconfirmed.

Policies most often behind a rejection

Data safety mismatches deserve special attention. Google's User Data policy requires that the declared data practices cover every third-party SDK in the binary, that a privacy policy be linked both on the listing and inside the app, and that apps offering account creation also offer account deletion ⁶. Google checks the declaration against what the APK actually does, so an inaccurate form can trigger enforcement even when the error is accidental ⁶. Permission rules are tightening again: from January 27, 2027, apps that do not need broad contact access must use the Android Contact Picker, and phone-call verification is no longer an accepted reason for READ_CALL_LOG ⁹.

Anonymous and random chat features became subject to the Families and Child Safety rules on August 26, 2026, which caught some social and dating apps that had not updated their content rating or safeguards ⁹.

The enforcement ladder

Google's own help page describes four outcomes, and the differences matter ¹:

• Warning. No effect on account standing, but the email states a number of days before the app is removed if nothing changes.
• Rejection. Applies to an update. The last published version stays live, and a rejection does not count against your account.
• Removal. The live app is taken down until a compliant update is submitted. Users, statistics and ratings are retained when it returns, but active subscriptions are cancelled going forward. A single removal does not affect standing, but several can lead to a suspension.
• Suspension. The app is gone and you lose its users, installs and ratings. Suspensions count as strikes against the account, and they are also issued for egregious or repeated violations and for a pattern of rejections or removals.

Serious categories such as malware, fraud and apps that harm users or devices are treated as egregious and can go straight to suspension without a warning stage ⁵.

Account-level enforcement and repeat offenders

The Developer Program Policy states that repeated or serious violations of the policies or the Developer Distribution Agreement will result in termination of the developer account and any related accounts ⁵. Multiple strikes have the same effect ⁵. Termination removes every app in the catalogue, blocks new publishing, and extends to associated accounts, which Google identifies through shared ownership, administrative access and payment details, among other signals (the full list of association criteria is not published; unverified) ⁵.

Two further points from the policy page are worth internalising. First, an enforcement notice may not list every violation in your account, and Google expects you to audit the rest of your catalogue yourself ⁵. Second, opening a fresh account to route around a termination is itself a violation and typically leads to the new account being closed as well ⁵.

The appeals process

Each removal, suspension or other enforcement action may be appealed once, through the Appeal button on the Policy status page or the "File an appeal" link in the help centre ^1,2. Google reinstates apps only when it concludes it made an error or the app does not actually violate the cited policy, so an appeal is for disagreement, not for promising to fix things later ¹. Appeals are answered in English, Chinese, Japanese and Korean only, and abusive communication can end your access to email support ¹.

Account terminations now carry a deadline. For terminations on or after January 28, 2026, the appeal must be filed within 180 days of the termination email; after that, Google treats the matter as closed ⁴. Earlier terminations had a one-time grace period that expired on July 27, 2026 ⁴. If an appeal is submitted near the end of the window and denied, the developer automatically gets a further 30 days to supply new information ⁴.

How to read a policy email

A Play policy email follows a predictable structure, and the same content appears in the Play Console Inbox and on the Policy status page ². Look for these parts in order:

1. The action. Warning, rejection, removal or suspension, and whether it is at app or account level.
2. Issue found. The named policy and, for listing issues, the specific area such as the title, screenshots or in-app experience; for SDK problems, the version codes and SDK involved.
3. Action required. What Google expects to change, sometimes with a deadline after which the app loses availability in some regions.
4. Appeal link. Present when an appeal is available; absent on ordinary update rejections, which you simply fix and resubmit.

Read the full text of the cited policy before changing anything, because the email paraphrases it and the fix usually lives in a sub-clause ¹. Do not republish a rejected or removed app until the violation is actually resolved; doing so is one of the fastest routes to a suspension ².

Pre-launch report and other prevention tools

The pre-launch report runs automatically when you upload a bundle to a testing track or save a production release, subject to device-lab capacity, and usually returns within an hour ³. A crawler installs the app on a rotating set of phones, tablets, Wear OS and Chromebook devices running Android 9 and later, then exercises it for several minutes, reporting on stability, compatibility, performance and accessibility ³. Supply a dedicated test account in the report settings so the crawler can get past sign-in; it cannot complete purchases, cannot handle WebView-based login, and cannot test launchers, widgets, keyboards or watch faces ³. Upload a deobfuscation file so crash traces are readable ³.

The report is not a policy review, but it catches the crash-on-launch and broken-layout issues that reviewers treat as evidence of an incomplete app. Pair it with three habits: regenerate the Data safety form whenever you add or upgrade an SDK, keep the content rating questionnaire current, and review the policy-deadlines table on Android Developers each quarter so a scheduled change does not land as a surprise rejection ⁹.

How this shows up in the charts

Play enforcement is visible in the rankings if you know what to look for. A removal takes an app out of every Top Free, Top Grossing and category chart immediately, while a rejection leaves it in place but freezes its ability to ship the update that might have moved it. Because removals retain install history, a reinstated app often re-enters the charts within days at close to its previous position, whereas a suspended app returns at zero under a new package name. Google's own counts of 160 million blocked spam reviews and 255,000 apps denied excessive permissions in 2025 ⁷ also suppress chart manipulation, so a listing that climbs implausibly fast and then drops to nothing is more often an enforcement story than a viral one.