Part 8. Retaliation as a Separate Tort

Reading the Platform — Part 8 of 21.

Anderson v. TikTok punched the first hole in the wall of 1996 — a platform’s algorithmic decisions stopped being “the pipe” and became its own speech.

The second hole is of a different nature. It isn’t about the algorithm. It’s about motive.

When a platform bans an author in response to a specific act by that author — a complaint to a regulator, public criticism, contacting a lawyer — that is no longer moderation. It is a separate category of action, and in legal language it has a name.

That name is retaliation. And Section 230 does not shield against retaliation claims.

What retaliation means in the legal sense

The doctrine is not new. It exists in American law across several fields.

Employment law. If an employee files an EEOC complaint about discrimination and the employer fires them — that is retaliation. The claim proceeds regardless of whether the discrimination was real to begin with. The revenge for the complaint is itself a separate cause of action.

Housing law. If a tenant reports a sanitary-code violation and the landlord evicts them — retaliation. The claim proceeds even if the eviction would be formally lawful on other grounds.

Whistleblower protection. If an employee discloses a violation and the company punishes them — a separate claim.

In every case the logic is the same: the law protects the right to complain. If every complaint guaranteed revenge, no one would complain. The whole control system would stop working.

That is why courts and regulators treat retaliation as a standalone tort — not “breach of an employment contract,” not “breach of a lease,” but a separate cause of action with its own elements of proof.

And the doctrine keeps expanding into new areas. Including the relationship between a platform and an author.

The elements of proof

To prove retaliation you need three things. They are standard across all fields.

First. Protected activity. A protected act by the claimant. A complaint to a regulator is protected. Public criticism is protected. Consulting a lawyer is protected. Going to the press is protected.

Second. Adverse action. A hostile act by the respondent. Firing, eviction, a ban, content removal, demotion in ranking — all of these are adverse actions depending on context.

Third. Causal connection. A causal link between the first and the second. This is the hardest part. Direct proof is rarely available (no one writes “we fired you for complaining”). So courts look at circumstantial evidence.

The key circumstantial evidence:

— Temporal proximity. The closer in time the protected act and the hostile act, the stronger the presumption of a link. Hours and days — very strong. Weeks — strong. Months — weaker.

— Pattern of conduct. A consistent pattern of behavior. If the respondent systematically punishes complaints — that is a pattern.

— Absence of an alternative explanation. If the hostile act happened “out of nowhere,” with no trigger from the claimant, the presumption of a link strengthens.

Why Section 230 does not shield against retaliation

This is the crucial point. Section 230 protects a platform from liability for content moderation. The immunity operates in the realm of “publishing decisions.”

Retaliation is not a publishing decision. It is a decision whose motive lies outside the realm of moderation. The motive is to punish an external act by the claimant.

Legally, these are different things.

An example. A platform bans an author for “violating the rules” — that is the realm of Section 230. A platform bans an author in response to a lawsuit against the platform — that is outside Section 230. The external motive pulls the act out of the immunity.

This is not a theoretical position. It works in adjacent areas. Whistleblower retaliation is not shielded by “the employer’s right to hire and fire whomever it wants.” A lease is protected by contract, but retaliatory eviction is not shielded by that contract.

In the same way, a ban is shielded by Section 230 in the general case. But a retaliatory ban is a separate cause of action. Section 230 is the shield of moderation, not the shield of revenge.

This is a framing that has not yet been directly affirmed by the U.S. Supreme Court with respect to platforms. But the logic is standard and well known. Regulators use it. Lower courts apply it.

Where it already works in adjacent areas

There is no direct federal precedent for a “retaliatory platform ban” yet — it is a forming theory. But the logic is borrowed from settled areas.

Employment law. The retaliation doctrine under Title VII of the Civil Rights Act has applied for decades. The key elements of proof (protected activity, adverse action, causation through temporal proximity) are standard and well developed.

Housing law. Retaliatory eviction is a separate tort in many U.S. states. California Civil Code § 1942.5 expressly prohibits evicting a tenant in response to complaints to regulators. The same logic, applied to a different field.

Whistleblower protection. Sarbanes-Oxley Act § 806, Dodd-Frank § 922 — federal laws protecting employees from punishment for disclosing violations. Here the retaliation doctrine is most developed.

FTC and state AG investigations. Regulatory agencies have, in recent years, paid attention to practices where companies punish users for going to regulators. Concrete public cases against tech platforms along this line are still rare, but the direction of regulatory movement is visible.

Applying this to platforms is an extension of a well-developed doctrine into a new field. The extension will have to be argued. But the fundamental logic is not new.

What close timing means

The hardest element to prove is the causal link. The strongest circumstantial evidence for it is timing.

When a ban lands within hours or a day of an author’s protected act — a complaint to a regulator, a letter from that regulator to the platform, a move toward a lawyer — temporal proximity does the work a confession never will. Hours and days are, in the retaliation doctrine, almost the strongest indicator available. Add the absence of any alternative explanation — no violation on the author’s side in the period before — and the presumption of a link hardens.

This is not proof of revenge. It is strong circumstantial evidence. The doctrine has never required a confession; it was built precisely because confessions do not exist.

A retaliatory ban is a separate tort. A separate claim. Section 230 does not extend to it.

And — more important in the context of this series — it shows the hole in the wall from a different side than Anderson. Anderson breaches Section 230 from the side of the algorithm. Retaliation breaches it from the side of motive.

Two different breaches. They do not duplicate each other.

Where this hole is not yet formed

An honest assessment.

No public decision of the Supreme Court or a federal appellate court has yet formulated a “retaliatory ban” doctrine for platforms directly. This is a forming area.

Proving retaliation requires protected activity — an act by the author that falls under protection. If an author simply publishes posts the platform dislikes and gets banned — that is not retaliation. That is moderation. For it to become retaliation, there must be an external appeal: to a regulator, a lawyer, the press, the authorities.

Not every ban case has this. Most do not.

But those that do — also have this hole.

What to do if you write on the platform right now

First. If you plan to complain to regulators — record the date of the complaint. The exact time of filing. Keep the confirmation of receipt from the regulator. This will be the time marker from which temporal proximity is counted.

Second. Document everything that happens to your account after the complaint. Reduced visibility, disappearance from Recommendations, deleted comments, bans. With dates. With screenshots. This is material for proving a pattern.

Third. Do not write to the platform “I filed a complaint with a regulator.” That hands the platform a formal trigger. The platform can use your own message as grounds for a ban with a formal reason. Better — let the regulator notify the platform within its own process. And keep the confirmation of that notification separately.

Fourth. Do not sign agreements to withdraw complaints. Sometimes platforms offer to restore an account in exchange for withdrawing a regulator complaint. That is the platform’s instrument. Documented retaliation is worth more than a restored account.

What this part shows

The second hole in the wall of 1996. Of a fundamentally different nature than the first.

The first hole — Anderson v. TikTok — breaches Section 230 at the point of “the platform’s algorithmic choice.” That is a structural attack on the immunity.

The second hole — retaliation — breaches Section 230 at the point of “a motive lying outside the realm of moderation.” That is an attack not on the structure but on a specific act.

They add up. An author who has both evidence of the platform’s algorithmic decision and evidence of retaliation can build two independent claims. Each with its own logic. Each with its own precedents.

And neither of them is closed by Section 230.

Five holes remain. The next — the seizure of the brand. When the platform holds the author’s name hostage after the ban.

— Lintara

Next: The Seizure of the Brand. The handle, released by the platform after a ban, stays in its possession. The author’s name — under which they hold subscribers, an archive, recommendation ties — passes into the platform’s ownership. The doctrine of conversion of intangible property, and why this is a separate claim.

Subscribe to the newsletter →