Back to all posts
Google Play7 min read·October 25, 2026

Common Reasons Google Play Rejects an App and How to Avoid Them

TB
ThynkBlox Apps Team
App Engineering

If your Google Play app was rejected, start with the reason in the review notice and compare it with the app you submitted. Check permissions and sensitive data, the Data safety form, your privacy policy, target API level, store listing, broken features and account deletion. Fix the mismatch, test the submitted version and use the Play Console policy center to confirm the current requirements before resubmitting.

What should you do first after a rejection?

Read the complete notice before changing anything. Identify the policy named, the behaviour described and the part of the app involved. Separate what the notice actually says from what you suspect caused it.

Then collect the material needed to investigate:

  • The app version submitted for review.
  • Its store listing and screenshots.
  • Its permissions and data disclosures.
  • The privacy policy available to users.
  • The sign-in instructions supplied for review.

Write the problem in one sentence: “The app does this, but our disclosure says that.” If you cannot explain the mismatch yet, investigate further before rebuilding.

Use our Google Play release checklist to organise the wider submission checks. For the rejection itself, keep the policy named in the notice at the centre of the work.

Why can permissions and sensitive data cause problems?

Treat each permission as a product decision. List the feature that needs it, when the app requests it and what happens if the user refuses. Remove permissions that no longer support a feature in the submitted app.

Pay particular attention to access involving sensitive information. A permission being available technically does not establish that your intended use meets the applicable policy.

Google Play's sensitive permissions policy says requests must be necessary for the app's core functionality. Where data use may not be expected, the User Data policy also requires an in-app disclosure and affirmative consent before the data is accessed.

For an illustrative example, consider an app that lets users attach a photo to a support request. Ask whether the feature needs broad access to the photo library or whether the user can select the specific image to share. Choose the narrowest access that supports the feature and meets the current rules.

Also inspect added libraries and services. Your review should cover what the complete app does, including behaviour introduced by components your team did not write.

Why might the Data safety form disagree with the app?

The Data safety form needs careful comparison with actual data handling. Do not complete it from a feature list alone.

Google's Data safety guidance says the form must reflect collection and sharing carried out by third-party code in the app, not only your own.

Create a simple inventory of information leaving the device. For each item, record its destination, purpose and the component sending it. Include sign-in, support, analytics and crash reporting wherever they are present.

Review areaQuestion to resolve
Account informationWhat details leave the device when someone signs up?
DiagnosticsWhat information accompanies an error report?
AnalyticsWhich actions and identifiers are recorded?
Third-party servicesWhat does each connected component receive?
Optional featuresDoes declining the feature stop the related data flow?
DeletionWhat happens to stored information after a deletion request?

Use the current form instructions to classify these activities. Everyday meanings of words such as “sharing” may differ from the definitions used in the form.

What makes a privacy policy useful for review?

A useful privacy policy describes the app people can actually install. Compare it with the data inventory, account settings and support process.

The User Data policy requires a privacy policy link in Play Console and a link or text inside the app.

Avoid copying a policy from another product. It may describe information you never collect, omit a service you use or promise deletion that your system does not perform.

Check practical access as well as wording. Open the policy from the store listing and from within the app. Confirm that the page loads and that the contact details work.

Review broad promises carefully. If the policy says information is never shared, establish whether that statement accurately describes every service receiving it. Align the policy, the Data safety answers and the app's behaviour before submission.

How can the target API level affect submission?

The target API level is a technical release requirement to verify for the particular submission you are making. Keep the current requirement in the release checklist rather than relying on a remembered value.

Google sets one requirement for new apps and updates and another for existing apps to stay available to new users on newer devices. Check the current target API level requirement for each release.

Ask your developer to confirm the target API level in the actual release package. Then test that package after any required change.

Treat the update as more than an edit to a setting. Recheck the behaviours relevant to your app, such as permission requests, notifications, file access and background activity. Resolve any compatibility work before submitting again.

When does store metadata become misleading?

Review the title, description, icon and screenshots against the submitted app. A reader should be able to understand what they will receive without guessing which features are available.

Google Play's Metadata policy requires the listing to reflect what the app does and does not allow ranking claims or anonymous testimonials in it.

Remove screenshots of unfinished screens. Explain material access conditions, such as a required account or paid feature, wherever needed to make the description accurate. Avoid claims about rankings, endorsements or results that you cannot support.

A useful check is to give someone the listing first, then let them use the app. Ask which expectations the listing created and whether the app met them.

If scope changed during development, update the listing to match. Our guide to how to scope an app MVP can help you define a clear first release.

What if the reviewer cannot use the app?

Test the path from installation to the app's main purpose. A working home screen does not establish that sign-in, loading data or completing the central action works.

Google Play does not allow apps that crash, freeze or function abnormally. If parts of the app need a sign-in, Google asks for sign-in details for review that keep working throughout the review.

Check the submitted release with the access instructions you provided. Confirm that the review account works, required services are available and the app does not depend on information the reviewer cannot obtain.

Try common failure conditions too: a slow connection, a refused permission, an expired session and an empty account. The app should give people a clear way forward where recovery is possible.

Our guide on how to test an Android app before release provides a broader testing structure. See also common reasons Apple rejects an iOS app.

What should you check about account deletion?

If users can create accounts, check the current account deletion policy and its applicability to your app. Do not assume that signing out, uninstalling the app or disabling access addresses deletion.

Google Play requires apps that allow account creation to offer deletion inside the app and through a web page users can reach without reinstalling. Our guide to designing an account deletion flow covers the details.

Walk through the request as a user. Can they find it, understand what happens and complete the process? Then check the result across the systems holding their information.

Where some information must be retained, establish the reason and explain it accurately. Avoid promising immediate or complete deletion unless the process actually delivers that result.

Which common mistakes make resubmission harder?

Avoid these shortcuts:

  • Changing only the declaration. Verify the app's behaviour before changing an answer.
  • Removing a screen but keeping its data flow. Check the underlying component too.
  • Testing a different build. Verify the release package you intend to submit.
  • Fixing only the named screen. Inspect other places using the same permission or component.
  • Resubmitting without evidence. Record what changed and how you checked it.

Before resubmission, confirm that the policy notice, implemented fix, disclosures and test results tell a consistent story. Keep the explanation specific enough that someone else can reproduce the corrected behaviour.

What else do founders ask about rejected apps?

Does a rejection mean the app idea is unsuitable?

Read the stated reason before drawing that conclusion. A broken sign-in flow and a restriction on the app's core activity call for different decisions. Establish whether the issue concerns implementation, disclosure or the proposed service itself.

Should you appeal or submit a corrected version?

If you identify a mismatch, prepare and verify the correction. If you believe the decision rests on a misunderstanding, use the review or appeal instructions provided with the notice and explain the relevant behaviour with evidence. Check the available route in Play Console.

Can a checklist guarantee approval?

No. A checklist helps organise your checks, but it does not replace the policies applicable to your app or the review decision. Use the Play Console policy center for current requirements and investigate the specific reason given in your notice.


Need help preparing a release or resolving a submission issue? Explore our app development and maintenance services.

Ready when you are

Planning an app of your own?

Tell us where your project is today. We will help you work out the scope before you commit to a budget.