DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed7 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedplayhigh sensitivity
Merged incident · 7 filings

Alcott HR — February 2025 breach

Clustered 7 filings across 7 jurisdictions · filing window Feb 25, 2025 → Jun 23, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

6

Affected · reported

76,098

First → last filing

Feb 25, 2025 → Jun 23, 2026

Merge confidence

100%

incident inc_3410bd8a15ea4cd8 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 unverified claim. The filing describes unauthorized access. Intrusion Feb 12, 2025, discovered Feb 1, 2025 — the first regulatory filing landed 501 days later (flagged late). 76,098 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 2 more. Notifications rolled out on a 482-day schedule across 6 filings beginning Feb 25, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
501days

Discovered → first regulatory filing

Discovery variance
11days

Range of discovered_at dates across filings

Leak precedence
476days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
482days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dCalifornia✗ CA 60-day late · 488dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 12, 2025breach begins
Feb 1, 2025discovered · members disagree
notification delay · 501 days
Jun 17, 2026first filing
Jun 23, 2026most 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. FEB 25Leak siteplay postfirst filing · attacker claim · unverifiedday 0
  2. JUN 17VT AGVT AG notice28 VT residents+476d
  3. JUN 17IN AGIN AG noticestates nationwide total 76,098+476d
  4. JUN 17CA AGCA AG noticeno count stated+476d
  5. JUN 17NE AGNE AG notice54 NE residents+476d
  6. JUN 22NH AGNH AG notice128 NH residents+481d
  7. JUN 23MA AGMA AG noticemost recent · no count stated+482d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 12, 2025
IN AG
Discovered
Feb 1, 2025NE AG + NH AGFeb 12, 2025CA AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI
VT AG + CA AG + NE AG +2
Attack vector
Unauthorized Access
NE 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)

76,098

Sum of filed state slices

377· 0.5% of stated

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

US76,098
IN167
NH128
NE54
VT28

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing6 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

482 days

Cadence

~1 / 80.3d

vs. multi-state median

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