Clustered 2 filings across 2 jurisdictions · filing window Mar 1, 2023 → Mar 6, 2023. View entity profile → Other incidents for this victim →
incident inc_4f55a1f1034145cc · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Credentials
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.
NH VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 2, 2021 → Oct 19, 2021
When the intrusion reportedly occurred, per the linked filings
Oct 14, 2021
Reported by VERMONT AG, NEW HAMPSHIRE AG filings
Eileen Fisher, Inc. notified consumers of unauthorized access to employee email accounts between July 2, 2021, and October 19, 2021. The breach may have exposed names and other data elements. The company secured its network, engaged third-party specialists, reported to law enforcement, and offered 24 months of identity monitoring services.
Eileen Fisher, Inc. filed a supplemental notice with the New Hampshire Attorney General regarding unauthorized access to employee email accounts. The incident occurred between July 2 and October 19, 2021, and was discovered on October 14, 2021. Compromised data included names, SSNs, and bank account information. The company engaged third-party specialists, notified law enforcement, and provided 24 months of credit monitoring. Four New Hampshire residents were affected.
Affected (this filing): 4
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.