Clustered 2 filings across 2 jurisdictions · filing window Nov 18, 2025 → Nov 19, 2025. View entity profile → Other incidents for this victim →
incident inc_65a16b344f014d44 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
PII · Identity (basic)
DE NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 31, 2025
Reported by NEW HAMPSHIRE AG filing
WEL Companies, Inc. notified Delaware residents of a data security incident occurring in March 2026, discovered in November 2026. Unauthorized acquisition of files containing personal information (names, addresses) occurred. No evidence of misuse. WEL engaged cybersecurity experts, enhanced security, and offered 60 months of free identity monitoring via Kroll.
WEL Companies, Inc. notified the New Hampshire Attorney General of a data security incident discovered on January 31, 2025. Unauthorized access to WEL systems resulted in the potential acquisition of personal information, including names, Social Security numbers, and driver's license numbers, affecting 592 New Hampshire residents. Notifications were sent on November 18, 2025, offering complimentary identity protection services. No evidence of misuse was found.
Affected (this filing): 592
Mar 1, 2026
When the intrusion reportedly occurred, per the linked filings
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.