Clustered 4 filings across 4 jurisdictions · filing window Mar 16, 2022 → Feb 24, 2023. View entity profile → Other incidents for this victim →
incident inc_e663f4a127ab4cce · merge_method human · confidence 100%
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
PII
ME MT VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
School District of Elmbrook reported a data breach to the Montana Attorney General. The breach was reported on 2022-03-16. The breach occurred from 8/23/2022 to 8/27/2022. 1 Montana residents were affected.
Affected (this filing): 1
Aug 23, 2022 → Aug 27, 2022
When the intrusion reportedly occurred, per the linked filings
Aug 30, 2022
Reported by MAINE AG filing
The School District of Elmbrook (Wisconsin) experienced an external system breach (hacking) between August 23 and 27, 2022. The incident compromised the names and Social Security Numbers of 4,356 individuals, including one Maine resident. The breach was discovered on August 30, 2022. The District provided written notification on September 23, 2022, and offered 12 months of Experian credit monitoring services to affected individuals.
Affected (this filing): 4,356
Jan 13, 2023
Reported by VERMONT AG filing
School District of Elmbrook notified consumers of unauthorized network access between Aug 23-27, 2022. Personal information was removed from the network. The district engaged external cybersecurity professionals and offers one year of Experian IdentityWorks credit monitoring.
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.