Clustered 3 filings across 3 jurisdictions · filing window Mar 6, 2026 → Mar 11, 2026. View entity profile → Other incidents for this victim →
incident inc_8a1f534025424545 · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
IN VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 18, 2026
When the intrusion reportedly occurred, per the linked filings
Feb 18, 2026
Reported by VERMONT AG filing
NELSON Worldwide is an award-winning firm delivering architecture, interior design, graphic design, and brand strategy services that transform all dimensions of the human experience, providing our clients with strategic and creative solutions that positively impact their lives and the environments w...
Nelson Worldwide, LLC reported unauthorized network access on February 18, 2026. The incident compromised customer names. The company engaged external forensic investigators, secured the network, and offered complimentary credit monitoring services to affected individuals. No specific count of affected individuals was disclosed in the filing.
Nelson Worldwide LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2026-02-18 and was reported on 2026-03-11. 13 Indiana residents were affected. 2,942 individuals affected in total.
Affected (this filing): 2,942
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.