Rockwood School District reported a data breach to the Montana Attorney General. The breach was reported on 2021-08-19. The breach occurred from 4/20/2021 to 6/24/2021. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Aug 19, 2021. View entity profile → Other incidents for this victim →
incident inc_800b05f9862c485d · 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
Apr 20, 2021
When the intrusion reportedly occurred, per the linked filings
Jun 17, 2021
Reported by MAINE AG filing
Rockwood School District reported a data breach to the Montana Attorney General. The breach was reported on 2021-08-19. The breach occurred from 4/20/2021 to 6/24/2021. 1 Montana residents were affected.
Affected (this filing): 1
Rockwood School District, an educational organization, experienced an external system breach through hacking between April 20, 2021, and June 24, 2021. The breach was discovered on June 17, 2021, and affected 77,294 individuals. The compromised information included names and financial account numbers or credit/debit card numbers along with their security codes or PINs. Affected individuals were notified in writing on August 19, 2021, and offered 12 months of identity monitoring and restoration services from Kroll.
Affected (this filing): 77,294
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.