Google Play's closed-testing requirement, now at least 12 testers opted in for 14 continuous days before you can apply for production access, reduced from 20 testers in December 2024, has a narrow set of exceptions, and they are about your account, not your app. The requirement applies only to personal Google Play developer accounts created after November 13, 2023. So there are two exemptions: organization accounts are not subject to it at all, and personal accounts created on or before November 13, 2023 are also exempt. There is no exception based on what your app does, so a government, nonprofit, or enterprise app on a new personal account still has to run the test; the only way such an organization skips it is by using an organization account.
Short answer
The exceptions to the testers requirement are account-based, not app-based. Per Google's testing requirements, the closed-testing rule, at least 12 testers opted in for 14 continuous days before applying for production, applies only to personal developer accounts created after November 13, 2023. So organization accounts are exempt, and personal accounts created on or before that date are exempt. Per Google's account types, you choose personal or organization when you register, and that choice, along with your registration date, is what determines whether the requirement applies. There is no exemption for government, nonprofit, or any app category.
What the testers requirement is
The requirement is a closed-testing step Google added to raise app quality from new developers: before you can apply for production access to publish on the main Play store, you must run a closed test with a minimum number of real testers for a continuous period. As of December 2024, the minimum is 12 testers who have been opted in for the last 14 days without a break, lowered from the original 20 testers, though the 14-day window is unchanged. Only once you have met it can you apply to release to production.
It is worth stating the number clearly because it changed. Many guides and search results still say 20 testers, which was correct until December 11, 2024, when Google reduced the minimum to 12. The 14-day continuous window and the requirement to have the testers actively opted in remain the same, so if you are subject to the rule, plan around 12 testers for 14 days rather than the outdated figure. The exceptions below are about who has to do this at all.
Who the requirement applies to
The rule applies specifically to personal Google Play developer accounts created after November 13, 2023, which is the date Google introduced it. So the target is new individual developers, the group the policy was designed to raise the bar for. If your account is a personal account and you registered it after that date, you are subject to the closed-testing requirement and must meet it before applying for production.
This precise scoping is what creates the exceptions, because anyone outside that description is not covered. The two dimensions that matter are the account type, personal versus organization, and the registration date relative to November 13, 2023. Everything about the exemptions follows from those two facts, so identifying which account type you have and when you created it tells you immediately whether the requirement applies to you or whether you fall into one of the exceptions covered next.
Exception one: organization accounts
Organization accounts are exempt from the closed-testing requirement, so if your Play Console account is registered as an organization rather than as an individual, you do not have to run the 12-tester, 14-day closed test before applying for production. This is the clearest exception, and it reflects that the policy was aimed at new individual developers rather than registered businesses.
The catch is that account type is chosen at registration and reflects a real distinction. An organization account represents a company or legal entity and requires the corresponding verification, including a D-U-N-S number and matching business details, whereas a personal account is an individual. So the organization exemption is not a toggle you flip to skip testing; it is a consequence of being a verified organization. If you are a business currently on a personal account, becoming an organization is a real registration change with its own requirements, not a quick workaround.
Exception two: personal accounts created before November 13, 2023
Personal accounts created on or before November 13, 2023 are also exempt, because the requirement only applies to personal accounts created after that date. If you registered your individual developer account before Google introduced the rule, you are not subject to the closed-testing requirement and can publish without running the mandated 12-tester test, since the policy was not applied retroactively to existing accounts.
This is essentially a grandfathering exception tied to your registration date. It means two individual developers can face different rules purely based on when they signed up, with an older personal account exempt and a newer one required to test. So if you are unsure whether the requirement applies to you, check when your personal account was created: a creation date on or before November 13, 2023 places you in this exception, while a later date means the requirement applies.
Is there a government or app-type exception?
No. There is no exemption based on what your app is or who makes it, so government apps, nonprofit apps, internal enterprise apps, and any other category are not exempt on the basis of their purpose. The requirement is scoped entirely by account type and registration date, and a government or nonprofit app published on a new personal account is subject to the closed-testing rule like any other app on such an account.
The reason this confuses people is that organizations, including government bodies and nonprofits, often qualify for the exemption, but through the organization account exception, not a special app category. So the practical answer for an institution is to publish under a verified organization account, which is exempt, rather than to expect a carve-out for the app itself. If such an app is on a personal account created after the cutoff, it must complete the test, because there is no app-type exception to fall back on.
Exceptions at a glance
Matching your account to the rule tells you at a glance whether you must test. The table below maps it.
| Your account | Created | Must run the closed test? |
|---|---|---|
| Organization | Any date | No, exempt |
| Personal | On or before Nov 13, 2023 | No, exempt |
| Personal | After Nov 13, 2023 | Yes, 12 testers for 14 days |
| Personal (government or nonprofit app) | After Nov 13, 2023 | Yes, no app-type exemption |
Read the account-type column first: an organization account is exempt regardless of date, while a personal account's date decides the rest.
If you are not exempt: what you must do
If none of the exceptions applies to you, there is no way around the requirement, so plan to meet it rather than to skip it. You need at least 12 genuine testers opted into your closed test, kept opted in for 14 continuous days, before you apply for production access, and the testers should be real people who can actually access the app. Approaches to finding testers and the details of the 14-day window are covered in dedicated guides, but the core is that this is a real testing step, not a formality.
One thing to avoid is trying to fake it. Buying testers or using throwaway accounts to hit the number carries real risk, because Google can detect inauthentic testing and it can jeopardize your account, and it also defeats the purpose of getting real feedback. So if you are subject to the rule, treat the 12 testers and 14 days as a genuine requirement to satisfy honestly, and use the two-week window productively rather than looking for a shortcut that does not exist for your account type.
Checklist
Working through these steps confirms whether you are exempt and what to do. The checklist below covers it.
| Step | Action | Done? |
|---|---|---|
| Check account type | Confirm personal or organization | [ ] |
| Check the creation date | Before or after November 13, 2023 | [ ] |
| Determine exemption | Org or pre-cutoff personal is exempt | [ ] |
| If required, gather testers | Line up at least 12 genuine testers | [ ] |
| Run 14 continuous days | Keep them opted in without a break | [ ] |
| Apply for production | Only after meeting the requirement | [ ] |
The step teams skip most is checking the creation date, since a personal account's exemption depends entirely on whether it predates November 13, 2023.
Where a scan fits
Whether you are exempt is an account-policy question, but if you do run the two-week closed test, that window is a natural time to check your app's security before a wider release.
A scanner like PTKD.com analyzes your Android build for security issues such as exposed keys, over-broad permissions, and risky third-party code, mapped to OWASP MASVS. To be clear about the boundary: PTKD does not grant an exemption or manage your testing track, which are Play Console matters tied to your account. It gives you a security review of the build you are testing, so a required closed-testing period doubles as time to harden the app rather than only waiting out the clock.
What to take away
- The Google Play testers requirement is now at least 12 testers for 14 continuous days, reduced from 20 in December 2024, before applying for production.
- Its exceptions are account-based: organization accounts are exempt, and personal accounts created on or before November 13, 2023 are exempt.
- The requirement applies only to personal accounts created after November 13, 2023, so a later personal account must run the test.
- There is no exemption for government, nonprofit, or any app category; such organizations skip the rule only by using a verified organization account.
- If you are not exempt, meet the requirement with genuine testers rather than faking it, and use the window to scan your build with a tool like PTKD.com.
