Reviewed by Survivor Rights Center · Updated 2026-10-21
Figures compiled from the state's court filing and reporting on the federal dismissal; see sources below.
Earlier this month, a federal judge in California threw out a proposed class action brought by two survivors who said images from their own childhood abuse kept circulating on the company's cloud storage storage service years later. The court found the claims were blocked by Section 230, the decades-old federal law that generally shields online platforms from liability for content their users upload rather than content the platform itself created. The dismissal was entered with prejudice, meaning that particular case cannot be refiled in the same form.
That was not the only legal action the company has been facing over how it handles known abuse material on its storage platform. Months before the federal dismissal, a state attorney general's office filed its own lawsuit making a related but legally distinct argument, and that case is still very much alive. The timing puts the two outcomes side by side and offers a useful, plain look at why one legal theory failed while a different one, built around the same underlying facts, is still standing.
West Virginia's attorney general filed suit in a county circuit court earlier this year, arguing that the company's handling of known child sexual abuse material on cloud storage amounted to a violation of the state's consumer protection law rather than the kind of user-content liability claim Section 230 typically bars. The complaint pointed to a large gap between how many suspected abuse-material reports the company filed with the national reporting center in a recent year compared with other major technology companies, arguing that gap reflected a choice not to build or use available detection tools rather than a lack of options.
The state is asking the court for statutory and punitive damages along with an order requiring the company to adopt more effective detection measures going forward. Because the claim is framed as a consumer protection and product-design issue brought by a government office, rather than a private class action over failing to remove user-posted content, it does not run into the identical legal wall that ended the federal case.
The company tried to shift the West Virginia case out of state court and into federal court, arguing that because it complies with federal reporting requirements tied to abuse-material detection, it was effectively acting under the direction of a federal officer and entitled to a federal venue. A federal court rejected that argument, finding that simply following an existing federal reporting duty does not turn a private company into an arm of the government for jurisdictional purposes.
That ruling sent the case back to state court, where it will proceed under state law rather than the federal framework that shaped the outcome of the dismissed class action. It is a technical-sounding ruling, but it matters in practice: it determines which court's rules, and which legal theories, will actually decide whether the company is held responsible.
The core lesson here is not that one legal outcome is more important than the other, but that a single dismissal does not automatically end every legal question tied to the same conduct. A private class action built on a theory that Section 230 blocks can lose in federal court while a government enforcement action built on a different legal theory, in a different court, keeps going. Survivors' attorneys in the dismissed case have said they are weighing an appeal and exploring whether some other legal framing might avoid the same Section 230 barrier.
None of this is legal advice for any individual survivor's own situation, and it does not change the separate, more familiar process of pursuing a civil claim against an individual abuser or an institution that enabled abuse. But it is a useful, current example of how platform-accountability litigation and state enforcement actions can run on separate, parallel tracks even when they both trace back to the same reported failure.
We strive to provide accurate, current reporting on news and related legal proceedings. However, articles may contain errors, omissions, or outdated information. Allegations are not established facts, and individuals accused of criminal offenses are presumed innocent unless proven guilty in a court of law.
If you identify an inaccuracy or would like to request a correction, revision, or update, please email info@survivorrightscenter.org with the article URL, the requested change, and any supporting documentation. We will review submissions and make corrections or updates as appropriate.
Some content may be distressing. Please use discretion when reading.
Reporting reflects information available at the time of publication. Cases may develop, and articles may be updated or corrected. To report an error, request an update, or raise a privacy concern, please contact our editorial team.
If you or someone else is in immediate danger, contact local emergency services.
Two separate cases, same underlying subject, different legal tracks. Here is a plain rundown of where each one stands.
No. A separate lawsuit brought by a state attorney general on different legal grounds is continuing in state court.
The dismissed case relied on a theory that a federal law shielding platforms from user-content claims blocked, while the ongoing case is framed as a state consumer protection claim.
No. Both cases concern a technology platform's handling of known abuse material, a separate legal question from a survivor's personal claim against an individual or an organization that enabled abuse.
It is possible. The state case here shows that a consumer protection framing can proceed even after a similar federal class action was dismissed, though outcomes would depend on each state's own laws.
This article is general educational information, not legal advice. Confirm specifics with a licensed attorney in your state; many offer a free first consultation. If you need support now, the RAINN hotline is 800-656-4673, 24/7.
Free to use. Tell us only what you’re comfortable sharing, and the team that runs this site can point you to support options. In crisis? Call RAINN at 800-656-4673, 24/7.
Thank you for reaching out. If you need help now, call RAINN at 800-656-4673, free and confidential, 24/7.