Can you buy app reviews? What Google’s policy actually says

Short answer: no, and the services telling you otherwise are selling you a risk they are not pricing. The longer answer is worth your time, because the reason people go looking for paid reviews is usually a real problem that has a legitimate solution.

What the policy actually says

Google Play’s Ratings, Reviews and Installs policy prohibits developers from attempting to manipulate the placement of their apps, and names the specific mechanisms: incentivising or paying for ratings, reviews or installs. Apple says the same thing in App Store Review Guideline 3, in fewer words.

The part people misread is what counts as payment. It is not limited to cash. A review given in exchange for a review, for points, for credits, for a gift card, for entry into a draw, or for anything else of value is an incentivised review. The exchange is the violation. The sincerity of the reviewer does not enter into it, which is why “but they are real people leaving honest opinions” is not the defence it sounds like.

If a review would not have been written without something being given for it, it is incentivised. That is the whole test.

What enforcement looks like

The failure people imagine is that the reviews get deleted. That does happen, and it is the mildest outcome. In its 2024 report on Play security, Google said it prevented more than 2.36 million policy-violating apps from being published and banned over 158,000 developer accounts. Termination is account-level: every app you have published goes with it, and you cannot publish new ones.

The part that matters specifically for exchange networks is that risk appears to travel. Reporting through early 2026 describes accounts inheriting risk by association — a device fingerprint, an IP subnet, a payment method or a phone number that has appeared alongside a terminated account carries that history forward. A review-trading network is, structurally, a dense graph of exactly those signals. Its downside is not distributed across its members independently; it is correlated. If it goes wrong, it goes wrong for a lot of people at once, and the people who lose their accounts are the developers, not the platform that matched them.

Notice also that these services tend to carry a content policy stating that fake, paid or incentivised content is prohibited. Read that next to the product description offering points per review. Both cannot be true. The policy is there to be pointed at when enforcement arrives, and it points at you.

What you actually needed

Almost nobody wants store reviews for their own sake. Underneath the request there are usually one of two problems, and both have answers that do not put the account at risk.

“I cannot publish yet”

If your developer account was created after 13 November 2023, Google will not grant production access until you have run a closed test with at least 12 testers opted in continuously for 14 days. This is the real blocker for most people searching for paid installs, and buying reviews does not solve it at all — closed-track testers are a completely different requirement from store ratings.

The legitimate route is other developers in the same position. Every method for getting 12 testers is worth reading before you pay anyone anything.

“My app is not good enough to earn reviews on its own”

This is the honest version of the request, and paid reviews are the worst possible answer to it. They tell you nothing, they decay, and they buy you a store page that overpromises — which converts into uninstalls and one-star reviews from real users who believed it.

What fixes it is critical feedback from people who know what a shipped Android app should feel like, before your users arrive. Not a rating. A written report that names what broke, on which device, and what they would change.

The line, and where it actually runs

The clearest thing that can be said is about the store surface. Ratings, reviews and production install counts are public signals, and trading for any of them is squarely what the policy prohibits. Closed testing tracks produce none of those signals: tester feedback there does not affect your public rating, and closed-track installs are not production installs.

What that does not buy is a blanket exemption, and you should be suspicious of anyone who tells you it does. Google’s policy language on incentivising installs is not written with a closed-track carve-out, and Google expects testers to be real people giving genuine feedback rather than metrics you assembled. A closed test is a much better place to stand than a store listing; it is not a place the rules stop applying.

So the honest version is narrow rather than reassuring. TesterPool never touches a public rating, review or install count, and it has no mechanism that could. It cannot get you a five-star review and will never offer to. Read the policy yourself before trusting anybody’s summary of it, including this one, and see what is open to testers if you want to look at what we do instead.