Closed testing basics

Is it allowed to pay for Google Play closed testers?

November 15, 2026 · 5 min read

An open book, eyeglasses, and smartphone on a wooden desk, illustrating a classic study setting.
Photo by Pixabay on Pexels

Google Play's official policies don't mention paid testing services or paid testers at all, so there is no official rule that either allows or forbids them. What the policies do clearly forbid is paying for ratings, reviews or installs, and trying to evade app review. Paying people for their time to genuinely try a test build isn't addressed by those rules either way. Paying for reviews, inflated installs or bots clearly is.

That is the honest answer, and it's less tidy than either "yes, it's fine" or "no, you'll get banned." The rest of this article explains where the line is and how to stay on the right side of it.

What Google's official policy says, and doesn't say

We searched the Developer Program Policy and the ratings and reviews policy. Neither mentions testing services, paid testers or "testers" in this sense. The testing requirement itself, from the App testing requirements page, only says that personal developer accounts created after November 13, 2023 "must run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days." It says nothing about how you find those testers, beyond suggestions.

Those suggestions are worth knowing. Google recommends you "reach out to friends, family, colleagues, or classmates," "connect with communities where potential users exist," and look for testers who "represent your app's intended future audience." Paying someone isn't on the list, but it isn't excluded either.

So the status of paid testing is simply not defined in official policy. Google may change its documentation at any time, so if you're reading this much later, check those pages again.

What a Google Product Expert said

The most-cited source on this question is the community guide Everything about the 12 testers requirement, written by volunteer Product Experts on Google's community site. It says:

"You can also reach out to third-party companies who are specialized in testing, it does not violate the policy."

The same guide adds that "Google does not have control over the third-party testing company," and warns that "people offering access to groups in return for a fee are not recognized testing companies."

Two things to keep in mind:

  • This is a community view, not Google policy. Product Experts are knowledgeable volunteers, but their guide is not official documentation. Don't treat it as Google approving paid testing.
  • Nobody is endorsed. Google doesn't publish any approved or partner testing services. If a provider claims otherwise, that alone is a reason to walk away.

What is clearly prohibited

Here the official text is direct. The User Ratings, Reviews, and Installs policy says developers must not manipulate their app's placement, including "inflating product ratings, reviews, or install counts by illegitimate means, such as fraudulent or incentivized reviews and ratings." Its summary adds: "We prohibit any manipulation of ratings, reviews, or install counts. This includes incentivizing feedback… or paying for fake reviews."

The Developer Program Policy also states: "Techniques to evade app reviews are not allowed."

Where the practical line falls

Not addressed by written policy Prohibited, whoever you pay
Real people opting in to your closed test Ratings or reviews, on the test or later in production
Real people's time trying a test build for 14 days Installs to inflate counts or rankings
Private feedback sent to you during the test Bots, emulators or bulk-created accounts posing as testers
Coordination: reminders, replacing dropouts Anything presented as a way around review or the 14 days

The left column is the work Google asks for: people trying your app. The right column is manipulation. Note that the policy names incentivized installs that inflate install counts or placement; Google hasn't said how that applies to people taking part in a closed test, which is one more reason the status of paid testing stays unclear. Using fake or automated accounts is not named word for word in the policy, but it goes against the idea of real people testing and likely counts as manipulation, so treat it as off limits.

One useful detail: "Testers cannot leave public reviews on Google Play for test versions," and private feedback "won't affect your app's public rating" (Set up a test). A service offering reviews for your closed test is offering something that either can't happen or would happen after launch, in production, where it is clearly prohibited.

What Google actually checks

Whoever your testers are, Google looks at the same things:

  • The count and the continuity. At least 12 testers must be opted in when you apply, and they must have been opted in continuously for the preceding 14 days.
  • Engagement. Google may require more testing, giving "fewer than 12 opted-in testers or insufficient tester engagement during the testing period" as reasons.
  • Your answers. The production access form asks how easy it was to recruit testers, how they engaged, what feedback you got and what you changed. What Google reviews in production access walks through it.

Testers who opt in and do nothing don't help with that second point. Paid or unpaid, what matters is that people actually use the app. Showing engagement during your closed test covers how to make that visible. Google makes the final decision either way.

A checklist for a legitimate testing service

A service that stays in bounds should:

  • Use real people with their own Google accounts
  • Test on real Android devices, not emulators
  • Keep testers opted in for the full 14 continuous days, with a plan for dropouts
  • Have testers open and use the app, and send private feedback you can summarize
  • Explain clearly how testers join: a Google Group or a list of emails you add
  • Be transparent about price, process and refund terms

It should never:

  • Offer ratings, reviews or installs
  • Promise guaranteed approval or a fixed approval date
  • Claim to shorten the 14 days or make fewer than 12 testers work
  • Ask for your Play Console login or Google account password (it only needs you to add its testers to your track)
  • Claim a partnership with, or approval from, Google
  • Sell access to a group without any actual testing behind it

For a fuller set of questions to ask before paying, see choosing a closed testing service.

Is it worth paying at all?

You don't have to. Recruiting friends, family and communities is free and is exactly what Google suggests. A service mainly saves time and coordination. How much closed testing costs compares the free and paid routes side by side.

For transparency: GoPlayTester is a paid service of this kind, with real testers on real Android devices for 14 continuous days, and no promise of approval because Google decides. If that fits your situation, details are on the order page; if not, the checklist above works for any provider, or for organizing your own testers.

All articles