A federal judge in Texas has thrown out a class-action lawsuit that could have set a major precedent for how “revenge porn” laws apply to paid subscription content — and the reasoning behind the dismissal is worth understanding if you sell content online for a living.
The case, brought by an anonymous OnlyFans creator against X Corp and filed as a proposed class action, alleged that the platform violated the federal revenge porn statute by allowing a third party to repost the creator’s paid subscription content without permission. On 27 February 2026, Chief Judge Reed O’Connor of the US District Court for the Northern District of Texas dismissed the case with prejudice, meaning it cannot be refiled.
What the lawsuit actually alleged
The creator argued that content originally sold behind a paywall had been reposted on X without consent, and that this amounted to a violation of the federal law commonly known as the “revenge porn” statute — legislation designed to give victims of non-consensual intimate image sharing a route to compensation and takedown.
Why the case was dismissed — the “commercial content” gap
The court’s reasoning is the part that should concern anyone monetising adult content online. Judge O’Connor found that the federal revenge porn law is built to protect private content — material never intended for distribution — rather than content that was deliberately created and sold for profit. Because the creator’s content was produced and marketed commercially, the judge ruled it fell outside the statute’s scope, unless it could be shown the content was obtained through “force, fraud, misrepresentation, or coercion.” The court rejected the argument that unauthorised reposting alone met that bar.
In other words: the law many creators assume protects them from leaks was, in this instance, found not to apply at all to commercially sold material — a legal gap that predates OnlyFans-style platforms and hasn’t caught up with them.
Section 230 did the rest
Even where the creator tried a different legal angle, the case ran into Section 230 of the Communications Decency Act, which broadly shields platforms from liability for content posted by their users. The court also rejected an intellectual-property argument, noting that the underlying statute is concerned with privacy harm, not content ownership — so copyright-style claims didn’t fit either.
What this actually means for your content
This ruling doesn’t mean creators have no options when their paid content is leaked or reposted without consent — it means the specific “revenge porn” statute is the wrong tool for commercially sold material in this circuit. Copyright law, platform reporting tools, and contractual terms of service are generally the stronger levers. Practically, that means:
- Register your content’s copyright where practical, or at minimum keep dated, timestamped originals so ownership is easy to prove.
- Use a DMCA takedown notice rather than relying on privacy statutes — it doesn’t require proving the content was “private,” only that you own it and didn’t authorise the repost.
- Watermark previews and paywalled previews consistently, so leaked clips are traceable back to your account.
- Report reposts directly through the platform’s own non-consensual content tools as well as via legal notice — platform-level removal is often faster than litigation.
- Keep records of every leak and takedown request — a pattern of documented incidents strengthens any future legal or platform escalation.
If you’re dealing with a live leak situation, our guide to sending a DMCA takedown notice walks through the actual process, and our piece on what’s real and what’s not in OnlyFans leak panic covers how to tell a genuine breach from noise. One creator’s experience dealing with impersonation and stolen content is also covered in our piece on catfish accounts trading on a real creator’s identity.
This article is provided for general information only and does not constitute legal advice. Laws around image rights, privacy, and content ownership vary by jurisdiction and change frequently — if you’re dealing with a leak, impersonation, or a potential legal claim, consult a qualified attorney in your jurisdiction.
