Questions, answered properly
Short answers where a short answer is honest, long ones where it is not.
The requirement
What Google actually asks for, and who is exempt.
If you created a personal Google Play developer account on or after 13 November 2023, you cannot publish to production until you have run a closed test with at least 12 testers opted in continuously for 14 days. Google introduced the rule with 20 testers in November 2023 and reduced it to 12 in December 2024. The 14-day window never changed.
It applies to personal Play Console accounts created on or after 13 November 2023. Organisation (business) accounts are exempt, and so are personal accounts created before that date. Once an app has production access, its future updates never need testers again.
How the service runs
From payment to production access.
Testers usually begin opting in within 6 hours of us receiving your closed testing link, and the group is complete within 24 hours. Your 14 days are counted from the moment the 12th tester opts in, not from when you created the track.
Three things: your app name, the closed testing opt-in link from Play Console, and a WhatsApp number to reach you on. That is the entire onboarding. We do not need your Play Console password and will never ask for it.
You do not add them one by one. In Play Console open Testing, then Closed testing, create or open a track, and set the tester list to allow anyone with the opt-in URL, or send us the list link and we will return the 14 Gmail addresses for you to paste in. We walk you through it on WhatsApp either way.
No. Keep the closed track live and do not remove testers or unpublish the release. We check in around day 7 and again on day 14. Everything else is on us.
You apply for production access from the Play Console dashboard. Google reviews the application and usually responds within a few days. We stay reachable on WhatsApp through that review in case Google asks for anything else.
Testers and legitimacy
Who the testers are, and whether this is allowed.
Yes. Every tester is a real person opting in with their own Google account and installing your app on a real Android device: Samsung, Xiaomi, Pixel, Realme, OnePlus, Vivo, Oppo and Motorola among them. Emulators and fake accounts do not satisfy Google and we do not use them.
No. Google's production access questionnaire explicitly lists paid testing services as a way developers recruit testers. What Google requires is that testers are real people on real devices genuinely using your app, not how you found them. Answer the questionnaire honestly and you are within policy.
Google does not require testers to be in specific countries for closed testing. If your app is geo-restricted, tell us before we start so we can assign testers in regions where your app is actually available.
Yes, and it is common. A rejection usually means testers dropped out, the count fell below 12, or engagement was too thin. You do not need a new app or account. You restart the 14 days on the same closed track. We take it from there.
Yes, 100%. If Google rejects your production access application after our 14-day closed test, we refund the full ₹349. If you would rather try again, we re-run the entire test free instead. Ask within 30 days of the refusal and the refund reaches your original payment method within 3 business days of approval.
You get your money back, or a free re-run, your choice. The only runs the guarantee does not cover are ones ended by you: removing testers, halting the rollout, unpublishing the release, deleting the closed track, or applying before day 14 is complete. Our refund policy sets out the detail.
Price, payment and refunds
Why ₹349, and what happens if it goes wrong.
Because we run one plan and nothing else. No dashboard to build, no account system, no sales team, no ASO upsell. You pay, you send your app link on WhatsApp, testers join. Stripping everything except the testers is the whole reason the price is what it is.
We add 14 testers, not 12. Google needs 12 opted in for the entire 14 days, so if one or two people change phones or drop out mid-run, the extras absorb it and your clock never resets.
Yes, 100%. If Google rejects your production access application after our 14-day closed test, we refund the full ₹349. If you would rather try again, we re-run the entire test free instead. Ask within 30 days of the refusal and the refund reaches your original payment method within 3 business days of approval.
You get your money back, or a free re-run, your choice. The only runs the guarantee does not cover are ones ended by you: removing testers, halting the rollout, unpublishing the release, deleting the closed track, or applying before day 14 is complete. Our refund policy sets out the detail.
All Indian payment methods through Razorpay: UPI, credit and debit cards, net banking and popular wallets. International cards work too. We never see or store your card details.
Yes. Each app needs its own closed test, so place one order per app. Message us on WhatsApp if you are running several at once and we will keep them coordinated.
Answered? Then let's start the clock.
One payment, one WhatsApp message, and the clock is running. No account to create.
- Testers within 6 hours
- 100% money-back if rejected
- No account needed
Closed test complete
14 of 14 days complete, 12 testers held