DisclosureLens
State AGConfirmed5 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 5 filings

American Family Mutual Insurance Company, S.I. — February 2021 breach

Clustered 5 filings across 5 jurisdictions · filing window Jan 1, 2021 May 13, 2021. View entity profile → Other incidents for this victim →

affected count, data types, discovery date agreeMerge100%

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

283,734

First → last filing

Jan 1, 2021 May 13, 2021

Merge confidence

100%

incident inc_20fd485cc4b54827 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe unauthorized access. Intrusion Feb 6, 2021–Mar 19, 2021, discovered Mar 18, 2021. 283,734 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 132-day schedule across 5 filings beginning Jan 1, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
132days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksWashington WA AG >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 6, 2021breach begins
Mar 18, 2021discovered
Jan 1, 2021first filing
May 13, 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. MAY 11NH AGNH AG noticestates nationwide total 283,734+130d
  3. MAY 13CA AGCA AG noticeno count stated+132d
  4. MAY 13IN AGIN AG noticestates nationwide total 283,734+132d
  5. MAY 13WA AGWA AG noticemost recent · states nationwide total 283,734+132d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 6, 2021Mar 7, 2021
NH AG
Discovered
Mar 18, 2021· 40d undetected
IL AG + NH AG + WA AG
Data types
Identity (basic) · Government ID
NH AG + CA AG + WA AG
Attack vector
Unauthorized Access
NH 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)

283,734

Sum of filed state slices

9,469· 3.3% of stated

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

US283,734
WA5,246
IN4,137
NH86

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

132 days

Cadence

~1 / 33d

vs. multi-state median

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