Clustered 3 filings across 3 jurisdictions · filing window Nov 24, 2024 → Jan 9, 2025. View entity profile → Other incidents for this victim →
incident inc_d1134a3347a34571 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
PII · Identity (basic) · Government ID
CA ME
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 10, 2024 → Nov 10, 2024
When the intrusion reportedly occurred, per the linked filings
Nov 20, 2024
Reported by CALIFORNIA AG, MAINE AG filings
Client’s Personal data and ID’s Total personal records : 422,075 https://www.stiiizy.com/ Company representative should follow the instructions to contact us before time runs out
Stiiizy Inc. notified customers of a data breach involving a third-party point-of-sale vendor. An organized cybercrime group compromised the vendor's accounts, acquiring personal information of Stiiizy customers between October 10 and November 10, 2024. Stiiizy was notified on November 20, 2024. Affected data includes government-issued ID details (driver's licenses, passports), medical cannabis cards, and transaction histories. Stiiizy is offering 12 months of free credit monitoring.
Stiiizy Inc. (cannabis dispensary) reported a breach affecting 212 Maine residents (380,000 total). Oct 10–Nov 10, 2024: an organized cybercrime group compromised a third-party POS vendor serving CA retail locations. Data exposed: names, addresses, DOB, driver's license/passport numbers, photos, signatures, medical cannabis cards, transaction histories. Notified Jan 8, 2025; 12-month credit monitoring offered via Cyberscout/TransUnion.
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.
Affected (this filing): 212