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

PROGRESSIVE CASUALTY INSURANCE COMPANY — May 2021 breach

Clustered 9 filings across 9 jurisdictions · filed Aug 1, 2023. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

347,100

First → last filing

Aug 1, 2023

Merge confidence

100%

incident inc_e492464835dd45ba · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. Intrusion May 1, 2021–May 19, 2023, discovered May 19, 2023 — the first regulatory filing landed 74 days later (flagged late). 347,100 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
74days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
0days

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 clocksOregon✗ OR AG >45dWashington⏱ WA AG >30dMaine⏱ ME AG >30d · 74dHawaii✓ HI CRA notice dueSouth Carolina✓ SC CRA notice dueMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 1, 2021breach begins
May 19, 2023discovered
notification delay · 74 days
Aug 1, 2023first filing
—watching for filings

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

Member cascade — every filing about this breach

  1. AUG 1WA AGWA AG noticefirst filing · 8,325 WA residentsday 0
  2. AUG 1HI AGHI AG notice1,044 HI residentsday 0
  3. AUG 1IN AGIN AG noticestates nationwide total 347,100day 0
  4. AUG 1DE AGDE AG noticeno count statedday 0
  5. AUG 1SC AGSC AG notice10,157 SC residentsday 0
  6. AUG 1ME AGME AG noticestates nationwide total 347,100day 0
  7. AUG 1CA AGCA AG noticeno count statedday 0
  8. AUG 1OR AGOR AG noticestates nationwide total 347,100day 0
  9. AUG 1MA AGMA AG noticemost recent · 400 MA residentsday 0
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 1, 2021 – May 18, 2023
WA AG
Discovered
May 19, 2023· 748d undetected
WA AG + HI AG + ME AG +2
Data types
Financial account · Identity (basic) · Government ID · PCI · PII
WA AG + HI AG + DE AG +4
Attack vector
Third-Party / Supply Chain
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)

347,100

Sum of filed state slices

29,611· 8.5% of stated

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

US347,100
SC10,157
WA8,325
IN7,955
ME1,730
HI1,044
MA400

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 filing9 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-reviewed Jun 12, 2026 · 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

0 days

Cadence

~1 / 0d

vs. multi-state median

20.0× faster

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.