Clustered 2 filings across 2 jurisdictions · filed Mar 13, 2026. View entity profile → Other incidents for this victim →
incident inc_4094f4cfc38540da · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
PII · Identity (basic)
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.
NH VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 10, 2025 → Jul 25, 2025
When the intrusion reportedly occurred, per the linked filings
Jul 25, 2025
Reported by VERMONT AG, NEW HAMPSHIRE AG filings
Philadelphia Corporation for Aging notified consumers of a data breach occurring between July 10-25, 2025. Unauthorized access resulted in copying of personal information. PCA reported to law enforcement, engaged forensic specialists, and offered 12 months of free credit monitoring. No specific count of affected individuals was disclosed in the filing.
Philadelphia Corporation for Aging (PCA) submitted a supplemental data event notice to the New Hampshire Attorney General regarding a cybersecurity incident. PCA became aware of unusual network activity on July 25, 2025, involving unauthorized copying of data between July 10 and July 25, 2025. The incident affected 10 New Hampshire residents, exposing names, SSNs, financial account numbers, and health/Medicaid information. PCA engaged forensic specialists, reported to law enforcement, and provided 12 months of credit monitoring. This is a follow-up to an initial notice filed November 4, 2025.
Affected (this filing): 10
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.