Capital One, National Association, notified customers out of an abundance of caution that they were at risk of future fraud. The company stated there was no evidence that data has been breached.
Affected (this filing): 2
One linked filing — more sources may join as they report · filed Mar 22, 2021. View entity profile → Other incidents for this victim →
incident inc_cbd6e81c17674f3e · merge_method deterministic
Discovered → first regulatory filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Financial account · Financial credentials
ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 10, 2020
When the intrusion reportedly occurred, per the linked filings
Dec 11, 2020
Reported by MAINE AG filing
Capital One, National Association, notified customers out of an abundance of caution that they were at risk of future fraud. The company stated there was no evidence that data has been breached.
Affected (this filing): 2
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.