Hamilton Zanze & Company reported a data breach to the Montana Attorney General. The breach was reported on 2017-07-25. The breach occurred on 6/29/2017. 5 Montana residents were affected.
Affected (this filing): 5
Clustered 2 filings across 2 jurisdictions · filing window Jul 25, 2017 → Jul 27, 2017. View entity profile → Other incidents for this victim →
incident inc_6adc0d92e19948da · 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.
CA MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 29, 2017
When the intrusion reportedly occurred, per the linked filings
Jun 29, 2017
Reported by CALIFORNIA AG filing
Hamilton Zanze & Company reported a data breach to the Montana Attorney General. The breach was reported on 2017-07-25. The breach occurred on 6/29/2017. 5 Montana residents were affected.
Affected (this filing): 5
Hamilton Zanze & Company reported the theft of an employee's password-protected laptop from a vehicle on June 29, 2017. The laptop potentially contained client information including names, dates of birth, phone numbers, addresses, and Social Security numbers. The company disabled credentials, wiped the laptop remotely, and offered 24 months of identity repair and credit monitoring to affected individuals. No evidence of data access was found.
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.