Clustered 3 filings across 3 jurisdictions · filing window Mar 27, 2026 → Apr 1, 2026. View entity profile → Other incidents for this victim →
incident inc_5583a4490d1749bd · 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
Aug 22, 2025
When the intrusion reportedly occurred, per the linked filings
Aug 22, 2025
Reported by NEW HAMPSHIRE AG filing
Proxycare, Inc., a Florida-based healthcare provider, reported a Hacking/IT Incident to HHS OCR affecting 45,196 individuals. The breach involved a network server. No business associate was reported as involved.
Affected (this filing): 45,196
State of Vermont Attorney General breach notice filed by Proxycare Inc. on 2026-03-27. The filing page contains a link to a PDF attachment, but the attachment content is empty/redacted in the source. No specific breach details, dates, data types, or affected individual counts are visible in the provided text.
Proxycare, LLC notified the New Hampshire Attorney General of a data breach affecting 26 NH residents. Unauthorized access occurred on or about August 22, 2025. The breach exposed personal health information, names, DOBs, SSNs, and driver's license numbers. Proxycare offered credit monitoring services to affected individuals.
Affected (this filing): 26
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.