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

ARTHUR J. GALLAGHER & CO. — June 2020 breach

Clustered 30 filings across 6 jurisdictions · filing window Jun 30, 2021 → Oct 4, 2021. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

30 filings

States

6

Affected · reported

not comparable

First → last filing

Jun 30, 2021 → Oct 4, 2021

Merge confidence

100%

incident inc_ba33c28c2f334065 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 30 regulatory filings. Intrusion Jun 3, 2020–Sep 26, 2020, discovered Sep 26, 2020 — the first regulatory filing landed 277 days later (flagged late). Data reported: Government ID, Biometric, PII, and 7 more. Notifications rolled out on a 96-day schedule across 30 filings beginning Jun 30, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
277days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
96days

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 clocksCalifornia✗ CA 60-day late · 277dWashington✗ WA AG >90dHawaii✓ HI CRA notice dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

authenticationbiometricidentity_government

Incident timeline

Jun 3, 2020breach begins
Sep 26, 2020discovered
notification delay · 277 days
Jun 30, 2021first filing
Oct 4, 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. JUN 30DE AGDE AG noticefirst filing · no count statedday 0
  2. JUN 30CA AGCA AG noticeno count statedday 0
  3. JUL 6NH AGNH AG notice13 NH residents+6d
  4. JUL 8HI AGHI AG notice2,345 HI residents+8d
  5. JUL 9DE AGDE AG noticeno count stated+9d
  6. JUL 12DE AGDE AG noticeno count stated+12d
  7. JUL 13WA AGWA AG notice72,378 WA residents+13d
  8. JUL 15NH AGNH AG noticeno count stated+15d
  9. JUL 16DE AGDE AG noticeno count stated+16d
  10. JUL 19SC AGSC AG notice14,638 SC residents+19d
  11. JUL 21DE AGDE AG noticeno count stated+21d
  12. JUL 21SC AGSC AG notice1,348 SC residents+21d
  13. JUL 22NH AGNH AG notice157 NH residents+22d
  14. JUL 26NH AGNH AG notice604 NH residents+26d
  15. AUG 4NH AGNH AG notice4 NH residents+35d
  16. AUG 4SC AGSC AG notice11 SC residents+35d
  17. AUG 4DE AGDE AG noticeno count stated+35d
  18. AUG 12DE AGDE AG noticeno count stated+43d
  19. AUG 16NH AGNH AG notice1,189 NH residents+47d
  20. AUG 17DE AGDE AG noticeno count stated+48d
  21. AUG 17SC AGSC AG notice57 SC residents+48d
  22. AUG 17SC AGSC AG notice379 SC residents+48d
  23. AUG 17SC AGSC AG notice950 SC residents+48d
  24. AUG 19DE AGDE AG noticeno count stated+50d
  25. AUG 23NH AGNH AG notice1,222 NH residents+54d
  26. SEP 7NH AGNH AG notice690 NH residents+69d
  27. SEP 8SC AGSC AG notice6 SC residents+70d
  28. SEP 13NH AGNH AG notice2 NH residents+75d
  29. SEP 30SC AGSC AG notice1 SC residents+92d
  30. OCT 4NH AGNH AG noticemost recent · 511 NH residents+96d
  31. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 3, 2020 – Sep 26, 2020
DE AG
Discovered
Sep 26, 2020· 115d undetected
DE AG + CA AG + NH AG +3
Data types
Authentication · Biometric · Credentials · Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
DE AG + HI AG + WA AG +3
Attack vector
Ransomware
DE AG

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

Affected residents by state

per-state reported counts

WA72,378
SC14,638
HI2,345
NH1,222

State AGs report only their own residents; teal bars show each state's reported slice.

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

96 days

Cadence

~1 / 3.3d

vs. multi-state median

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