State of New Hampshire Attorney General breach notification filed by Windhaven Investment Management, Inc. on September 19, 2013. The attached PDF document is empty; no breach details, dates, or data types are provided in the source text.
Clustered 2 filings across 2 jurisdictions · filing window Sep 19, 2013 → Sep 23, 2013. View entity profile → Other incidents for this victim →
incident inc_73629c4b4eb345c9 · 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.
Identity (basic) · Financial account
CA NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 1, 2013
Reported by CALIFORNIA AG filing
State of New Hampshire Attorney General breach notification filed by Windhaven Investment Management, Inc. on September 19, 2013. The attached PDF document is empty; no breach details, dates, or data types are provided in the source text.
Windhaven Investment Management, Inc. disclosed an unauthorized intrusion on a web server maintained by a third-party vendor. The incident was discovered in August 2013. The intruder may have accessed a database containing customer names, account numbers, custodians, and investment positions. Social Security numbers and dates of birth were not included. Windhaven disconnected the server, reported to law enforcement, and offered credit monitoring.
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.