Roblox Child Safety lawsuit update

Verified snapshot

The facts that anchor this dossier

A trauma-informed, allegation-versus-fact account of the new Roblox child sexual exploitation MDL, the platform's changing safety controls, and what families can learn without exposing minors or turning an unfinished case into a verdict.

Federal proceeding

MDL 3166

Northern District of California before Chief Judge Richard Seeborg.

Pending federal actions

170

JPML count as of July 1, 2026; early-docket counts can move quickly.

Cases at creation

31 actions

The JPML also reported 48 related actions when it centralized the litigation in December 2025.

Claims at issue

Exploitation and assault allegations

Plaintiffs allege predators used Roblox to target or groom minors and sometimes moved communication to other platforms.

Platform scale

127 million average DAUs

Roblox's 2025 Form 10-K figure; scale provides context, not an incident rate.

Documented chronology

How the litigation reached this point

What families should understand about the allegations

The transfer order describes plaintiffs' allegations with unusual specificity. They say predators targeted and groomed minors through Roblox and, after making contact, sometimes persuaded them to continue on Discord, Snapchat, Instagram, text, or video calls, where explicit-image exchanges or in-person assault allegedly occurred. Plaintiffs assert negligence, failure-to-warn, design-defect, and misrepresentation theories. Roblox, Discord, Snap, and Meta opposed centralization; opposing an MDL or disputing claims is not an admission.

Centralization means one judge can manage overlapping discovery and legal questions. It does not establish that the alleged events occurred in every case, that a platform legally caused a third party's crime, or that every child who had an unsafe interaction has the same claim. The court will have to separate platform-wide questions from age, settings, communications, off-platform conduct, notice, and injury evidence specific to each action.

Why platform scale matters—but cannot become a risk rate

Roblox reported 127 million average daily active users in 2025 across more than 180 countries and 123.9 billion hours of engagement for the year. Its filing also acknowledges that a large number of daily users have historically been under 13 and describes regulatory and safety risks. These are company-reported metrics filed with the SEC. They show the scale at which safety systems must operate, but they do not reveal the percentage of children who experienced grooming, exploitation, or any other specific harm.

The same caution applies to CyberTipline figures. NCMEC says its CyberTipline received 20.5 million reports covering 29.2 million incidents in 2024 across providers. Roblox separately said it made 13,316 reports in 2023 and used a lower reporting threshold. Reports can contain suspected material or conduct and may be bundled, duplicated, or later assessed differently. They should never be presented as confirmed crimes, confirmed victims, or a platform-specific prevalence rate without denominator and validation data.

Safety controls have changed during the litigation period

Roblox's own announcements document a moving product baseline. In July 2025 it introduced age estimation and Trusted Connections, with additional controls for teen-to-adult connections. Later it expanded facial age checks for chat. In June 2026 it announced worldwide Kids accounts for ages 5–8 and Select accounts for ages 9–15, age-based content and communication defaults, and chat restrictions for users who had not completed an age check. Company descriptions are primary evidence of what Roblox says it deployed; they are not an independent audit of effectiveness.

This chronology may matter because a case involving older settings cannot automatically be evaluated using today's controls. The JPML identified common questions about whether Roblox had the means to implement effective parental controls and age or identity verification, what it knew, and what it represented about safety. Discovery, not marketing language alone, will test those disputed questions.

Privacy is part of the court process, not an afterthought

The MDL court entered early orders addressing pseudonyms and guardians ad litem. That is significant in cases involving minors and alleged sexual harm: public access must be balanced against a child's privacy and the legal requirement that a minor act through an appropriate representative. Families should not post screenshots, names, account handles, intimate images, or identifying details publicly to prove an allegation or attract attention.

Preservation can be quiet and controlled. Relevant material may include account identifiers, dates, parental-control settings, reports made to a platform, law-enforcement report numbers, device records, and communications that remain lawfully accessible. Suspected child sexual abuse material should not be downloaded, copied, or redistributed. NCMEC's CyberTipline and local law enforcement provide reporting channels; immediate danger belongs with emergency services.

What the docket can—and cannot—tell us now

MDL 3166 is young. The jump from 31 actions at centralization to 170 pending actions in July 2026 shows growth, not a merits trend. Early orders largely establish leadership, direct filing, confidentiality-sensitive procedures, and how minors may proceed. Future motions may test platform immunity arguments, causation, duties, design theories, and the relevance of off-platform conduct, but no responsible update should predict those rulings before they exist.

There is no public official payout schedule in the cited materials, and docket growth does not create one. Civil remedies also do not replace safeguarding, medical care, trauma-informed counseling, or criminal reporting. A child's wellbeing should not depend on whether a federal civil claim ultimately survives. This page therefore tracks verified court and company documents without rating individual legal eligibility or putting a monetary label on trauma.

Reader questions

Frequently asked questions