Presnell Gage, PLLC reported a data breach to the Montana Attorney General. The breach was reported on 2016-08-18. The breach occurred from 7/16/2016 to 8/18/2016. 35 Montana residents were affected.
Affected (this filing): 35
Clustered 2 filings across 2 jurisdictions · filing window Aug 18, 2016 → Aug 30, 2016. View entity profile → Other incidents for this victim →
incident inc_ca081df33d0547e6 · 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.
MT WA
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 16, 2016
When the intrusion reportedly occurred, per the linked filings
Aug 18, 2016
Reported by WASHINGTON AG filing
Presnell Gage, PLLC reported a data breach to the Montana Attorney General. The breach was reported on 2016-08-18. The breach occurred from 7/16/2016 to 8/18/2016. 35 Montana residents were affected.
Affected (this filing): 35
Presnell Gage, PLLC, a finance sector entity reported a unauthorized access incident to the Washington Attorney General. The organization became aware of the incident on 2016-08-18 and filed notice on 2016-08-30. 2,613 Washington residents were affected. 12 days elapsed between awareness and notification. 33 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 2,613
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.