Clustered 3 filings across 1 jurisdiction · filing window Jan 18, 2017 → Feb 20, 2017. View entity profile → Other incidents for this victim →
incident inc_8dc171f5473b4f9c · merge_method deterministic · confidence 100%
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.
CA
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 31, 2016
When the intrusion reportedly occurred, per the linked filings
Discover Financial Services reported a data security breach to the California Attorney General. The breach occurred on January 31, 2016. The provided source document contains only the filing metadata and empty attachment placeholders; no narrative details regarding the nature of the breach, data types affected, or number of individuals impacted are available in the text content.
Discover Financial Services reported a data security breach to the California Attorney General. The filing lists the date of the breach as January 2, 2016. The provided source document contains only the web portal metadata and empty attachment placeholders; no narrative details regarding the nature of the breach, data types affected, or number of individuals impacted are available in the input.
Discover Financial Services reported a data breach to the California Attorney General. The filing lists the date of the breach as November 29, 2015. The provided source document contains only the web page metadata and empty attachment placeholders; no narrative description of the incident, data types, or affected counts is available in the text provided.
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.