From order to production approved. In 4 simple steps.

Yes. Google requires at least 12 opted-in testers for at least 14 consecutive days, and it does not restrict who your testers are or how you find them. We provide real people on real Android devices who genuinely install and use your app, which is exactly what the requirement asks for. What Google forbids is fake engagement: bots, emulators, and incentivized installs. We never touch those. 7,400+ apps have been approved through this exact process with zero developer accounts banned or penalized.

Plan for about 15 days from order to your production application. Setup happens within 4-6 hours, the 14-day clock starts as soon as our testers opt in, and on day 14 you apply using the questionnaire answers we hand you. Google says its review usually takes 7 days or less, though it can occasionally take longer. If you are racing a deadline, order in the morning and message us on WhatsApp; setup is the only part that can be compressed, and we compress it.

You choose: a full refund or a free retest, as written in our refund policy. With a 99.9% success rate this is rare, and a pushback usually means Google wants to see more genuine testing activity or clearer questionnaire answers. Both are fixable: we rerun the 14-day cycle at no cost and tighten your answers before you reapply. Our breakdown of why closed testing gets rejected shows the usual causes.

No. Your part is pasting an email list into Play Console and sending us the opt-in link, about 3 minutes with the step-by-step instructions in your dashboard. We handle everything else, and support answers on WhatsApp within minutes if your console looks different from the guide. The full walkthrough with screenshots is in our guide on how to invite testers.

You can verify it yourself, in your own Play Console: the closed testing track shows exactly how many testers have opted in. Every tester is a verified human on a physical Android device across 120+ countries; we never use emulators or bot accounts, because those typically do not count toward the requirement and they put the developer account using them at risk. The bug reports you receive are written from real sessions on real phones.

We monitor tester activity every day of the window and replace any dropout immediately at no extra cost, so your count never falls below Google's minimum. The Professional and Enterprise plans also run 8 and 13 testers above the requirement as a built-in buffer. Keeping the streak unbroken is the entire job you are paying us for, and it is why developers who tried recruiting volunteers come to us after their count dipped mid-test.

Three one-time plans: Starter is $19.99 for 12 testers, Enterprise is $27.99 for 25 testers (the most popular), and Professional is $29.99 for 20 testers. Every plan includes the full 14-day closed test, real devices, a written report, questionnaire answers, and free retesting. No subscription, nothing renews. The full breakdown is on our pricing page.

No, never. You add the tester list to your own console yourself, which takes about 3 minutes, and the only thing you send us is the public opt-in link Google generates. We never ask for your password, your console access, or your developer account details, and you can watch every opt-in appear in your own dashboard. You stay in full control of your app and your account the entire time.

The clock starts when testers accept your opt-in link, not when you paste their emails into the console. That distinction catches a lot of developers who add testers and wait while nothing counts. With us it stops mattering: our testers opt in within hours of receiving your link, your dashboard shows the day counter from day 1, and we watch that the 14-day window stays unbroken until the end.

Yes. Uploading new versions to the closed track during the 14 days is allowed and does not reset the clock, so you can ship fixes as our testers report bugs. Many developers use the two weeks exactly that way and reach Google's review with a stronger build than they started with. The details are in our guide on updating your app during closed testing.

Two things: a Google Play developer account with the $25 fee paid, and your app uploaded to a closed testing track in Play Console. Internal testing does not count toward the requirement, so the build must sit on a closed track; our comparison of the testing tracks explains the difference. If your app is not on a track yet, order anyway and message us on WhatsApp; we walk you through the upload live.

No. Google counts opted-in testers wherever they live, and your launch countries are a separate setting in your store listing. The one thing to check is that your closed test track is available in the testers' countries, which we cover during setup. Our guide on testers in different countries breaks down both gates.