One linked filing — more sources may join as they report · filed Apr 15, 2026. View entity profile → Other incidents for this victim →
incident inc_27ca7a3f239d417c · 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
10-K Item 1C cybersecurity disclosure. The registrant explicitly states it has not experienced any material cybersecurity incidents or identified any material cybersecurity threats. The filing describes a risk management program covering access controls, data protection, monitoring, incident response, and third-party risk management, relying on AWS for cloud infrastructure.
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.