Sears Hometown Stores, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2021-08-24. The breach occurred from 6/3/2021 to 6/15/2021. 7 Montana residents were affected.
Affected (this filing): 7
Clustered 2 filings across 2 jurisdictions · filing window Aug 24, 2021 → Aug 27, 2021. View entity profile → Other incidents for this victim →
incident inc_637af6e955e74951 · 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.
MT NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 3, 2021
When the intrusion reportedly occurred, per the linked filings
Jun 24, 2021
Reported by NEW HAMPSHIRE AG filing
Sears Hometown Stores, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2021-08-24. The breach occurred from 6/3/2021 to 6/15/2021. 7 Montana residents were affected.
Affected (this filing): 7
Sears Hometown Stores, Inc. reported a data breach involving its third-party HR provider, Transform SR Holding Management LLC. Unauthorized access to employee data occurred between June 3 and June 15, 2021, and was discovered on June 24, 2021. The breach affected 9 New Hampshire residents, exposing Social Security numbers, financial account numbers, and healthcare insurance information. Sears Hometown notified the NH Attorney General on August 27, 2021, and sent notifications to affected individuals on August 24, 2021, offering 12 months of identity monitoring via Kroll.
Affected (this filing): 9
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.