ReviewProof ⚖

Why are employee reviews of your own business a violation risk?

By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026

Run the free review audit See pricing · See a sample provenance report

Short answer

Because the reader is deceived about who is speaking. The FTC rule bans insider reviews presented as independent customer opinion: employees, owners, close contractors and immediate family reviewing the business without a clear disclosure of the connection. In an audit, insider reviews surface as what they are mechanically — UNLINKED rows (no transaction exists), often clustered at launch or after a bad week, sometimes sharing fingerprints or wording with the business's own materials. The fix is a written rule (insiders do not review, full stop), the rows flagged honestly when found, and every future ask confined to real customers through the standard flow.

What is an insider review?

An insider review is a review of a business by a person whose connection to it — employment, ownership, close contracting, immediate family — a reader would want to know and is not told. The category is about undisclosed interest, not about enthusiasm: a staff member may genuinely love the product, and their five stars are still a violation when presented as a stranger's verdict. Disclosure can cure some insider commentary in some settings; for a business's own profile, the only safe operating rule is abstention.

How insiders get in — almost never by conspiracy

The launch rally: the owner asks the team to 'help us get started' and six staff reviews appear in week one. The rescue: a brutal one-star lands and a loyal manager 'balances' it from a personal account. The agency handover: a contractor who built your site reviews it as a delighted customer. The family favour: a cousin in another city writes the review your first real customer has not yet written. Each act is small, warm and explicable — and the cluster is legible in the file to any examiner as early-dated, UNLINKED, sometimes similarly worded, sometimes (when the same person reviews the group's other locations) visible to the pooled graph. The audit does not need to prove who anyone is; it needs the business to have a rule, and to have looked.

Triage starts from your own data, not from the public profile. Import the reviews, look at which rows carry which signals, and separate three questions that are often mashed together: is this review about a real transaction, was it solicited in a way the FTC rule prohibits, and what record do we hold if anyone asks? ReviewProof answers the first two from the imported rows — transaction link present or UNLINKED, gating or incentive language present or absent — and answers the third with the provenance chain. What it will not do is declare a review fake: signals are heuristics for human review, and acting as if they were verdicts creates a new problem while solving none.

The policy that prevents the next cluster

Write it in one paragraph and put it where new staff will meet it: nobody employed by, owning, contracting closely with, or immediately related to the business may review it on any platform, under any account, at any time — disclosure or not, because the business will not rely on disclosure judgements made at a keyboard at midnight. Cover the grey zones explicitly: former staff (a cooling-off period, and never for the period of their employment), suppliers (their commercial interest is the same shape), and the multi-location trap, where staff of location A review location B imagining distance cures it — inside one business, it does not. Then handle history as the audit prescribes: found insider rows stay in the record, flagged internally with the identification basis stated carefully, and the policy's start date is logged.

ReviewProof's import is forgiving about format and strict about meaning. Column names are matched flexibly — body, review or text for the review itself; rating or stars; reviewer, author or name; a verified flag and a transaction reference when you hold them. Rows are capped per import by plan (500 on Free, 5,000 on Pro, 50,000 on Agency), which is generous for a single location's history. What the importer will not do is upgrade a review's status: a row that arrives without a transaction link is analysed fully and still labelled UNLINKED, because the label is the product.

Mistakes that undo the work

Asking staff to disclose in the review text ('I work here but honestly…') and imagining the problem solved — the operating rule is abstention, because disclosure quality cannot be supervised. Quietly asking the insiders to delete their reviews converts a policy gap into a doctored record; flagging is the remediation, deletion is the cover-up. And retaliating against the audit finding by disputing the rows as 'fake' to the platform misdescribes them: they are insider reviews, a different and more honest label.

Keep the negative reviews. That instruction surprises people mid-crisis, but suppression is itself a violation under the FTC rule, and a profile scrubbed clean during an attack reads as manipulation to anyone who later examines it. ReviewProof has no silent-delete path: moderation decisions are kept, published or flagged internally, each one is logged in the chain of custody, and the evidence export counts the negatives you kept. The strongest response to a suspicious review is a boring, complete record — the row, the dates, the signals, the decision, all preserved while you dispute through the platform's own process.

Worked example: launch week, found in the first audit

A fictional worked example, written to show the numbers and the decisions in practice.

A consultancy's first import showed 7 reviews from its launch fortnight with no transaction links, six of them five stars, two sharing long phrases with the firm's own website copy. The partners recognised the pattern before the auditor finished the sentence: the founding team and two spouses, from a launch-evening request none of them had thought about since. The firm flagged all 7 internally, recording the identification basis ('identified by the partners as staff and spouses from launch week'), adopted the one-paragraph policy into its staff handbook that month, and let the profile's growth come from clients thereafter. When the pattern later surfaced in a client's due-diligence question about the firm's own marketing, the managing partner answered with the audit page itself — the shortest such meeting in the firm's history.

Your five-action checklist

  1. Adopt the one-paragraph rule: insiders never review the business
  2. Cover former staff, contractors, suppliers and other locations explicitly
  3. Audit early-date and UNLINKED clusters for insider patterns
  4. Flag identified rows with the basis stated carefully and factually
  5. Brief the rule at onboarding; log the policy and its start date

Frequently asked questions

Can an employee ever review their employer?

Under the FTC rule an insider review without clear disclosure of the connection is prohibited; some disclosed contexts exist, but the only safely operable business rule is that insiders do not review the business at all.

What about a genuinely satisfied staff member's spouse?

Immediate family sits inside the insider category for the same reason: undisclosed interest. The abstention rule covers them.

How can an audit tell a review is an insider's?

Mechanically it cannot prove identity — it surfaces the pattern: no transaction link, launch-era or reactive timing, wording overlaps, pooled-fingerprint links. The business's own knowledge completes the identification, which is then logged honestly.

Should identified insider reviews be reported to the platform?

They can be flagged in your record and, where the platform's policy provides for it, reported as insider reviews. Your own log should use the accurate label, not 'fake'.

Keep reading

Related guides from the ReviewProof library:

Start with the tool itself: open the free audit desk, see how ReviewProof works, compare Free, Pro and Agency plans, inspect the sample provenance report, or browse all ReviewProof guides.