Clustered 3 filings across 3 jurisdictions · filed May 21, 2021. View entity profile → Other incidents for this victim →
incident inc_f240d36313b747b8 · 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.
Health (basic) · Identity (basic)
MT NY OR
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 19, 2021
When the intrusion reportedly occurred, per the linked filings
Mar 22, 2021
Reported by OREGON AG filing
Aspen Dental Management, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2021-05-21. The breach occurred from 3/19/2021 to 3/20/2021. 1 Montana residents were affected.
Affected (this filing): 1
Aspen Dental Management, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2021-05-21. The breach occurred during 3/19/2021 - 3/20/2021. The breach was discovered on 3/22/2021. 10,147 individuals were affected. Notice was sent on 5/21/2021.
Affected (this filing): 10,147
Aspen Dental Management LLC (NY, Business Associate) reported to HHS on 2021-05-21 a Theft affecting 9,620 individuals. A hard drive containing PHI — including names, dental x-ray images, and medical record numbers — was stolen from its office. The CE notified HHS, affected individuals, and media, provided substitute notice, offered complimentary credit monitoring, and implemented additional administrative and technical safeguards. Breached information located on Laptop.
Affected (this filing): 9,620
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.