Clustered 2 filings across 2 jurisdictions · filed Apr 17, 2026. View entity profile → Other incidents for this victim →
incident inc_6d4a3d80c5054520 · 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.
NH VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 18, 2026
Reported by NEW HAMPSHIRE AG filing
Ameriprise Financial, Inc. reported a data breach to the Vermont Attorney General. The breach was reported to the AGO on 2026-04-17. The reporting organization type is Financial Services. 83 Vermont residents were affected. Categories of data breached: Social Security Numbers, Financial Account Codes, Credit or Debit Account Info.
Ameriprise Financial, Inc. notified the New Hampshire Attorney General on April 17, 2026, of a data incident discovered on March 18, 2026. An unauthorized individual accessed stored data, potentially affecting 433 NH residents. Affected data included names, addresses, account numbers, DOB, and SSNs. No unauthorized fund movements occurred. Ameriprise engaged external cybersecurity experts, enhanced account monitoring, and offered 12 months of free credit/identity monitoring via Equifax.
Affected (this filing): 433
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.