Stampin' Up reported a data breach to the Montana Attorney General. The breach was reported on 2021-05-14. The breach occurred from 6/12/2020 to 11/17/2020. 25 Montana residents were affected.
Affected (this filing): 25
Clustered 2 filings across 2 jurisdictions · filing window May 14, 2021 → May 17, 2021. View entity profile → Other incidents for this victim →
incident inc_000c0ff47eed4e34 · merge_method llm · confidence 44%
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.
Identity (basic) · Financial account
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 12, 2020
When the intrusion reportedly occurred, per the linked filings
Apr 14, 2021
Reported by MAINE AG filing
Stampin' Up reported a data breach to the Montana Attorney General. The breach was reported on 2021-05-14. The breach occurred from 6/12/2020 to 11/17/2020. 25 Montana residents were affected.
Affected (this filing): 25
Stampin' Up! reported a data breach affecting 36 Maine residents. The breach, which occurred between June 12, 2020, and November 17, 2020, was discovered on April 14, 2021. The incident was categorized as an external system breach or hacking, resulting in the compromise of names and financial account numbers or credit/debit card details, including security codes or PINs. Consumers were notified in writing on May 14, 2021.
Affected (this filing): 36
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.