Gateway Financial Solutions reported a data breach to the Montana Attorney General. The breach was reported on 2021-10-27. The breach occurred from 11/12/2021 to 12/6/2020. 10 Montana residents were affected.
Affected (this filing): 10
Clustered 2 filings across 2 jurisdictions · filed Oct 27, 2021. View entity profile → Other incidents for this victim →
incident inc_31c9bf72939b4003 · 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
Nov 12, 2020 → Dec 6, 2020
When the intrusion reportedly occurred, per the linked filings
Sep 27, 2021
Reported by MAINE AG filing
Gateway Financial Solutions reported a data breach to the Montana Attorney General. The breach was reported on 2021-10-27. The breach occurred from 11/12/2021 to 12/6/2020. 10 Montana residents were affected.
Affected (this filing): 10
Gateway Financial Solutions experienced an external system breach that occurred between November 12, 2020, and December 6, 2020. The breach was discovered on September 27, 2021, and affected 53,801 individuals. The compromised information included names in combination with financial account numbers or credit/debit card numbers along with their security codes or PINs. The company began notifying affected individuals on October 27, 2021, and offered complimentary credit monitoring services.
Affected (this filing): 53,801
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.