Sunshine Behavioral Health Group, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2020-01-21. The breach occurred from 9/4/2019 to 11/14/2019. 21 Montana residents were affected.
Affected (this filing): 21
Clustered 2 filings across 2 jurisdictions · filed Jan 21, 2020. View entity profile → Other incidents for this victim →
incident inc_4403bf1d2caf4d70 · 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.
CA MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 4, 2019
When the intrusion reportedly occurred, per the linked filings
Sep 4, 2019
Reported by CALIFORNIA AG filing
Sunshine Behavioral Health Group, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2020-01-21. The breach occurred from 9/4/2019 to 11/14/2019. 21 Montana residents were affected.
Affected (this filing): 21
Sunshine Behavioral Health Group, LLC notified individuals that a cloud-based system storing patient records was inadvertently configured to allow public internet access. The company became aware of the misconfiguration on September 4, 2019, and immediately changed settings and removed records from general access. Affected data included names, addresses, credit/debit card numbers, expiration dates, security codes, and electronic signatures. The company offered 24 months of identity protection services.
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.