Google Play app rejected for a policy violation: fix or appeal

If Google Play rejected your app for a policy violation, I'd usually fix it: read the policy named in the enforcement message, update the app, and resubmit on every track, deactivating the non-compliant bundles. I'd appeal only if you've read the policy and believe Google got it wrong. You get one appeal per enforcement action, through the link in the enforcement email or Play Console Help.

As of November 6, 2026, this comes from Google's Play Console Help pages, mainly My app has been removed from Google Play. All four pages are listed at the end.

Rejected, removed, suspended or warned?

Open Play Console, select the app, and choose Policy status in the left menu. It shows any active enforcement against the app and what action Google took. The difference matters, because only some of them count against your account.

Status	What happens to the app	Effect on your developer account
Rejected	The update isn't published. The last version you published successfully stays on Google Play.	Doesn't affect your account's standing.
Removed	Not available on Google Play until you submit a compliant update.	Doesn't immediately affect standing, but multiple removals may lead to a suspension.
Suspended	No longer available on Google Play.	Counts as a strike against your account's good standing.
Warning	Stays up for now, but is removed after the number of days in the warning email.	Doesn't affect standing. If the app is suspended after a warning, an appeal is required.

For a suspension, the Policy status page has an Appeal option. Google also says not to republish a rejected or removed app until the violation is fixed.

How do I fix and resubmit?

Google's removal page lists these steps. The one that trips people up is that the fix has to reach every track, not only production.

1. Read the policy named in the enforcement message, and check your Notifications in Play Console and your email.
2. Make the changes, and update all release types, not just your production release.
3. Upload the compliant app bundle to every track and deactivate the non-compliant bundles. Google says that if you don't, your resubmission will fail and live versions may be removed.
4. For each track, open Manage track, then Create new release. Add the compliant bundle, and make sure the non-compliant version is under Not included.
5. Enter a release name, click Save, then Review release, and roll it out to 100%.
6. Repeat for every track that still has a non-compliant version, including testing tracks.

That last step is easy to miss if you've been testing on a closed track. An old build sitting there is still a non-compliant bundle.

When should I appeal instead?

Google's appeals page says it will reinstate apps if an error was made and the app doesn't violate the Google Play Program Policies and the Developer Distribution Agreement. So an appeal fits when you've read the policy carefully and believe the decision was wrong. If you agree the app breaks the policy, fixing and resubmitting is the route the help pages describe.

Rule	What Google's help pages say
How many	One appeal per app removal, suspension or other enforcement action.
Where	Follow the instructions in the enforcement email, or use the appeal link on Google's Managing Policy Violations and Appeals page.
Language	Appeals are answered only in Chinese, English, Japanese and Korean at this time.
Misuse	Misusing the appeal process can make you ineligible for further email support.

The one-appeal limit, the languages and the misuse note come from Google's removal page, not the appeals page. Since you get one appeal per action, I'd write it once, carefully: name the policy from the email, say which part you believe the app meets, and point to where in the app a reviewer can see it.

What if my whole account was terminated?

That's a separate case with a deadline. For account terminations on or after January 28, 2026, Google says you have 180 days from the date your account was terminated to appeal. After that, Google considers the matter closed. If you appeal near the end of the window, Google says and the appeal is denied, you automatically get an extra 30 days after that decision to reply with new information for a re-review. For terminations before January 28, 2026, the one-time grace period ran until July 27, 2026.

What I'd do

Start in Policy status, not the email alone, so you know whether it's a rejection, removal, suspension or warning. If it's a rejection or removal and you can see what the policy is pointing at, fix it, then go through every track and deactivate the old bundles before you roll out. Save the appeal for a decision you're sure is wrong, and write it once with the policy name and where to look in the app.