Paying for help with a closed test is reasonable. Coordinating 12+ people for 14 days is time-consuming, and not everyone has an Android network.
The problem is that "tester service" can mean very different things. At one end, a real group of people with their own devices. At the other, a pile of accounts that technically satisfy a number and put your app at risk.
What a legitimate service looks like
A good service should be comfortable explaining:
- how testers are recruited;
- that testers use their own Google accounts;
- that testers use real Android devices, not emulators;
- how opt-ins are confirmed;
- how the group is kept active for the full window;
- what happens if someone drops off;
- what the service does not guarantee.
It should also be clear about what you need to provide and what you remain responsible for: the app, the policy compliance, the production-access answers.
Red flags
Be cautious if a provider:
- guarantees production access or approval;
- promises "12 testers in 10 minutes";
- uses emulators or "virtual devices";
- says you can use accounts they control;
- asks for your Google password, recovery codes, or full account access;
- offers to write fake reviews or manipulate ratings;
- is much cheaper than every other option with no explanation;
- has no written scope, refund policy, or contact method;
- cannot explain what happens if testers drop off;
- pressures you to pay immediately.
A guarantee about a Google review decision is a strong sign that the provider does not understand the process or is willing to say anything to close a sale.
Questions to ask
Before you pay, ask:
- How do you recruit testers, and where are they located?
- Do testers use their own Google accounts and Android devices?
- How do you confirm each tester has opted in and installed from the closed track?
- What happens if a tester drops off during the 14 days?
- Do you replace testers? Does the replacement start a new 14-day clock?
- How do you communicate with testers during the window?
- Do you need access to my Play Console? What kind of access?
- What do you guarantee, and what do you not guarantee?
- What is the refund policy if the test cannot be completed?
- How do you handle my app and tester data?
The answers should be specific. "We have a large network" is not an answer to question 3.
What you still own
A tester service can coordinate the group. It cannot make your app compliant or guarantee a reviewer's decision.
You are still responsible for:
- a working build;
- accurate store listing and declarations;
- policy compliance;
- the production-access answers;
- keeping the app available during the test;
- responding to Google if there is a review issue.
If a provider says they will "handle everything" including production access, ask exactly what that means. No one can promise a Google decision.
Access and security
A legitimate service usually does not need your Google password. It may need information you choose to share, screenshots, or a limited role if you decide to grant one.
Never share:
- your Google password;
- recovery codes;
- full account access;
- payment details beyond what is necessary for the service.
If someone asks for these, stop. The risk is not worth the convenience.
A simple contract or written scope
Even a short written scope helps. It should cover:
- what the service will do;
- the timeline;
- the number of testers and the replacement policy;
- what you need to provide;
- what is not guaranteed;
- payment and refund terms;
- confidentiality and data handling.
You do not need a 20-page legal document for a small engagement, but you do need something you can point to if the test goes wrong.
The short version
- A real service uses real people, accounts, and devices.
- No one can guarantee production access.
- Ask how opt-ins are confirmed and what happens on drop-off.
- Do not share passwords or recovery codes.
- Get the scope, timeline, and refund policy in writing.
- You remain responsible for the app and its compliance.
Next: where to find Android testers, or real testers vs emulators.
Our team’s note
If this answered the question but your situation still feels messy, send us the screenshot or the rejection email. Some things are easier to solve in a two-minute conversation than another article.