How closed testing works
Google's rule is short and unforgiving: a personal developer account must run a closed test with at least twelve testers, opted in continuously for fourteen days, before it can apply for production access. This is what that means in practice, and what we do about each part of it.
1. You add the app
Two things: the package name, and the opt-in link Play Console generates for your closed test. Without the link there is nothing for a tester to join, so we ask for it before a run can start rather than after you have paid.
2. Testers opt in — and we prove it
Each tester joins with a real Google account on a real device, then sends a screenshot of the opt-in screen. You keep those. If your production application is ever queried, that is what you show.
3. The fourteen days run
The clock starts when the last tester opts in, not when you pay. Google counts testers who are opted in on each day, so a drop-out on day nine is the expensive kind of problem — it can cost you the whole fortnight. We watch daily and replace anyone who leaves the same day, which is the entire reason this service is worth buying rather than assembling from friends.
4. You apply for production
At the end you have twelve or more testers with an unbroken fourteen days behind them, and the screenshots to match. What you do with the app after that is your business — we do not touch your Play Console, and we never ask for your credentials.
What we will not do
- We do not ask for your Play Console login. Ever. Anyone who does should worry you.
- We do not use bots or recycled accounts — Google detects both, and it is your account that pays for it.
- We do not promise approval. We supply the testers and the evidence; Google decides.