Gries Financial Partners reported a data breach to the Montana Attorney General. The breach was reported on 2023-02-10. The breach occurred from 9/8/2022 to 10/11/2022. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Feb 10, 2023 → Feb 14, 2023. View entity profile → Other incidents for this victim →
incident inc_12f870d1cecc4dd7 · 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.
MT NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 8, 2022
When the intrusion reportedly occurred, per the linked filings
Oct 12, 2022
Reported by NEW HAMPSHIRE AG filing
Gries Financial Partners reported a data breach to the Montana Attorney General. The breach was reported on 2023-02-10. The breach occurred from 9/8/2022 to 10/11/2022. 1 Montana residents were affected.
Affected (this filing): 1
Gries Financial Partners notified the New Hampshire Attorney General of a data event affecting one resident. Unauthorized access to employee email accounts occurred between September 8 and October 11, 2022, discovered on October 12, 2022. Affected data included names, addresses, financial account info, SSNs, and driver's licenses. GFP notified law enforcement, enhanced email security, and offered 2 years of credit monitoring.
Affected (this filing): 1
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.