Google Play Play Console Requirements policy: fixes and checks

By The Draftbit team ยท Updated
Sources checked

This guide is for Developers verifying an account or preparing an app for review.

Incomplete account verification or missing review access can block an otherwise working app. Google requires accurate account information, the appropriate account type, and the resources needed to review your app.

What to check

Check legal identity, address, contact information, linked payments profile, and applicable payment details. Organization information must match the Dun & Bradstreet profile where required.

Certain services must register as organizations: the policy lists financial services, specified health apps, approved VPN services, and government apps. Check your actual service category before choosing a personal account.

Before submission, verify metadata, the privacy policy, Data safety answers, and app-access instructions. Reviewers may need more than a username: include QR codes, setup information, or other resources necessary to reach the functionality.

How to address the rejection

Correct inconsistent account information and complete the verification tasks shown in Play Console. Provide a working demo account and remove avoidable access barriers to review.

Test reviewer access from a clean session without your developer credentials. Explain any required sequence and keep the account active during review. Never include private production credentials or sensitive customer records as review evidence.

Messages this guide can help with

Play Console Requirements; Play Console Requirements policy violation; Play Console Requirements rejection; Play Console Requirements denied

Official sources

We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.

Your next stepSubmit a Google Play release with working review access