Clustered 2 filings across 2 jurisdictions · filed Apr 2, 2025. View entity profile → Other incidents for this victim →
incident inc_0ba099bb3388469a · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
VT WA
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.
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 30, 2024 → Nov 18, 2024
When the intrusion reportedly occurred, per the linked filings
Dec 5, 2024
Reported by WASHINGTON AG, VERMONT AG filings
Neltac, Inc., a business sector entity reported a unauthorized access incident to the Washington Attorney General. The organization became aware of the incident on 2024-12-05 and filed notice on 2025-04-02. 2,584 Washington residents were affected. 118 days elapsed between awareness and notification. 66 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 2,584
Neltac, Inc. notified consumers of a data breach where an unauthorized individual accessed an employee email account. The unauthorized access occurred between September 30, 2024, and November 18, 2024. The incident was discovered on December 5, 2024, and forensic investigation confirmed personal data was likely subject to unauthorized acquisition. Neltac engaged external cybersecurity professionals and is offering 12 months of identity theft protection services to affected individuals.
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.