Clustered 4 filings across 3 jurisdictions · filing window Jul 18, 2023 → Jul 20, 2023. View entity profile → Other incidents for this victim →
incident inc_cc72317bdd3a473b · 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.
ME MT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 20, 2023
When the intrusion reportedly occurred, per the linked filings
May 11, 2023
Reported by MAINE AG filing
The Wasserstrom Company, which began as a local, family-run business, has steadily grown to become one of the largest restaurant suppliers and distributors of foodservice products. With more than a century of experience and a team of over 1200 dedicated associates, Wasserstrom remains a family-owned
Wasserstrom Holdings, Inc reported a data breach to the Montana Attorney General. The breach was reported on 2023-07-18. The breach occurred from 4/20/2023 to 4/21/2023. 1 Montana residents were affected.
Affected (this filing): 1
Wasserstrom Holdings, Inc. reported an external system breach that occurred between April 20 and April 21, 2023. The breach was discovered on May 11, 2023, and affected 3 Maine residents. The compromised information included names and Social Security numbers. Affected individuals were notified on July 18, 2023, and offered 12 months of identity theft protection services through Experian.
Affected (this filing): 3
The Wasserstrom Company, headquartered in Columbus, Ohio and founded in 1902, is a restaurant supplier and distributor of foodservice supplies and equipment. They sell products, such as kitchen supplies and catering supplies, from industry manufacturers.
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.