Google Play closed testing, answered.

Only personal developer accounts created on or after November 13, 2023. If your account pre-dates that date, or if you are using an organization account (verified with a D-U-N-S number), Google does not require the 14-day closed testing period before you can publish to production. If you are unsure of your account type, check Google Play Console under Settings → Developer account → Account details.

Google counts the period as complete when 12 or more testers have been continuously opted in for the 14 calendar days immediately before you submit your production access application. A reset happens if your opted-in tester count falls below 12 at any point — even temporarily. There is no partial credit: if the count drops on Day 10, the counter restarts from Day 1. This is why daily monitoring and same-day dropout replacement are non-negotiable for completing the window reliably.

Google's published policy ties the 14-day window to tester opt-in continuity, not to a specific build version. Shipping a build update during the testing period does not appear to reset the timer based on Google's current documentation. That said, we recommend checking directly with Google Play Console support if your situation requires certainty — policies can and do change, and we won't represent a third-party platform's internal rules as fixed.

Physical Android handsets only — no emulators, no BlueStacks, no virtual machines of any kind. Google Play Protect actively identifies emulated environments and flags them in your Play Console device analytics. Our tester pool uses consumer-grade Android phones you can independently verify in your Console after testers opt in. The device models, Android versions, and manufacturers all show up in your Android Vitals.

Our pool covers Android 11, 12, 13, and 14 across multiple device manufacturers — Samsung Galaxy, Google Pixel, Xiaomi, and OnePlus. After testers opt in you will see the specific device models and Android versions listed in your Play Console device analytics. A diverse, multi-manufacturer device list is itself a positive signal to Google's review process that your app has been tested under real-world conditions.

We monitor active tester counts every day. If any tester goes below active status we assign a replacement before the next day begins — so your opted-in count never falls below 12 and the consecutive-day window never resets due to a dropout on our side. Same-day replacement is included on all plans, not just Pro or Agency. This has been our operating standard since day one.

No access required to your Play Console credentials, your APK or AAB file, or your developer account. Our testers join through the standard Google Play opt-in URL — the same invite link you would share with any tester. We never touch your account, your build files, or your release pipeline. Every tester signs a non-disclosure agreement covering your app, its functionality, and any pre-release features before joining your test.

If Google rejects your production application specifically citing testing inconsistency, insufficient tester count, or testing period gaps — we re-run the full 14-day closed test at zero additional charge. No re-order form, no extra invoice, no limit on the number of re-runs. The re-run starts as soon as you notify us of the rejection. This guarantee is included on all three plans: Starter ($15), Pro ($25), and Agency (from $21).

The re-run guarantee covers rejections directly caused by the closed testing period — testing inconsistency, count too low, or period gaps. It does not cover rejections caused by app content policy violations, missing or incomplete store listing metadata (screenshots, descriptions, privacy policy), or reasons unrelated to the testing requirement. If you receive a rejection and are unsure whether it qualifies, email us. We review every case individually.

Yes. Every tester signs a non-disclosure agreement before joining your test. The NDA covers your app's identity, features, design, and any pre-release content they observe during the testing period. Testers are prohibited from discussing, sharing screenshots of, or distributing anything related to your app outside the testing context. This is a non-negotiable condition of joining our network.

Starter gives you 12 testers (Google's minimum), same-day assignment, the questionnaire guidance document, and the free re-run guarantee. Pro adds 3 more testers for a total of 15 — providing a comfortable buffer above the 12 minimum — plus priority assignment under 4 hours, a detailed ASO and UX report on your Play Store listing, and a review of your draft questionnaire answers before you submit them to Google. Both plans include NDA-signed testers, physical-device-only verification, and the re-run guarantee.

One-time fee per app — no subscription, no monthly charge, no automatic renewal. You pay once per app per testing cycle. If Google accepts your production application, you're done. If a re-run is needed due to testing-related rejection, it's covered in your original payment. We do not store payment details or charge you again without your explicit action.

Your order requires a closed testing opt-in link from Google Play Console, which means your app must already be uploaded to a closed or alpha testing track before we can start assigning testers. If your app is not yet ready, you can email us first — we will walk you through the Play Console setup so everything is in order before you order. This avoids setup delays once your build is ready.

If we fail to assign your testers within the guaranteed time window — under 6 hours for Starter, under 4 hours for Pro — you are entitled to a full refund. Once testers are actively opted in and the testing window has begun, we do not offer refunds, as the tester commitment is already live. The free re-run guarantee is your protection against Google-side rejections caused by testing issues. If you have a situation not described here, email us — we handle unusual cases individually.