Clark County School District reported a data breach to the Montana Attorney General. The breach was reported on 2020-09-08. The breach occurred from 8/25/2020 to 7/27/2020. 26 Montana residents were affected.
Affected (this filing): 26
Clustered 2 filings across 2 jurisdictions · filing window Sep 8, 2020 → Oct 16, 2020. View entity profile → Other incidents for this victim →
incident inc_adc7de6eb70c4048 · merge_method human · confidence 100%
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
Aug 25, 2020
When the intrusion reportedly occurred, per the linked filings
Clark County School District reported a data breach to the Montana Attorney General. The breach was reported on 2020-09-08. The breach occurred from 8/25/2020 to 7/27/2020. 26 Montana residents were affected.
Affected (this filing): 26
Sep 25, 2020
Reported by MAINE AG filing
The Clark County School District located in Las Vegas, Nevada reported a data breach to the Maine Attorney General. The breach was an external system breach (hacking) that occurred on August 25, 2020 and was discovered a month later on September 25, 2020. The breach affected 8 Maine residents, and the information acquired was their names in combination with their Social Security Numbers. The affected individuals were notified in writing on October 16, 2020 and were offered 12 months of credit monitoring and identity restoration services from TransUnion.
Affected (this filing): 8
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.