Closed testing: a tester opted out. Does the 14-day count reset?
You hit 12 testers, then somebody left. The anxiety is understandable. Here is what Google actually says, what it leaves unspecified, and how to stop it happening again.
What Google says
From the FAQ in Google’s testing-requirements article, on “What does continuous 14-day opt-in mean for testers?”:
“Testers who opt in, test for fewer than 14 days, and then opt out do not count toward the requirement. If a tester opts out and opts back in later, the 14 days must be consecutive to count toward the minimum requirement of 12 continuous opted-in testers.”
Two things follow directly: a tester who leaves early stops counting, and a tester who leaves and rejoins starts a fresh run of 14 days. The requirement itself is stated per tester: 12 testers, each opted in continuously for the 14 days before you apply.
What Google doesn’t spell out
Google’s article doesn’t describe in detail how the Dashboard presents the count when your total dips below 12 for a while, or whether anything else resets beyond the individual tester’s run. We won’t guess. Look at the numbers your Dashboard and closed-test page show, and if they’re unclear, ask Google support through Play Console.
The practical fix: a buffer
Because every tester must individually have 14 continuous days, losing one tester when you have exactly 12 leaves you at 11 qualifying testers until you replace them and they complete their own 14 days. Our advice (not a Google rule): aim for noticeably more than 12 opted-in testers (for example 15–20) so a few drop-outs don’t cost you two weeks.
Why testers opt out
- They didn’t know it mattered. Google explicitly tells you to inform testers they must remain opted in for at least 14 days. Put it in the invite, not just the thank-you.
- They cleaned up their phone and uninstalled or left the program. Ask them not to leave the test until you say it’s done.
- They forgot about it. A short reminder around days 3, 7 and 12 helps.
A reminder cadence you can use today
- Day 0 (invite): opt-in link, what to try, where to send feedback, and “please stay opted in until [date]”.
- Day 3: thank you, one feature to try, reminder to stay opted in.
- Day 7: halfway, ask for feedback, remind again.
- Day 12: nearly there, please don’t opt out yet.
- Day 15: done. Thank them and tell them they may leave when you confirm.
Track it somewhere
Keep a simple day-by-day log: date, number opted in as shown in Play Console, and who you chased. A daily check is how you notice a dip early, while there’s still time to replace someone.
Want help keeping the streak alive?
Day15 is a do-it-yourself kit we’re building for developers going through this: an opt-in streak tracker, tester reminder emails, Data safety answers drafted from your app’s permissions, a privacy policy, and drafted production-questionnaire answers. It’s in development, nothing is charged today, and the early-bird price is planned at around $15 one-time.
Sources (Google’s own help pages)
- App testing requirements for new personal developer accounts
- Set up an open, closed, or internal test
Facts about Google Play rules on this page were checked against these pages on Oct 29, 2026. Google changes its policies and Play Console UI; if something here disagrees with Google’s page, trust Google. Practical advice is labelled as ours. This is an independent guide by Anchor Point Apps LLC, not legal advice, and not affiliated with or endorsed by Google.