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

Hinsdale New Hampshire School District/ SAU 92 — November 2023 breach

Clustered 4 filings across 3 jurisdictions · filing window Jun 3, 2024 → Jul 16, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

4 filings

States

3

Affected · reported

not comparable

First → last filing

Jun 3, 2024 → Jul 16, 2024

Merge confidence

100%

incident inc_0cd2b15bef4d4194 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe unauthorized access. Intrusion Nov 2, 2023–Dec 7, 2023, discovered May 6, 2024 — the first regulatory filing landed 28 days later. Data reported: Government ID, Health (basic), Identity (basic), and 2 more. Notifications rolled out on a 43-day schedule across 4 filings beginning Jun 3, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
28days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
43days

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 credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 2, 2023breach begins
May 6, 2024discovered
notification delay · 28 days
Jun 3, 2024first filing
Jul 16, 2024most 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 3MA AGMA AG noticefirst filing · 67 MA residentsday 0
  2. JUN 6NH AGNH AG notice89 NH residents+3d
  3. JUL 11MT AGMT AG notice1 MT residents+38d
  4. JUL 16NH AGNH AG noticemost recent · 647 NH residents+43d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 2, 2023 – Dec 7, 2023
NH AG
Discovered
May 6, 2024· 186d undetected
NH AG
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
MA AG + NH AG + MT AG
Attack vector
Unauthorized Access
NH 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

NH647
MA67
MT1

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

43 days

Cadence

~1 / 14.3d

vs. multi-state median

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