Clustered 6 filings across 1 jurisdiction · filing window May 18, 2011 → Sep 16, 2011. View entity profile → Other incidents for this victim →
incident inc_204fb0b48c3f4f9b · 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.
NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
State of New Hampshire Attorney General breach notification filed by Experian on 2011-05-18. The source document is a PDF attachment that contains no visible text content in the provided source body. No specific breach details, dates, or data types are extractable from the provided input.
State of New Hampshire Attorney General breach notification filed by Experian on May 27, 2011. The source document is a PDF attachment that appears to be empty or contains only page markers. No specific breach details, dates, data types, or response actions are visible in the provided text.
State of New Hampshire Attorney General breach notification filed by Experian on 2011-07-20. The source document is a PDF attachment that contains no extractable text content in the provided source body. No breach details, dates, or data types are available for extraction.
State of New Hampshire Attorney General breach notification filed by Experian on 2011-07-28. The source document is a PDF attachment with no visible text content provided in the extraction.
State of New Hampshire Attorney General breach notification filed by Experian on 2011-08-31. The source document is a PDF attachment that contains no visible text content in the provided source body. No breach details, dates, or data types are extractable.
State of New Hampshire Attorney General breach notification filed by Experian on 2011-09-16. The source document is a PDF attachment with no visible text content provided in the source body.
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.