Arbor Financial Credit Union reported a data breach to the Montana Attorney General. The breach was reported on 2020-11-06. The breach occurred from 5/15/2020 to 10/20/2020. 9 Montana residents were affected.
Affected (this filing): 9
Clustered 2 filings across 2 jurisdictions · filing window Nov 6, 2020 → Nov 7, 2020. View entity profile → Other incidents for this victim →
incident inc_8b2f85dcdc534a05 · 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
May 15, 2020
When the intrusion reportedly occurred, per the linked filings
Oct 20, 2020
Reported by MAINE AG filing
Arbor Financial Credit Union reported a data breach to the Montana Attorney General. The breach was reported on 2020-11-06. The breach occurred from 5/15/2020 to 10/20/2020. 9 Montana residents were affected.
Affected (this filing): 9
Arbor Financial Credit Union reported a data breach to the Maine Attorney General, stating that an external system breach (hacking) occurred on May 15, 2020. The breach was discovered on October 20, 2020, and affected 7 Maine residents. The compromised information included names and financial account numbers or credit/debit card numbers with their security codes. The credit union offered 12 months of complimentary credit monitoring services through Experian to the affected individuals.
Affected (this filing): 7
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.