Dakota County, Minnesota reported a data breach to the Montana Attorney General. The breach was reported on 2019-04-12. The breach occurred on 3/27/2019. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Apr 12, 2019. View entity profile → Other incidents for this victim →
incident inc_d4e2386753be4151 · 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.
MN MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 27, 2019
When the intrusion reportedly occurred, per the linked filings
Apr 12, 2019
Reported by HHS OCR filing
Dakota County, Minnesota reported a data breach to the Montana Attorney General. The breach was reported on 2019-04-12. The breach occurred on 3/27/2019. 1 Montana residents were affected.
Affected (this filing): 1
Dakota County reported to HHS on 2019-04-12 a Hacking/IT Incident affecting 1,026 individuals. Breached information located on Email. An employee was the victim of an email phishing scheme exposing PHI including names, addresses, driver's license numbers, SSNs, health insurance, diagnoses, and clinical information. The CE implemented additional safeguards and retrained staff on identifying fraudulent emails.
Affected (this filing): 1,026
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.