Clustered 2 filings across 2 jurisdictions · filed Oct 27, 2023. View entity profile → Other incidents for this victim →
incident inc_6c262f2dfcfe439a · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · PCI · Financial account
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.
CA ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 24, 2021
When the intrusion reportedly occurred, per the linked filings
Jun 6, 2023
Reported by MAINE AG, CALIFORNIA AG filings
Pennsylvania General Store, a retail entity, reported a data breach affecting 19,454 individuals. The breach was caused by a skimming attack on its third-party e-commerce vendor, CommerceV3, which compromised customer names and payment card information. The incident occurred on November 24, 2021, but was not discovered until June 6, 2023. Affected individuals were notified on September 15, 2023.
Affected (this filing): 19,454
Pennsylvania General Store notified customers of a data security incident involving its third-party e-commerce platform, CommerceV3. The incident occurred between November 24, 2021, and December 14, 2022, but was not discovered until June 6, 2023. Affected data may include names, email addresses, billing addresses, payment card numbers, CVV codes, and expiration dates. Approximately 46 Rhode Island residents were potentially impacted. CommerceV3 conducted a forensic investigation and implemented additional security measures.
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.