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

Infinity Insurance Company — December 2020 breach

Clustered 8 filings across 8 jurisdictions · filing window Jan 1, 2021 → Mar 17, 2021. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

5,724,732

First → last filing

Jan 1, 2021 → Mar 17, 2021

Merge confidence

100%

incident inc_9854dcdeba8e4f8e · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe unauthorized access. Intrusion Dec 1, 2020–Dec 31, 2020, discovered Dec 26, 2020 — the first regulatory filing landed 6 days later. 5,724,732 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 1 more. Notifications rolled out on a 75-day schedule across 8 filings beginning Jan 1, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
6days

Discovered → first regulatory filing

Discovery variance
54days

Range of discovered_at dates across filings

Filing span
75days

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 clocksWashington⏱ WA AG >30dOregon✓ OR AG ≤45dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 1, 2020breach begins
Dec 26, 2020discovered · members disagree
notification delay · 6 days
Jan 1, 2021first filing
Mar 17, 2021most 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. MAR 16OR AGOR AG noticestates nationwide total 5,724,732+74d
  3. MAR 16WA AGWA AG notice606 WA residents+74d
  4. MAR 16MA AGMA AG notice212 MA residents+74d
  5. MAR 16IN AGIN AG noticestates nationwide total 5,724,732+74d
  6. MAR 16CA AGCA AG noticeno count stated+74d
  7. MAR 17NH AGNH AG notice34 NH residents+75d
  8. MAR 17SC AGSC AG noticemost recent · 2,921 SC residents+75d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 14, 2020 – Dec 27, 2020
OR AG
Discovered
Dec 26, 2020IL AG + WA AG + CA AG +2Feb 18, 2021OR AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PII
WA AG + MA AG + NH AG +2
Attack vector
Unauthorized Access
WA 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)

5,724,732

Sum of filed state slices

4,487· 0.1% of stated

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

US5,724,732
SC2,921
IN714
WA606
MA212
NH34

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 filing8 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
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

75 days

Cadence

~1 / 10.7d

vs. multi-state median

9.4× 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.