LEMONADE, INC. — April 2023 breach

Clustered 16 filings across 11 jurisdictions · filing window Apr 1, 2025 → Jun 17, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

16 filings

States

Affected · reported

190,279

First → last filing

Apr 1, 2025 → Jun 17, 2025

Merge confidence

100%

incident inc_89936e1e2deb42b0 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 16 regulatory filings. Intrusion Apr 1, 2023–Apr 8, 2025, discovered Sep 18, 2024 — the first regulatory filing landed 195 days later. 190,279 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 77-day schedule across 16 filings beginning Apr 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

195days

Discovered → first regulatory filing

Discovery variance

202days

Range of discovered_at dates across filings

Filing span

77days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksSouth Carolina✓ SC CRA notice dueTexas✓ TX AG ≤30dIowa✓ IA AG ≤5 bdayOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.