The FTC Fake-Review Rule for App Developers, in Plain English

Buying, selling, or writing fake app reviews is now a federal offense in the United States, and yes, it applies to you on both the App Store and Google Play, whatever your company's size or where it's based. The FTC's Rule on the Use of Consumer Reviews and Testimonials took effect on October 21, 2024, and it turned a lot of quiet growth-hacking into illegal conduct with a price tag: civil penalties of up to $53,088 per violation (FTC, 2025 inflation-adjusted amount). Not per campaign. Per fake review.

This isn't a store-guidelines problem Apple or Google enforces with a slap on the wrist. It's 16 CFR Part 465, enforced by a federal agency that can sue for money. Staying on the right side of it is genuinely simple, though, because the only durable review strategy, earning real reviews and then replying to them, was never the thing the rule bans. Below: what's actually prohibited, what counts as a "violation," the parts app teams get wrong, and the compliant path that also lifts your rating.

The rule targets deception in the review ecosystem, full stop, whether the fake was posted by a farm overseas or typed by your own intern on launch night. Here's the plain-English version of the six things it prohibits.

Yes. The rule is written around "consumer reviews" as a category, not around any one platform, so it covers app store reviews the same way it covers Amazon, Yelp, or a Google business listing. The store's own policies against fake or incentivized reviews still exist and still get you delisted, but the FTC rule sits on top of them as federal law with financial penalties the stores can't levy.

It also doesn't matter that Apple and Google host the reviews. Liability follows whoever created, bought, or procured the fakes, or suppressed the real ones. A solo developer who spends $50 on a gig to "boost my launch reviews" has done the prohibited thing as squarely as a funded studio at scale. If you're weighing that shortcut, [what happens if you buy app reviews](/blog/what-happens-if-you-buy-app-reviews) walks through the platform side; the FTC rule is why the downside now includes a federal fine, not just a takedown.

The headline number is up to $53,088 per violation, an amount the FTC adjusts for inflation each year (it was $51,744 when the rule was finalized in 2024). The words doing the heavy lifting are *per violation*. Regulators have signaled that each fake review, and in some readings each consumer who sees it, can count separately. A few hundred bought reviews isn't one $53,088 exposure; it's arithmetic that gets frightening fast.

Be realistic about enforcement, though. The FTC goes after organized deception, not a single misjudged review, and it has no button to clean up your listing. But "they won't come for a small fish" ignores the likelier damage: the stores enforce quietly and constantly, and a rating built on fakes evaporates the moment their detection catches up ([are App Store reviews fake?](/blog/are-app-store-reviews-fake) covers how good that detection has gotten). The rule's point isn't that you'll definitely get fined; it's that the buy-reviews playbook is now downside with no floor.

Most developers reading this aren't running review farms. The exposure hides in "growth" tactics that felt normal a year ago. Three catch people out.

Here's the part that should make this easy. The tactic the rule can't touch, genuinely earning reviews and then publicly replying to them, is also the one with the best evidence behind it. Google reported at I/O 2019 that developers who respond to reviews see an average lift of 0.7 stars. A study of over four million reviews by Hassan et al. found users were roughly six times more likely to raise their rating after a developer replied (4.4% versus 0.7% with no response). You don't need a single fake review to move your rating. You need real ones and a habit of answering them.

A public reply does the work a fake review pretends to do, except it's true, compliant, and visible to every future installer. A calm, specific answer to a one-star is worth more than ten purchased five-stars, at zero legal risk. For why replies move ratings, [what happens when a developer replies to your review](/blog/what-happens-when-a-developer-replies-to-your-review) has the full breakdown.

That reply is real, useful, under Google Play's 350-character cap, and does more for your rating than any bought review could: the reviewer and everyone reading after them can see a team that fixes things. That's the whole strategy the FTC rule leaves wide open.

The catch is doing it consistently, across both stores, in the reviewer's language, without a busy week letting a hundred reviews pile up. That's the gap [ReplyArgus](/features) fills: it watches your App Store and Google Play reviews in one inbox and drafts an on-brand reply to each, grounded in your past approved replies and your store listing, never invented, and sized to each store's limits. You approve before anything posts. Nothing about it touches the fake-review line; it just makes the compliant path fast enough to keep up with.

The honest path always won on the merits; the FTC rule just made the shortcut a federal liability on top of a rating that vanishes the moment detection catches up. Earn the reviews, answer them fast and well in every language your users write in, and the only review strategy that's legal turns out to be the one that actually moves your rating.