Google Play Data Safety Form and Privacy Policy
Who must complete the Data safety form, what to declare and the mistakes that cause problems later.
Read the guide →Google Play App Rejected: Common Reasons and How to Fix Them
Quick answer A Google Play app is rejected when a policy, metadata, content or technical check fails. Read the notice, fix the named issue, upload a corrected release and resubmit, or appeal if you believe it is wrong.
Few messages worry developers more than 'App rejected' in Play Console. The good news is that most rejections can be fixed and resubmitted. This guide explains what the status messages mean, the problems that most often cause them and how to respond.
What the status messages mean
Google explains publishing statuses on its Play Console Help page:
- Update rejected: one or more changes do not comply with Google Play policy or the Developer Distribution Agreement.
- App rejected: the same, but only for a draft app being published for the first time.
- Removed by Google: the app is removed indefinitely and needs a policy-compliant update to be reinstated.
- Suspended by Google: the app is removed indefinitely and needs a successful appeal.
Why do Google Play apps get rejected?
The rejection email names the policy that was broken, so always start there. These are the areas that most often cause trouble, based on what Google asks developers to prepare before submitting:
- Privacy policy or Data safety problems. A privacy policy and an accurate Data safety section are required. See our guide to the Data safety form.
- Reviewers cannot get into the app. Google asks you to provide an active demo account, login details and other review resources if your app needs them.
- Inaccurate app information or metadata. The listing should describe what the app really does.
- Account or app type issues. For example, some app types need an organization account. See our account verification guide.
- Errors in the release review. If the summary shows errors, you cannot publish until they are fixed.
How do you fix a rejected app and resubmit?
- Read the notice in fullFind the policy named and the part of your app or listing it points to.
- Fix the causeUpdate the app, listing, privacy policy or declarations so they match the policy.
- Check your release summaryResolve every error. Address warnings where you can.
- Send the changes for reviewChanges are not always sent automatically. Check the Publishing overview page for changes not yet sent for review.
- Wait for the resultGoogle says some developer accounts receive a more thorough review, which may take up to seven days or longer in exceptional cases.
When to appeal
If you believe the decision was wrong, Google allows you to submit an appeal instead of resubmitting. Explain clearly why your app complies, and attach any details that help the reviewer. A suspended app needs a successful appeal to come back.
Rejected app vs rejected production access
An app rejection is about policy. A production access rejection is about the closed test. If you got the second one, read what to do when production access is rejected. If you are new to the whole process, start with how to publish an app on Google Play for the first time.
How to avoid a rejection before you submit
- Read the policy summariesCheck that your app, ads, permissions and listing follow Google Play policy.
- Complete the app content forms accuratelyThis includes the Data safety form and privacy policy.
- Give reviewers accessProvide a working demo account and any other review details they need.
- Test the release buildInstall the exact build you are submitting on a real device.
- Check the review summaryFix errors and look over warnings before you click Release.
Still waiting on your closed test? Read the closed testing requirements checklist so you know exactly what Google needs.
Part of a series: this article is one chapter of Google Play Closed Testing: The Complete Guide. Start there for the full roadmap from setup to production.
A pre-submit checklist that prevents most rejections
| Area | Check |
|---|---|
| Metadata | Title, description and screenshots are accurate and do not mislead |
| Privacy | Privacy policy URL works and matches the Data safety form. See the guide |
| Content | Your content rating answers are honest |
| Access | If login is required, give reviewers test credentials |
| Technical | No crashes on launch, target API level is current |
| Account | Verification complete. See the verification guide |
When a rejection is part of a bigger problem
A single rejected release is usually fixable. Repeated or serious violations can lead to account action. If you receive an account-level notice, read the account termination guide right away. If it is only a production access decision, see production access rejected.
Frequently asked questions
What does 'App rejected' mean in Play Console?
Google says App rejected and Update rejected mean one or more changes do not comply with Google Play policy or the Developer Distribution Agreement. App rejected applies only to draft apps being published for the first time.
Can I appeal a rejection?
Yes. Google says you can fix the issue and resubmit, or submit an appeal.
What is the difference between removed and suspended?
Removed by Google means the app is removed indefinitely and needs a policy-compliant update to be reinstated. Suspended by Google means it is removed indefinitely and needs a successful appeal.
Is a rejected app the same as rejected production access?
No. Production access is about your closed test. An app rejection is about policy compliance of the app or its listing. Read the notice to see which one it is.
