Playhouse Square Foundation reported a data breach to the Montana Attorney General. The breach was reported on 2020-12-11. The breach occurred from 6/22/2020 to 6/29/2020. 2 Montana residents were affected.
Affected (this filing): 2
Clustered 2 filings across 2 jurisdictions · filing window Dec 11, 2020 → Dec 17, 2020. View entity profile → Other incidents for this victim →
incident inc_5e5e8a5cce1b47b4 · 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
Jun 22, 2020
When the intrusion reportedly occurred, per the linked filings
Dec 7, 2020
Reported by MAINE AG filing
Playhouse Square Foundation reported a data breach to the Montana Attorney General. The breach was reported on 2020-12-11. The breach occurred from 6/22/2020 to 6/29/2020. 2 Montana residents were affected.
Affected (this filing): 2
Playhouse Square Foundation, a non-profit organization, reported an external system breach (hacking) that occurred between June 22, 2020, and June 29, 2020. The breach was discovered on December 7, 2020. The compromised information included names and Social Security Numbers. One Maine resident was affected out of a total of 5,411 individuals. The foundation began notifying affected consumers on December 18, 2020, and offered 12 months of credit monitoring and identity protection services through IDX.
Affected (this filing): 1
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.