Baltimore's Lawsuit Accused DraftKings and FanDuel of Engineering Addiction, Not Just Enabling It

What happened

Baltimore filed suit against DraftKings and FanDuel in April 2025, alleging that both companies built systems designed to identify users showing signs of gambling disorder and then apply targeted pressure to keep them spending. The complaint did not describe a product malfunction or an accidental side effect. It described deliberate architecture.

At the center of the allegations is predictive modeling. According to the complaint, both platforms used machine-learning algorithms trained on extensive user data to identify bettors most likely to continue gambling even as it harmed them. That identification fed a pipeline of personalized promotions, push notifications timed to moments of vulnerability, and VIP programs that attached status and reward to continued play. The system was, by the city's account, calibrated to maximize user lifetime value, which in this context means extracting revenue from the people least positioned to walk away.

The VIP designation is worth examining separately. Loyalty programs are common in consumer products, but the complaint suggests that here VIP status functioned as amplification: it went disproportionately to heavy users, normalized high-frequency betting as aspirational, and made pulling back socially awkward. Combined with push notifications, the effect was a feedback loop in which the platform identified distress signals, responded with an incentive, and then used continued engagement to calibrate the next intervention.

Baltimore's standing as a plaintiff rests on public-health grounds. The city argued that harms from gambling disorder, including lost household income and downstream demand for social services, fell on its residents and therefore on its budget. That framing tries to give the city direct standing to sue over conduct it otherwise observed only through emergency rooms and caseworkers. Whether courts accept it will determine how much legal exposure sports betting platforms face beyond the individual bettors who might sue on their own behalf.

The accountability gap the suit points to is not unique to sports betting. Both companies know a great deal about which users are most vulnerable; the complaint alleges they used that knowledge to drive revenue rather than flag harm. There is no public-facing record of what their targeting systems actually do, which segments they prioritize, or what thresholds, if any, trigger a responsible exit rather than an upsell. A provable record of what a system did at the moment it acted on a specific user's behavioral profile would make claims like Baltimore's easier to verify and harder to deny.

Reported impact

Affected parties

Not publicly disclosed

Harm type

Not publicly disclosed

Scale

Not publicly disclosed

Financial impact

Not publicly disclosed

Regulatory action

Not publicly disclosed

Classification

Organization

Not publicly disclosed

AI system

Not publicly disclosed

Industry

Not publicly disclosed

Country

Not publicly disclosed

Provider

Not publicly disclosed

Incident type

Not publicly disclosed

Relevant governance controls

Governance control mapping is not available for this record.

• No controls mappedNot publicly disclosed

Control mapping is analytical. It does not state that any control would have prevented the incident.

Sources and evidence

This record was researched and written by the Index. The event is also catalogued in the following database, which is listed for cross-reference.