Clustered 3 filings across 3 jurisdictions · filing window Jul 11, 2025 → Jul 21, 2025. View entity profile → Other incidents for this victim →
incident inc_aefa1fe7f086489d · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
PHI
FL NH VT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 6, 2024 → Oct 3, 2024
When the intrusion reportedly occurred, per the linked filings
Sep 16, 2024
Reported by NEW HAMPSHIRE AG filing
HHS OCR breach portal entry: Freedom Plaza Senior Living (FL, Healthcare Provider) reported a Hacking/IT Incident affecting 4,847 individuals, with breached information located in Email. Submitted 2025-07-11. No business associate involvement indicated. The portal row provides no narrative beyond these structured fields, so action category, threat actor, and remediation specifics are unknown.
Affected (this filing): 4,847
Freedom Plaza Senior Living notified consumers of a data breach affecting personal information including names and government identifiers. The notice, filed with the Vermont Attorney General on July 11, 2025, covers residents in multiple jurisdictions including Vermont, Maryland, New York, and others. Affected individuals were offered 12 months of credit monitoring and identity theft protection services through IDX.
Freedom Plaza Senior Living notified New Hampshire AG of unauthorized access to employee email accounts between Sept 6 and Oct 3, 2024, discovered Sept 16, 2024. Attack likely via phishing leading to credential compromise. Data at risk: names and SSNs of 2 NH residents. Remediation included forensic investigation, account security, and 12 months credit monitoring.
Affected (this filing): 2
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.