Google Play Rejections and Policy Violations: A Fix-It Guide

Google Play's review is largely automated at first, which makes its messages feel terse. The policy name in the email or Play Console notice is the key: it tells you which part of your app, listing or declarations triggered the decision. This guide sorts the most common issues by where the fix lives, so you can go straight to the right place.

First, understand what kind of action you received

The Policy status page in Play Console lists open issues per app, including deadlines. Check it whenever you receive an email, because one email can hide several issues.

Fixes that live in Play Console declarations

Data safety form doesn't match the app

Google compares your declarations with what the app and its SDKs actually do. Typical gaps: an analytics or crash SDK collecting device identifiers, an ad SDK, or user content sent to an API. Update the form to reflect all data types, purposes and whether data is shared. Our guide to privacy labels and the data safety form walks through each section.

Privacy policy missing or unreachable

The policy URL must be active, publicly accessible, not a PDF behind a login, and it must cover the app. It also needs to be reachable inside the app.

Account deletion requirement

If users can create accounts, Google requires an in-app way to request account deletion and a web link where users can request deletion without reinstalling the app. Add the link in the data safety section.

Sensitive permission declarations

Some permissions require a declaration form explaining why your app's core functionality needs them, and sometimes a video. Common examples are background location, SMS and call log, QUERY_ALL_PACKAGES, and broad photo and video access. Since 2024, Google has limited broad photo and video permissions to apps whose core purpose needs them; others should use the system photo picker. The fastest fix is often to remove the permission and use a less invasive API.

Fixes that live in the build

• Target API level too old. Google requires new apps and updates to target a recent Android API level, roughly within a year of the latest major release. Update targetSdkVersion, then test behavior changes such as notification permissions and foreground service types.
• Undeclared foreground service types. Apps targeting newer Android versions must declare foreground service types and may need to justify them in Play Console.
• Crashes or broken functionality. Pre-launch reports in Play Console show crashes on test devices. Fix them before resubmitting.
• Minimum functionality and WebView spam. Apps that offer very little, or that mainly display a website the developer does not own or have permission to use, can be rejected under the spam policy. Publish only properties you control, and add genuine app features.
• Ads behaving badly. Full-screen ads that appear unexpectedly or block normal use violate the ads policy. Review your ad placements and SDK settings.

Fixes that live in the store listing

• Misleading or keyword-stuffed metadata. Avoid repeated keywords, ranking claims ("#1 app"), emojis or excessive capitals in the title, and names of other apps or brands.
• Screenshots that misrepresent the app. Show the real UI. Marketing frames are fine; features that do not exist are not.
• Impersonation or intellectual property. Using another brand's name or logo without authorization leads to removal. If you publish for a client, publish in the client's account or have written permission.
• Wrong content rating or target audience. If children are in your target audience, the Families policy applies with additional requirements for ads and data.

How to fix, resubmit and appeal

1. Identify the exact policy named in the notice and open the corresponding page in the Policy Center.
2. Find every instance of the issue, not just the one in the example. Automated checks often run again on the next submission.
3. Fix the build, the declaration or the listing, then upload a new version or update the listing.
4. Resubmit for review and watch the Policy status page.
5. Appeal if you disagree. Notices include an appeal option. Explain clearly and factually why the app complies, with references to the policy text. Do not appeal and resubmit unchanged versions repeatedly; repeated violations can escalate to suspension.

Keep it from happening again

Many Play issues appear with no change on your side, because policies and API requirements evolve. Assign someone to read Google's policy update emails, review the data safety form whenever you add an SDK, and plan one maintenance release per year for the target API level. New personal accounts face an extra gate before the first production release, the closed test explained in the 12-tester rule. If you also ship to iOS, compare with the most common App Store rejection reasons, since the two stores flag different things.

If a rejection blocks your release and you want experienced help, appsubmitter.io guides you through Play policy issues and resubmissions in your own developer account, and can set up a CI/CD pipeline so builds and declarations stay consistent.