GLOBALClaimed by PlayFirst sighting
Posted to leak site Feb 14, 2026bd_10adf862cbb28250
United States
Clustered 3 filings across 3 jurisdictions · filing window Feb 14, 2026 → Jun 10, 2026. View entity profile → Other incidents for this victim →
incident inc_ecc3c4c69e1f4d05 · 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.
NH TX
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
United States
Feb 25, 2026 → Feb 26, 2026
When the intrusion reportedly occurred, per the linked filings
Feb 26, 2026
Reported by NEW HAMPSHIRE AG filing
Apr 30, 2026
Reported by TEXAS AG filing
Project Consulting Services, Inc. (PCS) notified the New Hampshire Attorney General of a data event affecting 3 NH residents. An unknown actor accessed systems between Feb 25-26, 2026, copying files containing names and Social Security numbers. PCS reported to federal law enforcement, provided 24 months of Experian credit monitoring, and notified credit bureaus.
Project Consulting Services, Inc. based in Metairie, Louisiana, a other entity reported a data breach to the Texas Attorney General. The breach was discovered on 2026-04-30 and reported on 2026-06-10. 419 Texas residents were affected. 1,572 individuals affected in total. Types of information involved: Name of individual;Social Security Number Information;Driver’s License number;Financial Information (e.g. account number, credit or debit card number);Medical Information;Health Insurance Information. Consumers were notified via U.S. Mail.
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): 3
Affected (this filing): 419