Community Psychiatric Clinic reported a data breach to the Montana Attorney General. The breach was reported on 2019-07-26. The breach occurred from 3/1/2019 to 5/29/2019. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Jul 26, 2019 → Jul 27, 2019. View entity profile → Other incidents for this victim →
incident inc_e9cec8f029ab4321 · 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.
MT WA
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 1, 2019
When the intrusion reportedly occurred, per the linked filings
Mar 12, 2019
Reported by WASHINGTON AG filing
Community Psychiatric Clinic reported a data breach to the Montana Attorney General. The breach was reported on 2019-07-26. The breach occurred from 3/1/2019 to 5/29/2019. 1 Montana residents were affected.
Affected (this filing): 1
Community Psychiatric Clinic, a health sector entity reported a other incident to the Washington Attorney General. The organization became aware of the incident on 2019-03-12 and filed notice on 2019-07-27. 6,600 Washington residents were affected. 137 days elapsed between awareness and notification. 0 days to identify the breach. 78 days to contain the breach.
Affected (this filing): 6,600
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.