The Hatcher Agency reported a data breach to the Montana Attorney General. The breach was reported on 2020-12-01. The breach occurred on 4/21/2020. 7 Montana residents were affected.
Affected (this filing): 7
Clustered 2 filings across 2 jurisdictions · filing window Dec 1, 2020 → Jan 13, 2021. View entity profile → Other incidents for this victim →
incident inc_086360eff7644f09 · 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
Apr 21, 2020
When the intrusion reportedly occurred, per the linked filings
Oct 20, 2020
Reported by MAINE AG filing
The Hatcher Agency reported a data breach to the Montana Attorney General. The breach was reported on 2020-12-01. The breach occurred on 4/21/2020. 7 Montana residents were affected.
Affected (this filing): 7
The Hatcher Agency reported an external system breach that occurred between March 6, 2020, and April 21, 2020. The breach was discovered on October 20, 2020, and affected 6 Maine residents. The compromised information included names in combination with driver's license or non-driver identification card numbers. In response, the company offered one year of credit monitoring, fraud consultation, identity theft restoration, and identity fraud loss reimbursement services from Kroll.
Affected (this filing):
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.