Where the application is
Play Console, Dashboard for your app. Once the requirement is met, an Apply for production access task appears. If it has not appeared, the requirement is not met — check the opted-in count and the number of continuous days before assuming it is a bug.
What it asks
- How you recruited your testers
- What feedback you received from them
- What changes you made in response
- How you decided the app is ready for production
All four are asking one question in different words: did real people use this, and did it change because of them?
Answering honestly about paid testers
Say so. Google’s questionnaire lists paid testing services as a recruitment channel, and using one is not a policy problem. Inventing a recruitment story you cannot support is a much larger risk than naming a service.
What separates a strong answer from a refused one
Specificity. Named issues, dated releases, concrete fixes. “The app was tested and worked well” reads as nothing happening. “Two testers reported a crash opening settings while offline; fixed and released to the closed track on day six” reads as a real test.
Worked answers for all four questions.
Before you submit
- 12 or more testers still opted in right now
- 14 full days elapsed since the twelfth opt-in
- Data safety form complete
- Content rating questionnaire complete
- Store listing complete, with all required assets
- Closed track still live — leave it up until access is granted
How long review takes
Google typically responds within a few days, though it can take longer. Keep the closed track running throughout. If access is granted, you then create a production release, which goes through Google’s normal app review before it is live on the store.
If you are refused
A refusal on tester grounds is not a penalty on your account. You keep the same app, the same package name and the same track, and you re-run the 14 days. The checks to run before you start again.