Clustered 3 filings across 3 jurisdictions · filing window Oct 8, 2025 → Mar 9, 2026. View entity profile → Other incidents for this victim →
incident inc_2eaaa57791294a13 · 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
ME NH
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 1, 2025
Reported by NEW HAMPSHIRE AG filing
Sep 19, 2025 → Sep 21, 2025
When the intrusion reportedly occurred, per the linked filings
Sep 22, 2025
Reported by MAINE AG filing
Founded in 1947, the Public Relations Society of America (PRSA) is a nationwide non-profit trade association serving the communications community and public relations professionals. It is headquartered in New York City, New York.
PRSA experienced an external system breach (Sep 19-21, 2025, discovered Sep 22, 2025) in which an unauthorized actor accessed its server environment and copied a limited amount of personal data. 873 total individuals affected; 1 Maine resident. PRSA isolated systems, changed passwords, notified federal law enforcement, and engaged data security professionals. Notifications sent Mar 4, 2026. No ID theft protection offered.
Public Relations Society of America (PRSA) notified the New Hampshire Attorney General on March 4, 2026, of a September 2025 security incident. An unauthorized actor accessed PRSA's server environment and copied a limited amount of data. Two New Hampshire residents were identified as potentially affected. PRSA isolated systems, changed passwords, notified federal law enforcement, and engaged privacy professionals.
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): 1
Affected (this filing): 2