Dental Health Management Solutions reported a data breach to the Montana Attorney General. The breach was reported on 2023-02-22. The breach occurred from 8/5/2022 to 8/20/2022. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Feb 22, 2023 → Mar 2, 2023. View entity profile → Other incidents for this victim →
incident inc_a8bd4f75fe194c2c · 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
Aug 20, 2021
Reported by MAINE AG filing
Aug 5, 2022
When the intrusion reportedly occurred, per the linked filings
Dental Health Management Solutions reported a data breach to the Montana Attorney General. The breach was reported on 2023-02-22. The breach occurred from 8/5/2022 to 8/20/2022. 1 Montana residents were affected.
Affected (this filing): 1
Dental & Health Management Solutions experienced an external system breach on July 17, 2021, which was discovered on August 20, 2021. The breach affected 3,205 individuals, compromising their names and financial account or credit/debit card numbers along with security codes or PINs. The company began notifying affected individuals on February 17, 2023, and offered 12 months of identity theft protection services through Identity Force.
Affected (this filing): 3,205
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.