Production Access Readiness Checker
Ten questions that map to the ten ways a Google Play production access application actually gets rejected. Answer honestly and you will know, in about two minutes, which one is going to get you.
Nothing is uploaded, stored, or sent anywhere. This runs entirely in your browser.
- 1
You know whether the 12/14 rule applies to your account
Personal developer accounts created after 13 November 2023 must run a closed test before production access. Organisation accounts do not.
- 2
A closed testing track is published and live
Not internal testing, not a draft release. Closed testing, with a release actually rolled out.
- 3
At least 12 testers are opted in right now
Opted in — meaning they accepted the invite and installed from the testing link. Being on the email list is not the same thing.
- 4
All 14 days have been continuous, with nobody dropping below 12
If a tester opts out on day 9 and drops you to eleven, the continuous count restarts from zero.
- 5
A stranger has successfully used your opt-in link
Someone who is not you, on a device you do not own, with an account you did not set up.
- 6
Your testers are actually opening the app, most days
Google asks how engaged testers were. Twelve silent installs reads as twelve silent installs.
- 7
You have collected written feedback from testers
The production access form asks what feedback you gathered. It expects a real answer.
- 8
You changed something in response to testing
The application asks what you did with the feedback. "Nothing" is a bad answer.
- 9
Your store listing is complete: description, screenshots, categorisation
Production review looks at the listing, not just the test.
- 10
Your privacy policy URL is live and reachable
A dead link or a page behind a login is treated as a missing policy.
A note on what does not help
Buying installs or reviews to look more active will not fix an engagement rejection — it is the specific thing Google’s ratings, reviews and installs policy prohibits, and enforcement is account-level. Closed testing activity is safe because it never reaches the public store surface. Keep everything inside the closed track and you have nothing to worry about. Read the policy.