Bernards Township School District reported a data breach to the Montana Attorney General. The breach was reported on 2022-04-05. The breach occurred on 4/6/2021. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Apr 5, 2022 → Apr 6, 2022. View entity profile → Other incidents for this victim →
incident inc_78f2e5864469497b · merge_method llm · confidence 44%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Identity (basic) · Financial account
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 6, 2021
When the intrusion reportedly occurred, per the linked filings
Feb 11, 2022
Reported by MAINE AG filing
Bernards Township School District reported a data breach to the Montana Attorney General. The breach was reported on 2022-04-05. The breach occurred on 4/6/2021. 1 Montana residents were affected.
Affected (this filing): 1
The Bernards Township School District reported a data breach to the Maine Attorney General, indicating that an external system breach (hacking) occurred on April 6, 2021. The breach was discovered on February 11, 2022. The compromised information includes names or other personal identifiers in combination with financial account numbers or credit/debit card numbers and their security codes. One Maine resident was affected. The district provided written notification to affected individuals on April 5, 2022, and offered 12 months of identity theft protection services through Experian.
Affected (this filing): 1
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.