Mascoutah School District 19 reported a data breach to the Montana Attorney General. The breach was reported on 2021-01-08. The breach occurred from 10/1/2020 to 10/8/2020. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Jan 8, 2021. View entity profile → Other incidents for this victim →
incident inc_9ec786e1acec4087 · merge_method deterministic · confidence 100%
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.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 1, 2020
When the intrusion reportedly occurred, per the linked filings
Dec 15, 2020
Reported by MAINE AG filing
Mascoutah School District 19 reported a data breach to the Montana Attorney General. The breach was reported on 2021-01-08. The breach occurred from 10/1/2020 to 10/8/2020. 1 Montana residents were affected.
Affected (this filing): 1
Mascoutah School District 19 experienced an external system breach between October 1, 2020, and October 8, 2020, discovered on December 15, 2020. The incident compromised names and financial account or credit/debit card information for 1,383 individuals. The district notified affected individuals on January 8, 2021, and offered two years of complimentary credit monitoring and identity restoration services through TransUnion.
Affected (this filing): 1,383
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.