GLOBALClaimed by PlayFirst sightinglinked via shared-victim match · 100%
Posted to leak site Oct 21, 2024bd_2253413f51ca31e6
United States
Clustered 3 filings across 3 jurisdictions · filing window Oct 21, 2024 → Dec 2, 2024. View entity profile → Other incidents for this victim →
incident inc_3277c36979a64ecb · merge_method human · 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
ME NH
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
United States
Oct 27, 2024
When the intrusion reportedly occurred, per the linked filings
Oct 27, 2024
Reported by NEW HAMPSHIRE AG filing
Nov 4, 2024
Reported by MAINE AG filing
Joy Rockwell Ent., Inc. dba PostcardMania notified the New Hampshire Attorney General of a data security incident discovered on October 27, 2024. An unauthorized individual took files from the network containing personal information of one NH resident. The company engaged cybersecurity experts, notified the FBI, and offered Equifax identity protection services.
Affected (this filing): 1
On October 27, 2024, PostcardMania (Joy Rockwell Ent., Inc) experienced a network disruption. An investigation with independent cybersecurity experts determined that an unauthorized individual exfiltrated files containing personal information. The breach was discovered November 4, 2024. One Maine resident was among 2,640 total individuals affected. The FBI was notified. Affected individuals were offered 12 months of Equifax identity protection services.
Affected (this filing): 1
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.