DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
HHS OCRState AGConfirmed27 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 27 filings

Alera Group, Inc. — July 2024 breach

Clustered 27 filings across 11 jurisdictions · filing window May 21, 2025 → Dec 18, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

27 filings

States

11

Affected · reported

174,378

First → last dated filing

May 21, 2025 → Dec 18, 2025

Merge confidence

100%

incident inc_42263a9613d044f2 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 27 regulatory filings. The filings describe unauthorized access. Intrusion Jul 19, 2024–Aug 4, 2025, discovered Aug 1, 2024 — the first regulatory filing landed 293 days later (flagged late); 6 later filings were also flagged late. 174,378 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 3 more. Notifications rolled out on a 211-day schedule across 26 dated filings beginning May 21, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
293days

Discovered → first regulatory filing

Discovery variance
270days

Range of discovered_at dates across filings

Filing span
211days

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 · 293dTexas✗ TX AG >30dOregon✗ OR AG >45dMaine⏱ ME AG >30d · 293dDate basis✓ Clock withheld · confirmation dateHIPAA✓ HHS notifiedIowa✓ IA AG ≤5 bdaySouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 19, 2024breach begins
Aug 1, 2024discovered · members disagree
notification delay · 293 days
May 21, 2025first dated filing
Dec 18, 2025most 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. MAY 21NH AGNH AG noticefirst filing · 150 NH residentsday 0
  2. MAY 21ME AGME AG noticestates nationwide total 10,874day 0
  3. MAY 21CA AGCA AG noticeno count statedday 0
  4. MAY 21MT AGMT AG notice22 MT residentsday 0
  5. MAY 21OR AGOR AG noticestates nationwide total 10,874day 0
  6. MAY 21IN AGIN AG noticestates nationwide total 10,874day 0
  7. JUN 13ME AGME AG notice2 ME residents+23d
  8. JUN 13CA AGCA AG noticeno count stated+23d
  9. JUL 29HHS OCRHHS OCR noticestates nationwide total 155,567+69d
  10. JUL 29DE AGDE AG noticeno count stated+69d
  11. JUL 29MT AGMT AG notice829 MT residents+69d
  12. JUL 29NH AGNH AG notice8,343 NH residents+69d
  13. JUL 29HHS OCRHHS OCR noticestates nationwide total 174,378+69d
  14. JUL 29CA AGCA AG noticeno count stated+69d
  15. JUL 29ME AGME AG notice1,845 ME residents+69d
  16. JUL 29IA AGIA AG notice8,014 IA residents+69d
  17. JUL 30SC AGSC AG notice8,113 SC residents+70d
  18. AUG 1IL AGIL AG noticefiling day not on record · no count stated—
  19. AUG 28CA AGCA AG noticeno count stated+99d
  20. AUG 28NH AGNH AG notice101 NH residents+99d
  21. AUG 28ME AGME AG notice169 ME residents+99d
  22. SEP 5NH AGNH AG notice1 NH residents+107d
  23. SEP 5ME AGME AG notice1 ME residents+107d
  24. SEP 29ME AGME AG notice4 ME residents+131d
  25. OCT 24TX AGTX AG notice105,555 TX residents+156d
  26. NOV 7CA AGCA AG noticeno count stated+170d
  27. DEC 18OR AGOR AG noticemost recent · states nationwide total 18,159+211d
  28. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 19, 2024 – Aug 4, 2024
NH AG
Discovered
Aug 1, 2024NH AG + ME AG + CA AG +3Aug 4, 2024SC AGAug 14, 2024IL AGApr 28, 2025OR AG + ME AG + TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
NH AG + CA AG + MT AG +7
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)

174,378

Sum of filed state slices

137,509· 78.9% of stated

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

US174,378
TX105,555
NH8,343
SC8,113
IA8,014
IN4,810
ME1,845
MT829

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 filing27 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 22, 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

211 days

Cadence

~1 / 8.4d

vs. multi-state median

35.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.