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

Town of Amherst, NY — February 2026 breach

Clustered 3 filings across 3 jurisdictions · filing window Apr 1, 2026 → Apr 6, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

3 filings

States

3

Affected · reported

270

First → last filing

Apr 1, 2026 → Apr 6, 2026

Merge confidence

100%

incident inc_a46bb094711f4b50 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filing describes unauthorized access. Intrusion Feb 3, 2026, discovered Feb 3, 2026 — the first regulatory filing landed 57 days later. 270 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 5-day schedule across 3 filings beginning Apr 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
57days

Discovered → first regulatory filing

Discovery variance
34days

Range of discovered_at dates across filings

Filing span
5days

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 clocksMassachusetts⏱ MA AG >30dMaine✓ ME AG ≤30d · 23dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 3, 2026breach begins
Feb 3, 2026discovered · members disagree
notification delay · 57 days
Apr 1, 2026first filing
Apr 6, 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. APR 1MA AGMA AG noticefirst filing · no count statedday 0
  2. APR 1ME AGME AG noticestates nationwide total 270day 0
  3. APR 6NH AGNH AG noticemost recent · 260 NH residents+5d
  4. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 3, 2026
ME AG
Discovered
Feb 3, 2026MA AG + NH AGMar 9, 2026ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID
MA AG + ME AG + NH AG
Attack vector
Unauthorized Access
ME 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)

270

Sum of filed state slices

261· 96.7% of stated

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

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

5 days

Cadence

~1 / 2.5d

vs. multi-state median

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