Recruiting and verified opt-in
12 to 16 testers (safety buffer included) join your closed track through the official Play Store opt-in link, with genuine Google accounts on physical devices.
Closed testing · Google Play
12 real testers. 14 consecutive days. A report you can show Google.
Since November 2023, personal developer accounts must run a closed test with at least 12 testers opted in for 14 consecutive days before applying for production access. Testeo runs that test: recruiting, daily monitoring, same-day dropout replacement, and a detailed end-of-test report.
12+human testers, real devices
14days of daily monitoring
0 botsno emulators, no fake accounts
Why Testeo exists
Testeo did not come out of a market study. Its founder had to sit through the 14-day closed test himself, for his own app: rounding up twelve people, checking every single day that nobody had opted out, chasing the ones who forgot to open the app — and ending up with no document to show for it. The tools that were missing during those fourteen days are exactly the ones you find here: automatic daily tracking, an alert the moment a tester drops off, and a timestamped PDF report at the end. We sell the service we wish we could have bought.
The rule, verbatim
Personal developer accounts created after 13 November 2023 must keep at least 12 testers opted in continuously for the last 14 days before applying for production access (lowered from 20 to 12 testers on 11 December 2024). Organization accounts are exempt. Source: Play Console Help, article 14151465.
What every test includes
A test is not a checkbox: Google also reviews genuine tester engagement before granting production access.
Daily app usage
Every tester opens and uses the app every day for 14 days. The core flow gets exercised, not just the splash screen.
Continuity monitoring
The opted-in count is checked daily. Any dropout is replaced the same day so the 14-day streak never breaks.
Real bug reports
Crashes, slowdowns, clipped labels, permission issues: every finding is logged with device model, Android version and reproduction steps.
End-of-test report
A dated PDF: anonymised tester list, day-by-day attendance log, bugs found, qualitative feedback, screenshots. Everything you need to answer the production access questionnaire precisely.
Human follow-up
One dedicated contact, replies within 24 business hours, checkpoints on day 3, day 7 and day 14.
Step by step
1
Brief and quote
You describe the app, the flow to test and target countries. You receive a quote and a written agreement.
2
Payment before start
The test is paid in full before launch. Invoice issued immediately, stating the free re-run guarantee.
3
Tester onboarding
You add our email list (or share the opt-in link) in Play Console → Closed testing. We confirm each effective opt-in.
4
14 monitored days
Daily sessions, rolling bug reports, same-day dropout replacement, regular checkpoints.
5
Report and support
Final report delivered on day 14, plus help preparing your production access questionnaire answers (you remain the author of your answers).
6
Guarantee
Production access denied or extended testing requested by Google because testing was insufficient? We re-run a full 14-day cycle at no charge.
Pricing
Price per app, per 14-day cycle, taxes included. Paid in full at order, before the test starts. No subscription, no fee added at checkout.
Cheaper exists: tester bundles go for roughly €15 to €20. What they sell is sign-ups. What we sell is proven days of use — because since 2026 Google no longer counts opt-ins, it checks whether testers actually opened your app.
Starter
€29 / 14-day cycle
- Dated, day-by-day proof of engagement — the number one rejection reason in 2026
- Every day validated by a control question drawn from your own app
- 12 guaranteed opted-in testers (15 onboarded, real people, real devices)
- Same-day dropout replacement
- Per-tester PDF log you can attach to your production access request
- Blocking crash reports · email support within 24 business hours
Most chosen
Complete
€69 / 14-day cycle
- Everything in Starter, with the same 15 testers onboarded and a far deeper mission
- Guided functional flow checklist
- At least 3 written findings per tester
- Detailed report with screenshots
- Prioritised, reproducible bug list
- Production questionnaire drafting help
- Priority support
Studio
€189 from · 3 apps
- 3 apps at the Complete rate
- Specific countries and languages
- Regression testing between builds
- Company invoicing, framework agreement
- Dedicated contact
Roughly 70 % of what you pay goes straight back out as tester pay and payment fees: that is what buys their consistency for 14 days.
The re-run guarantee, spelled out
Everyone writes "approved or your money back". Here is exactly what we cover, what we do not, and with whose money — because a guarantee that promises everything convinces nobody.
Denied for insufficient testing: we re-run it
If Google denies production access citing an insufficient number of testers or insufficient engagement, we launch a fresh 14-day cycle with a new cohort. Free of charge, and as many times as that remains the stated reason.
Extension required: we keep going
If Google asks for a longer testing period, your testers stay opted in and keep checking in every day until the requirement is met. No surcharge, no renegotiation.
Denied for another reason: you still get the evidence
App content, privacy policy, store listing, target API level: that is outside our scope and we will not pretend to cover it. You still receive the full engagement log, which serves as evidence if the rejection also touches on testers.
Funded, not just promised
10 % of every order is set aside to pay for these re-runs, before we count any margin. That is not a marketing line: it is an entry in our accounts, and it is the only reason this guarantee holds when several clients invoke it in the same month.
What we will never do
No bots, no emulators, no account farms, no purchased installs, no fake reviews. Google detects these and they expose you to permanent developer account termination. We also do not promise “100% approval”: the decision is Google's. We guarantee a real, documented, compliant test — and a free re-run if needed.
Frequently asked questions
Does the 12-tester requirement apply to me?
Only if your developer account is a personal account created after 13 November 2023. Organization accounts (verified with a D-U-N-S number) are exempt. Your Play Console shows the requirement that applies to your account.
Is it 12 or 20 testers in 2026?
12. The requirement launched at 20 testers in November 2023 and was reduced to 12 on 11 December 2024. The 14 consecutive days did not change.
Is paying testers allowed?
Paying real people to perform testing work is standard QA practice. What is prohibited and penalised is simulating activity: bots, emulators, batch-created accounts, fraudulent installs. Our testers are real people, on their own devices, genuinely using the app and writing genuine feedback.
What if a tester opts out on day 11?
We check the counter daily and onboard a replacement immediately. Every test starts with 15 testers for the 12 required, precisely to absorb dropouts without breaking continuity.
Why is payment required upfront?
Because paid testers are mobilised from day one. In exchange, the free re-run guarantee is written into the contract and the invoice is issued before the test starts.
How long until production?
Plan for 14 days of testing, then Google's review of your production access request: usually seven days or less, sometimes longer. Prepare your store listing and Data safety section during the 14 days, not after.
Your test can start within 48 hours
Describe your app, get a quote and a precise schedule.