Manhattan School of Music reported a data breach to the Montana Attorney General. The breach was reported on 2022-02-18. The breach occurred from 4/17/2021 to 6/17/2021. 3 Montana residents were affected.
Affected (this filing): 3
Clustered 2 filings across 2 jurisdictions · filed Feb 18, 2022. View entity profile → Other incidents for this victim →
incident inc_722ff47da14d4f2f · merge_method human · 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 17, 2021
When the intrusion reportedly occurred, per the linked filings
Nov 23, 2021
Reported by MAINE AG filing
Manhattan School of Music reported a data breach to the Montana Attorney General. The breach was reported on 2022-02-18. The breach occurred from 4/17/2021 to 6/17/2021. 3 Montana residents were affected.
Affected (this filing): 3
Manhattan School of Music experienced a data breach where an external actor gained unauthorized access to its systems between April 17, 2021, and June 17, 2021. The breach was discovered on November 23, 2021. The compromised information included names and Social Security numbers of approximately 6,500 individuals. Affected parties were notified on February 18, 2022, and offered one year of credit monitoring and identity theft restoration services.
Affected (this filing): 6,500
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.