KSI — February 2015 breach
Clustered 2 filings across 1 jurisdiction · filed Feb 20, 2015. View entity profile → Other incidents for this victim →
incident inc_e26f73a1da154d81 · merged by deterministic · confidence 100%
Litigation Timing
Discovered → first regulatory filing
Range of discovered_at dates across filings
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.
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
- FEB 20NH AGNH AG noticefirst filing · states nationwide total 641day 0
- FEB 20NH AGNH AG noticemost recent · states nationwide total 641day 0
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Feb 9, 2015 NH AG
- Discovered
- Feb 9, 2015 NH AG
- Data types
- Identity (basic) · Government ID NH AG
- Response
- Took steps to secure the information and mitigate any harm · Identified the individual who received it and confirmed that no one else received a copy · Confirmed that the individual who received the email did not further disclose it, deleted it in all places and no longer retains a copy 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)
641
Sum of filed state slices
14· 2.2% of stated
98% 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.
Merge provenance
- Method
- deterministic
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Audit
- Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).
Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.
Filing velocity
Spread
0 days
vs. multi-state median
20.0× faster
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.