DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed41 filings · 12 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcritical sensitivity
Merged incident · 41 filings

ARTHUR J. GALLAGHER & CO. — June 2020 breach

Clustered 41 filings across 12 jurisdictions · filing window Jun 30, 2021 → Dec 10, 2021 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

41 filings

States

12

Affected · reported

1,140,520

First → last dated filing

Jun 30, 2021 → Dec 10, 2021

Merge confidence

100%

incident inc_dda5ac5b5d5848e6 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 41 regulatory filings. Intrusion Jun 3, 2020–Sep 26, 2020, discovered Sep 26, 2020. 1,140,520 individuals reported across the linked filings. Data reported: Government ID, Biometric, Identity (basic), and 8 more. Notifications rolled out on a 163-day schedule across 38 dated filings beginning Jun 30, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
270days

Range of discovered_at dates across filings

Filing span
163days

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 >90dMaine⏱ ME AG >30d · 42dMassachusetts✓ MA credit monitoring dueHawaii✓ HI CRA notice dueOregon✓ OR AG ≤45dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

authenticationbiometricfinancial_credentialsidentity_government

Incident timeline

Jun 3, 2020breach begins
Sep 26, 2020discovered · members disagree
Jun 30, 2021first dated filing
Dec 10, 2021most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  3. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  4. JUN 30CA AGCA AG noticefirst filing · no count statedday 0
  5. JUN 30ME AGME AG noticestates nationwide total 7,376day 0
  6. JUN 30IN AGIN AG noticestates nationwide total 27,856day 0
  7. JUN 30DE AGDE AG noticeno count statedday 0
  8. JUN 30MA AGMA AG notice19,164 MA residentsday 0
  9. JUL 6NH AGNH AG notice13 NH residents+6d
  10. JUL 8HI AGHI AG notice2,345 HI residents+8d
  11. JUL 8OR AGOR AG noticestates nationwide total 90,240+8d
  12. JUL 9MT AGMT AG notice372 MT residents+9d
  13. JUL 12DE AGDE AG noticeno count stated+12d
  14. JUL 13WA AGWA AG notice72,378 WA residents+13d
  15. JUL 15NH AGNH AG noticeno count stated+15d
  16. JUL 16DE AGDE AG noticeno count stated+16d
  17. JUL 16ME AGME AG noticestates nationwide total 212,721+16d
  18. JUL 19SC AGSC AG notice14,638 SC residents+19d
  19. JUL 21DE AGDE AG noticeno count stated+21d
  20. JUL 21ME AGME AG noticestates nationwide total 722,325+21d
  21. JUL 21MT AGMT AG notice1,770 MT residents+21d
  22. JUL 22NH AGNH AG notice157 NH residents+22d
  23. JUL 26NH AGNH AG notice604 NH residents+26d
  24. AUG 4DE AGDE AG noticeno count stated+35d
  25. AUG 4NH AGNH AG notice4 NH residents+35d
  26. AUG 4ME AGME AG noticestates nationwide total 6,823+35d
  27. AUG 12ME AGME AG noticestates nationwide total 584,048+43d
  28. AUG 12DE AGDE AG noticeno count stated+43d
  29. AUG 16NH AGNH AG notice1,189 NH residents+47d
  30. AUG 17DE AGDE AG noticeno count stated+48d
  31. AUG 17ME AGME AG noticestates nationwide total 1,140,520+48d
  32. AUG 19DE AGDE AG noticeno count stated+50d
  33. AUG 23NH AGNH AG notice1,222 NH residents+54d
  34. SEP 1ME AGME AG noticestates nationwide total 111,317+63d
  35. SEP 7NH AGNH AG notice690 NH residents+69d
  36. SEP 8ME AGME AG noticestates nationwide total 5,577+70d
  37. SEP 13ME AGME AG noticestates nationwide total 104,526+75d
  38. SEP 29ME AGME AG noticestates nationwide total 813,120+91d
  39. OCT 4NH AGNH AG notice511 NH residents+96d
  40. DEC 6ME AGME AG noticestates nationwide total 281+159d
  41. DEC 10NH AGNH AG noticemost recent · 1 NH residents+163d
  42. 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
CA AG
Discovered
Sep 26, 2020IL AG + CA AG + DE AG +5Jun 23, 2021ME AG + OR AGfilings disagree on discovery
Data types
Authentication · Biometric · Credentials · Employment · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI · PII
CA AG + DE AG + MA AG +6
Attack vector
Ransomware
CA 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)

1,140,520

Sum of filed state slices

138,706· 12.2% of stated

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

US1,140,520
WA72,378
IN26,307
MA19,164
SC14,638
HI2,345
MT1,770
NH1,222
ME882

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 filing41 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 29, 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

163 days

Cadence

~1 / 4.4d

vs. multi-state median

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