The Real Risks of Fake Testers on Google Play
Self-made accounts, idle bought opt-ins and emulator farms can meet the 12-tester counter but risk your application and developer account.
Short answer
Fake testers (your own extra accounts, bought idle opt-ins, emulator farms) may get you to 12 on the counter, but they leave you nothing honest to write in the production access questionnaire. Misrepresenting your test can break Google Play’s policies, and account suspensions can extend to linked accounts. A real test is faster in the long run.
What “fake testers” usually means
- Creating extra Google accounts yourself and opting them in.
- Paying for opt-ins from accounts that never use the app.
- Running the app on emulators or device farms to simulate usage.
- Asking iPhone users to opt in when they can’t install the app.
Risk 1: a refused application
The questionnaire asks how you recruited testers, how they used the app and what feedback you received. Fake testers give you nothing true to say. Developers often discover this after 14 days, then have to run a second test anyway.
Risk 2: misrepresentation
Google’s Developer Program Policies prohibit deceptive behaviour, including providing false information to Google. Writing that “12 users tested daily” when they didn’t is the kind of claim that can backfire badly.
Risk 3: your developer account
Google can suspend developer accounts for serious or repeated violations, and its policies allow action against related accounts. The account you paid for and verified with your ID is worth far more than two weeks.
Risk 4: a worse launch
Fake tests don’t find bugs. Real users do, on day one, in public reviews.
What a real test costs
| Fake route | Real route | |
|---|---|---|
| Time to 12 | Fast | 1-2 days with an exchange |
| Evidence for the questionnaire | None | Sessions, feedback, fixes |
| Bugs found before launch | Almost none | Many |
| Account risk | Real | None |
Honest shortcuts that work
- A tester exchange with verified check-ins.
- Your own audience (recruiting guide).
- Swap communities, with a buffer for drop-outs.
See also is it allowed to pay for testers.
Frequently asked questions
Is using friends’ phones with my account fake?
Yes. One account is one tester, whichever phone it uses, and testers should be real independent people.
What should I do if I already used fake testers?
Don’t apply with claims you can’t back up. Run a real test with real testers and answer the questionnaire truthfully.
How can I tell if a paid service is fake?
If you get opt-ins but no usage, no feedback and no crash data, the engagement probably isn’t real.
Sources and how we keep this accurate
- Google Play Developer Policy Center
- Play Console Help: App testing requirements for new personal developer accounts
Policy facts are checked against Google's own documentation on the date shown above. Google can change requirements at any time, so confirm in your Play Console. Where we give advice or estimates rather than Google's rules, we say so. TestersZone is independent and not affiliated with Google. Drafts are AI-assisted and reviewed by our team.
Need 12 testers? Get them free.
Test 3 apps, earn 60 credits, and list your app for up to 20 real testers with verified daily check-ins.
Start freeKeep reading
Is It Allowed to Pay for Google Play Closed Testers?
Does Google Check Whether Your Testers Actually Used the App?
Can You Skip Google Play’s 12 Testers Requirement?
How to Reply to a Google Play Policy Email
The Solo Developer’s Google Play Launch-Day Checklist
10 Common Reasons Google Play Rejects Apps (and Fixes)
Browse all blog, or see the quick answers, guides and comparisons.