Clustered 3 filings across 2 jurisdictions · filing window Aug 19, 2020 → Sep 29, 2020. View entity profile → Other incidents for this victim →
incident inc_fba9687f2fe84d8b · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
ME MT
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
all State AG
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
May 15, 2020
When the intrusion reportedly occurred, per the linked filings
Aug 6, 2020
Reported by MAINE AG filings
Capital One reported a data breach to the Montana Attorney General. The breach was reported on 2020-08-19. The breach occurred from 5/15/2020 to 6/16/2020. 1 Montana residents were affected.
Affected (this filing): 1
Capital One, National Association reported a cybersecurity incident to the Maine Attorney General affecting 1,277 individuals, including 8 Maine residents. The breach occurred between May 15, 2020, and June 2, 2020, and was discovered on August 6, 2020. The company stated that customers are at risk of future fraud but there is no evidence that data was actually breached. Affected data included names and financial account or credit/debit card numbers. Capital One provided 2 years of free credit monitoring through TransUnion.
Affected (this filing): 1,277
Capital One, National Association, reported a potential data compromise affecting 1,277 individuals, including 8 Maine residents. The incident occurred between May 15, 2020, and June 2, 2020, and was discovered on August 6, 2020. While the company stated there is no evidence that data has been breached, it issued notifications out of an abundance of caution as customers' Social Security numbers were at risk. The company offered 24 months of free credit monitoring services to affected individuals.
Affected (this filing): 1,277
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.