You can recruit Google Play closed testers any way you like, but paying for them is where it gets risky. First, the number is not 20 anymore: since December 2024, new personal developer accounts need at least 12 testers opted in for 14 continuous days, not 20. Using real people, including genuine tester-exchange communities, is fine. Paying a service that supplies fake or bot accounts is not, because Google treats manufactured engagement as a policy violation that can cost you strikes or your account.
Short answer
Recruiting testers is allowed; buying fake engagement is not. New personal accounts must run a closed test with at least twelve testers opted in for fourteen continuous days, a rule Google reduced from twenty in December 2024, and those testers are expected to actually use the app. Real testers from your network or a genuine exchange group are safe. Paid quota-filling services that rely on fake or farmed accounts risk violating Google's manipulation policy, and repeated or serious violations can lead to account termination. The compliant path is also the one most likely to actually satisfy the requirement.
The requirement: what Google actually asks for
For a new personal developer account, Google requires a closed test with at least twelve testers who have opted in and stayed opted in for at least fourteen continuous days before you can apply for production access. The count dropped from twenty to twelve in December 2024, after Google acknowledged how hard the original number was for solo developers. The fourteen-day clock is continuous, so losing testers partway through can set your progress back.
The point of the rule is quality: Google wants real users to try new apps and surface problems before a public launch. That framing matters for the "buy testers" question, because the requirement is not just a headcount. Google can ask you to keep testing if your testers are not genuinely engaged, which is exactly what passive or fake testers tend to be.
"Buying" testers: what people mean, and where the line is
"Buying testers" covers a range, and the risk depends entirely on what you are actually paying for. At the safe end, some developers join paid or free tester-exchange communities where real developers install and use each other's apps; the testers are genuine people giving genuine engagement. At the dangerous end, some services simply supply installs from fake or farmed accounts to tick the box.
The line Google cares about is authenticity. Real people who opt in and use your app are legitimate testers, however you found them. Fake accounts, bot installs, or "testers" who never open the app are manufactured engagement, and that is what the policy prohibits. Paying money is not itself the violation; faking the engagement is.
Will Google ban my account for buying testers?
It can, if what you bought amounts to fake engagement. Google's policies prohibit manipulating your app's placement, ratings, or installs by illegitimate means, and the enforcement process is explicit that repeated or serious violations can result in termination of your account and related accounts. A single risky choice may draw a strike; a pattern can end the account.
The safer way to think about it is risk versus reward. The requirement exists to get your app tested, and the downside of a fake shortcut is losing the developer account you are trying to launch on. Genuine testers cost you outreach effort, not your account, which is a far better trade for something you are about to build a business on.
Are Fiverr testers safe?
It depends on who the seller actually provides. If a Fiverr seller connects you with real people who opt in and genuinely use your app, that is closer to a recruiting service than to fake engagement, and the main risk is quality and reliability. If the seller uses fake accounts, shared device farms, or testers who install and never return, you inherit the policy risk, because that is the manufactured engagement Google acts against.
The table below compares the common options by risk.
| Option | What it is | Risk level |
|---|---|---|
| Real people you know | Friends, colleagues, existing users | Low, compliant |
| Genuine tester-exchange group | Developers who test each other's apps | Lower, reciprocal |
| Paid quota-filling service | Sellers who supply testers, sometimes fake | High, policy risk |
| Bot or fake-account installs | Automated or farmed accounts | Severe, likely termination |
Because you often cannot verify what a cheap fill-my-quota gig actually uses, the uncertainty is itself a risk. If you use any paid help, prefer services that clearly supply real, engaged testers, and treat anything promising instant results with fake accounts as a red flag.
Why paid testers often fail the requirement anyway
Even setting policy aside, bought testers frequently do not satisfy the rule. Google looks for opted-in testers who stay opted in for the full fourteen days and show engagement, so testers who install once and vanish, or who quietly opt out, can leave you short when you apply. You can pay and still not qualify.
This is the practical trap: the fake shortcut is both against policy and unreliable at the one job you paid for. Real testers, by contrast, tend to stay opted in and actually use the app, which is what the fourteen-day engagement window is checking for. The compliant route is usually the one that actually works.
Legitimate ways to get 12 real testers
Finding twelve real testers is very doable with a little outreach. Start with your own network: friends, family, colleagues, and any existing users can opt in through your closed-test link. From there, developer communities are the most reliable source, and many run on a reciprocal basis where you test other people's apps in return.
| Method | How to do it | Effort |
|---|---|---|
| Personal network | Ask 12 or more people you know to opt in | Low |
| Developer communities | Post in subreddits, Discord, and forums, offer to test back | Medium |
| Tester-exchange groups | Join genuine "I test yours, you test mine" groups | Medium |
| Existing users or beta list | Invite an email list or current users to the test | Low if you have one |
Reciprocity is the key idea. Genuine tester-exchange groups on Reddit, Discord, and dedicated forums work because everyone needs the same thing, so offering to test other apps in return gets you real, engaged testers who count toward your requirement without any policy risk.
How to set up closed testing correctly
In Play Console, create a closed testing track, add your testers by email list or a Google Group, and share the opt-in link so each tester joins. The fourteen-day clock is based on testers being opted in, so get all twelve in early rather than trickling them in, which only delays the date you can apply. Keep the track active and the app updated during the window.
Track engagement as you go. Ask your testers to open the app and try the main flows, since that genuine use is what the requirement is looking for. When you have held twelve opted-in, engaged testers for fourteen continuous days, apply for production access on the Play Console dashboard and answer the readiness questions honestly.
Test for a real launch, not just to tick a box
It is easy to treat the tester requirement as a hoop and forget its purpose, which is shipping an app that is actually ready. Your testers will surface crashes, confusing flows, and broken features, but they will not see the security problems underneath: an embedded API key, cleartext network traffic, or data leaking through an exported component. Passing the tester gate says nothing about whether your app is safe.
A scanner like PTKD.com analyzes your .apk and returns findings ordered by severity and mapped to OWASP MASVS, so the closed-testing period is also when you catch security issues before real users are exposed. To be clear about the boundary: PTKD does not provide testers, and it cannot help you pass or shortcut Google's requirement. It covers the part of "production ready" that a tester count never measures.
What to take away
- The requirement is now at least twelve testers opted in for fourteen continuous days, reduced from twenty in December 2024.
- Recruiting real testers, including genuine exchange groups, is fine; buying fake or bot engagement is a policy violation.
- Google can issue strikes or terminate accounts for manufactured engagement, so a fake shortcut risks the account you are launching.
- Paid testers often fail the engagement check anyway, making the compliant route both safer and more reliable.
- Use closed testing to also scan your build with PTKD.com, because testers will not catch security problems.
