Google Play rejection reasons and policy violations: fix table

What does Google Play do when an app breaks a policy?

Google Play picks one of several enforcement actions, and they differ sharply in what you lose. Google says it reviews "app metadata (for example, app title, description), in-app experience, account information (for example, past history of policy violations), any third-party code in apps", using both automated models and human reviewers. Unless the message says otherwise, an action applies in all regions and stays in effect until an appeal is granted.

Action	What happens to the app	Users, statistics, ratings	Developer account standing
Warning	Stays live for the number of days given in the warning email, then is removed if not fixed	Kept if you submit a compliant update	No impact
Rejection	The new app or update is not published; a rejected update leaves the previous version live	Not affected	No impact
Removal	The app and all earlier versions leave Google Play; the listing is hidden; in-app purchases may stop until a compliant version is approved; subscribers' future subscriptions are canceled	Restored once you submit a compliant update	No immediate impact, but "multiple removals may result in a suspension"
Suspension	Removed and hidden; you can no longer use that APK or app bundle	Forfeited	Counts as a strike; multiple strikes can end in termination
Limited visibility	Stays available, but discoverability is restricted; a direct link still works	Not affected	No impact
Limited regions	Downloadable only in some regions; users elsewhere cannot find it	Earlier installs keep working but get no updates	No impact
Restricted developer account	All apps in the catalog are removed; you cannot publish or republish, but you keep Play Console access	Listings and developer profile hidden	Restricted until all violations are fixed
Account termination	All apps removed; related developer accounts are permanently suspended	Listings and developer profile hidden	Ended; any new account you open is terminated too, without a refund of the registration fee

The ladder matters because it escalates. Google writes that suspension "can occur as the result of egregious or multiple policy violations, as well as repeated app rejections or removals." A careless resubmission loop can turn a harmless rejection into a strike. If you are already past rejection, read what to do when your app is suspended.

Why was my app rejected? Read the email, then Policy status

The enforcement email and your Play Console Notifications name the policy. The same information sits on the Policy status page: open Play Console, select the app, and choose Policy status in the left menu. "No issues found" means no enforcement action is active. A rejected app shows that the last published version is still live; a removed app is unavailable until a compliant update; a suspended app has an Appeal button.

Do not stop at the cited policy. Google states that "removal or administrative notices may not indicate each and every policy violation present in your account, app, or broader app catalog." Fixing only the named problem and resubmitting is how many apps collect a second rejection.

Which policy did I break, and how do I fix it?

The table below covers the policies behind most listing and update rejections. Each row links the official policy page; the quotes are Google's own words.

Policy named in the email	Typical cause	Fix
Metadata	Emoji or ALL CAPS in the title, icon or developer name; "#1", "Best", "Free", a discount or "Editor's choice" in text or graphics; anonymous testimonials; keyword lists	Rewrite the title, short and full description and graphics in every language. Details in the metadata policy guide
Spam: Repetitive content	Several apps with near-identical function, content and experience; copied content with nothing added	Merge small, similar apps into one app, or add original content and features
Spam: Webviews and affiliate spam	The app mainly wraps a website you do not own, or exists to drive referral traffic	Get permission from the site owner, or build real app functionality
Spam: Message spam	The app sends SMS, email or other messages for the user without letting them confirm content and recipients	Show the message and the recipients and require the user to confirm
User Data: privacy policy	No privacy policy link in Play Console or inside the app; a PDF, geofenced or broken URL; the policy does not name the app or the developer	Publish a labelled privacy policy on a public web page and link it in both places
User Data: account deletion	Users can create an account but cannot delete it in the app and through a web link; "freezing" offered instead of deletion	Add an in-app deletion path and a web resource, enter its URL in Play Console, delete the associated data
User Data: prominent disclosure	A runtime permission (location, contacts, call log) is requested before an in-app explanation	Show the disclosure screen first, then ask for consent with an explicit tap
Data safety	The form says "no data collected" while an analytics, ads or crash SDK sends data off the device	Re-audit every SDK and update the form. See the Data safety form guide
Target API level	The new app or update targets an API level below the current requirement	Raise `targetSdkVersion`. See the target API level guide
Impersonation	Another company's name, logo or look in the title, icon or developer name	Remove the other brand; never imply an "official" relationship
Deceptive Behavior	Screenshots or descriptions promise features the app does not have	Make every asset show the real app

A few policy sentences explain most of these rows:

Metadata: "Don’t use text or image in the app title, icon, or developer name that indicate store performance or ranking, price or promotional information, or that suggests relations to existing Google Play programs."

Spam: "We don't allow apps that merely provide the same experience as other apps already on Google Play."

User Data: "All apps must post a privacy policy link in the designated field within Play Console, and a privacy policy link or text within the app itself."

Impersonation: "We don’t allow apps that mislead users by impersonating someone else (for example, another developer, company, entity) or another app."

Deceptive Behavior: "Apps must provide an accurate disclosure, description and images/video of their functionality in all parts of the metadata."

Google also reminds developers that "the Metadata policy and our other policies apply to all translations of your Google Play store listing." A clean English listing does not protect a stuffed translation.

How do I resubmit after a policy violation?

Resubmitting is a release procedure, not a button. Google's steps, in order:

Read the policy cited in the enforcement message, and check your Notifications and email.
Check the rest of the app against all Developer Program Policies; further violations can bring additional enforcement.
Fix the app and update every release type, not only production: open, closed and internal testing tracks too.
In Play Console, open the track, select Manage track and Create new release.
If the release that holds the violating bundle is still a draft, discard it. Otherwise add the compliant app bundle.
Make sure the non-compliant version sits under "Not included" in this release.
Enter a release name, select Save, then Review release and roll out to 100%.
Repeat steps 4 to 7 on every track where the non-compliant version was released.

Google warns: "If you fail to deactivate the non-compliant app bundle(s), your attempt to resubmit your app will fail, and live versions of your app bundle(s) may be removed from Google Play."

For a listing-only problem (title, description, graphics), correct the store listing in every language and send the change for review. Do not republish a rejected or removed app before the violation is fixed: Google repeats this rule on every enforcement page, and repeated rejections are one of the listed paths to suspension.

How does the Google Play appeal process work?

Appeal only when you believe the decision is wrong; if the app does break the policy, fixing and resubmitting is faster. The rules:

One appeal per action. "You may submit one appeal per app removal, suspension, or other enforcement action." Put everything into that one appeal.
Where. Follow the instructions in the enforcement email, or use the Appeal button on the Policy status page for a suspended app.
Language. Google may email you in your app's default language, but it states it "can only respond to appeals in Chinese, English, Japanese, and Korean at this time." Write in one of those.
Tone. Abusive or inappropriate messages can make you ineligible for further email support.
Outcome. Google reinstates apps "if an error was made and we find that your app does not violate" the policies and the Developer Distribution Agreement. Developers offering apps in the European Economic Area may have additional recourse options, which Google links from its appeals page.

A useful appeal is short and factual: the app, the action, the policy cited, why the app complies (with the exact screen, setting or text that shows it), and what you changed if anything.

How do I avoid Google Play rejections? A prevention checklist

Title of 30 characters or less, no emoji, no repeated special characters, no ALL CAPS unless it is your brand.
No "#1", "Best", "Top", "New", "Free", "No Ads", discounts or prices in the title, icon, developer name, feature graphic or screenshots.
No anonymous testimonials and no comparisons with other apps in the description.
No keyword lists; write the full description in sentences and do not repeat the short description in it.
No other company's name or logo, and no "official" claims you cannot prove.
Screenshots and video that show the app as it really is.
A labelled privacy policy on a public, non-geofenced web page (not a PDF), linked in Play Console and inside the app, naming the app or the developer shown on the listing.
If users can create accounts: deletion in the app and through a web link entered in Play Console, with the data actually deleted.
An in-app disclosure before every sensitive runtime permission.
A Data safety form that includes every SDK, updated whenever you add or change one.
A target API level that meets the current requirement for your form factor.
Every track checked before a resubmission, and the Policy status page checked after each release.

Is Google Play stricter than the App Store?

The two stores enforce different rulebooks. Google Play relies on written policies with automated and human review and an escalating ladder of actions; Apple works from the App Review Guidelines and a reply-and-resubmit flow in App Store Connect. If you ship on both, read the App Store rejection reasons guide as well.

Where Uptika fits

Uptika does not read your Play Console or resolve policy cases for you. It helps on the part you control before review: the free Metadata Linter flags policy risks in pasted titles and descriptions, such as other brands, "best", "#1" or "free", prices, emoji, ALL CAPS and other platforms' names. On paid plans, Sayfa denetimi (page audit) runs the same rejection-risk check on your live listing next to a 0–100 listing score, and Günlük ping (daily brief) reports rank moves and listing changes each day, so a sudden drop after a release does not go unnoticed. Create an account to try it.

Questions

What are the most common Google Play rejection reasons?

The policies that catch most listings and updates are Metadata (emoji, ALL CAPS, "#1", "free" or prices in the title, icon or graphics, keyword lists), Spam (repetitive apps, webview wrappers of sites you do not own), User Data (missing or broken privacy policy, no account deletion, permissions requested before a prominent disclosure), an inaccurate Data safety form, and a target API level below the current requirement.

Why was my app rejected by Google Play?

The enforcement email and the Policy status page in Play Console name the policy. Google also warns that a notice may not list every violation in your app or catalog, so check the whole app against all policies before you resubmit.

How do I fix a Google Play policy violation?

Read the cited policy, fix the app or listing, upload the compliant bundle to every track that carries the old one (production, open, closed and internal testing), put the non-compliant bundles under "Not included" in a new release, and roll it out to 100%. If old bundles stay active, the resubmission fails.

Does a rejection hurt my developer account?

No. Google states that rejections do not impact the standing of your developer account, and a rejected update leaves the previously published version live. Removals do not immediately affect standing either, but multiple removals may lead to a suspension, and suspensions count as strikes.

How do I appeal a Google Play rejection?

Follow the appeal instructions in the enforcement email, or use the Appeal button on the Policy status page for a suspended app. You get one appeal per enforcement action, and Google answers appeals only in Chinese, English, Japanese and Korean.

Google Play rejections and policy violations: a fix table