Yes, keep 12 testers opted in for 14 days

Do I need to keep 12 testers opted in for 14 days before Google Play will review my production access request

Yes. For a new personal Google Play developer account, you need 12 testers who stay opted in continuously for the preceding 14 days before you submit a production access request. Google Play then reviews the request after you apply, and the review is a separate step.

The part people get wrong is the timing. Google does not want 12 people who signed up at some point in the last two weeks. It wants 12 people still opted in when you apply, and each of those tester opt-ins must cover the full 14-day window without a break.

Google’s help page says the 14 days must be consecutive. If a tester opts out and opts back in later, the clock does not keep running from the first opt-in. That tester has to complete a fresh 14-day stretch before they count again.

What matters for your request is the state at submission time. The requirement is not “collect 12 testers once” and then move on. It is “have at least 12 testers continuously opted in for at least 14 days, then apply for production access.” Google’s help center states that the application is reviewed after submission, and that continued testing can still be required if the requirement is not met.

The inconvenient part is that one dropout can force you to wait longer. If you had exactly 12 testers and one person opted out on day 13, you no longer meet the minimum. In that case, the safe move is to recruit another tester, get them opted in, and restart your 14-day count from the point where you again have 12 continuous opt-ins.

Do not treat buying testers or installs as a shortcut. Google Play policy treats incentivized or inauthentic engagement as a policy issue, and fake engagement can put the account at risk. DevConnect is for exchange-based testing on your own app and on apps owned by other developers, not paid tester schemes and not artificial installs.

If you are setting this up now, the practical workflow is simple. Add more than 12 real testers, confirm they are opted in to the closed test, wait until the full 14-day continuous window has passed, and then submit the production access request. A little extra buffer helps, because it avoids restarting the clock if one tester leaves early. DevConnect’s testing exchange can help you find real testers for your own app without charging them. That is separate from Google Play’s requirement, which still has to be met inside Play Console.

Google also distinguishes this closed test from internal testing. Internal testing can include up to 100 testers, but it does not count toward the closed testing requirement for production access. That is the part that surprises people who assume any test track will satisfy the rule. It will not.

The cleanest way to think about it is this: closed testing is the gate, the 12 continuous opt-ins are the key, and the 14 days are the lock. Once that window is complete, you can apply. Google then decides whether your submission is ready for production access, and it may ask for more testing if your closed test did not meet the requirement.

If you want the shortest possible answer for your checklist, use this: keep at least 12 testers opted in without interruption for 14 straight days before you submit, then wait for Google’s review. Do not submit early, and do not let the tester count drop below 12 before you apply.