Curian Capital, LLC — January 2010 breach
One linked filing — more sources may join as they report · filed Jan 29, 2010. View entity profile → Other incidents for this victim →
incident inc_f1c218a7693d4c0a · merged by deterministic
Litigation Timing
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.
Sensitive data
identity_governmentIncident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- JAN 29NH AGNH AG noticeonly filing · states nationwide total 706day 0
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Jan 19, 2010 – Jan 20, 2010 NH AG
- Discovered
- Jan 19, 2010 NH AG
- Data types
- Identity (basic) · Government ID · Financial account NH AG
- Response
- Promptly removed the statements from the incorrect financial professional’s secure online filing cabinet · Notified all of the approximately 706 clients that were potentially affected... by letter sent via first-class mail NH AG
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Count reconciliation
per-state reported counts
Nationwide (stated in a filing)
706
Sum of filed state slices
1· 0.1% of stated
100% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
Evidence ladder — rungs this incident occupies
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
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.