Thomas D. Mangelsen, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2020-12-31. The breach occurred from 10/29/2020 to 11/19/2020. 3 Montana residents were affected.
Affected (this filing): 3
Clustered 2 filings across 2 jurisdictions · filed Dec 31, 2020. View entity profile → Other incidents for this victim →
incident inc_fc9ad77b161d4e08 · 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.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 29, 2020
When the intrusion reportedly occurred, per the linked filings
Nov 25, 2020
Reported by MAINE AG filing
Thomas D. Mangelsen, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2020-12-31. The breach occurred from 10/29/2020 to 11/19/2020. 3 Montana residents were affected.
Affected (this filing): 3
Thomas D. Mangelsen, Inc. experienced an external system breach (hacking) that occurred from October 29, 2020, to November 19, 2020. The breach was discovered on November 25, 2020. The compromised information includes names and financial account numbers or credit/debit card numbers with their security codes. One Maine resident was affected out of a total of 210 individuals. Affected individuals were notified on December 31, 2020, and offered 12 months of complimentary credit monitoring services through TransUnion.
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.