Diversified Financial Services, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2021-09-02. The breach occurred from 3/19/2021 to 6/14/2021. 18 Montana residents were affected.
Affected (this filing): 18
Clustered 2 filings across 2 jurisdictions · filing window Sep 2, 2021 → Sep 9, 2021. View entity profile → Other incidents for this victim →
incident inc_f296a0e86500497f · 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
Mar 19, 2021
When the intrusion reportedly occurred, per the linked filings
Aug 4, 2021
Reported by MAINE AG filing
Diversified Financial Services, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2021-09-02. The breach occurred from 3/19/2021 to 6/14/2021. 18 Montana residents were affected.
Affected (this filing): 18
Diversified Financial Services, LLC reported a data breach impacting 3,531 individuals, with 4 Maine residents affected. The breach, which occurred between March 19, 2021, and June 14, 2021, was discovered on August 4, 2021. The incident was described as an external system breach or hacking, resulting in the acquisition of names and driver's license numbers. Affected individuals were notified on September 3, 2021, and offered 12 months of identity theft protection services.
Affected (this filing): 3,531
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.