One linked filing — more sources may join as they report · filed Feb 13, 2026. View entity profile → Other incidents for this victim →
incident inc_ddd43b16d3fa4e77 · merge_method deterministic
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; needs two dated filings.
FEDERAL
all SEC 10-K Item 1C
Earliest sighting first · deep chronology in Litigation Timeline
Item 1C disclosure states the Company has not experienced a cybersecurity incident that materially affected or is reasonably likely to materially affect its business, strategy, results of operations, or financial condition. The Company acknowledges it has experienced threats and breaches from time to time but provides no specific details on incidents, data types, or counts.
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.