DisclosureLens
State AGConfirmed5 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Merged incident · 5 filings

Berkshire Farm Center and Services for Youth — July 2022 breach

Clustered 5 filings across 5 jurisdictions · filing window Feb 28, 2023 Mar 6, 2023. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

6,451

First → last filing

Feb 28, 2023 Mar 6, 2023

Merge confidence

100%

incident inc_d0806a351b2648a4 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe unauthorized access. Intrusion Jul 14, 2022, discovered Jul 15, 2022 — the first regulatory filing landed 228 days later (flagged late). 6,451 individuals reported across the linked filings. Data reported: Identity (basic) and Financial account. Notifications rolled out on a 6-day schedule across 5 filings beginning Feb 28, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
228days

Discovered → first regulatory filing

Discovery variance
200days

Range of discovered_at dates across filings

Filing span
6days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delayno leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksVermont VT AG >45 bdayMaine ME AG ≤30d · 28dFull clock table in Litigation Timeline

Incident timeline

Jul 14, 2022breach begins
Jul 15, 2022discovered · members disagree
notification delay · 228 days
Feb 28, 2023first filing
Mar 6, 2023most 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 28IN AGIN AG noticefirst filing · states nationwide total 6,451day 0
  2. FEB 28ME AGME AG noticestates nationwide total 6,451day 0
  3. FEB 28VT AGVT AG noticeno count statedday 0
  4. FEB 28MA AGMA AG notice407 MA residentsday 0
  5. MAR 6NH AGNH AG noticemost recent · 1 NH residents+6d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 14, 2022
IN AG
Discovered
Jul 15, 2022VT AG + NH AGJan 31, 2023ME AGfilings disagree on discovery
Data types
Identity (basic) · Financial account
ME AG + VT AG + NH AG +1
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)

6,451

Sum of filed state slices

411· 6.4% of stated

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

US6,451
MA407
ME2
IN1
NH1

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

6 days

Cadence

~1 / 1.5d

vs. multi-state median

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