DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed16 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 16 filings

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

11

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

Sensitive data

identity_government

Incident timeline

Apr 1, 2023breach begins
Sep 18, 2024discovered · members disagree
notification delay · 195 days
Apr 1, 2025first filing
Jun 17, 2025most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. APR 1IL AGIL AG noticefirst filing · no count statedday 0
  2. APR 10IN AGIN AG noticestates nationwide total 190,279+9d
  3. APR 10DE AGDE AG noticeno count stated+9d
  4. APR 10NE AGNE AG noticeno count stated+9d
  5. APR 11SC AGSC AG notice1,950 SC residents+10d
  6. APR 11TX AGTX AG noticestates nationwide total 190,000+10d
  7. APR 11IA AGIA AG notice750 IA residents+10d
  8. APR 11CA AGCA AG noticeno count stated+10d
  9. APR 11OR AGOR AG noticestates nationwide total 190,000+10d
  10. APR 12MA AGMA AG notice32,801 MA residents+11d
  11. APR 14RI AGRI AG notice2,300 RI residents+13d
  12. JUN 12CA AGCA AG noticeno count stated+72d
  13. JUN 13NE AGNE AG noticeno count stated+73d
  14. JUN 13DE AGDE AG noticeno count stated+73d
  15. JUN 17TX AGTX AG noticestates nationwide total 279+77d
  16. JUN 17RI AGRI AG noticemost recent · 2,313 RI residents+77d
  17. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 1, 2023
IN AG
Discovered
Sep 18, 2024IA AG + RI AGMar 14, 2025IL AG + NE AG + TX AG +2Apr 8, 2025DE AG + SC AG + CA AG +3filings disagree on discovery
Data types
Identity (basic) · Government ID · PII
IL AG + DE AG + NE AG +6
Attack vector
Unauthorized Access
DE AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

190,279

Sum of filed state slices

57,238· 30.1% of stated

70% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US190,279
MA32,801
TX17,563
RI2,313
SC1,950
IN1,861
IA750

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing16 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-confirmed · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

77 days

Cadence

~1 / 5.1d

vs. multi-state median

9.6× slower

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

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.