PKF O'Connor Davies reported a data breach to the Montana Attorney General. The breach was reported on 2021-04-02. The breach occurred from 11/8/2020 to 12/10/2020. 8 Montana residents were affected.
Affected (this filing): 8
Clustered 2 filings across 2 jurisdictions · filed Apr 2, 2021. View entity profile → Other incidents for this victim →
incident inc_99a4ac9fc3f64ea5 · 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.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 8, 2020
When the intrusion reportedly occurred, per the linked filings
Dec 10, 2020
Reported by MAINE AG filing
PKF O'Connor Davies reported a data breach to the Montana Attorney General. The breach was reported on 2021-04-02. The breach occurred from 11/8/2020 to 12/10/2020. 8 Montana residents were affected.
Affected (this filing): 8
PKF O'Connor Davies, a financial services firm, reported an external system breach (hacking) occurring between November 8, 2020, and November 23, 2022. The incident affected 995 individuals, including 2 Maine residents. Acquired data included names and financial account or credit/debit card numbers (with security codes/PINs). The firm notified affected consumers in writing and provided 12-24 months of credit monitoring and ID theft protection via Cyberscout.
Affected (this filing): 995
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.