Orange textured background

US federal - healthcare sector

HIPAA and browser fingerprinting: when tracking technology creates PHI

OCR's 2022-2023 guidance on online tracking technologies established that device and browser fingerprinting on covered-entity websites can produce Protected Health Information the moment it combines a device identifier with health-related browsing activity. This page explains when HIPAA applies, what a Business Associate Agreement covers, and where the FTC Health Breach Notification Rule picks up for apps that fall outside HIPAA's scope.

Reviewed

RegionUnited States
RegulatorHHS Office for Civil Rights (OCR)
EffectivePrivacy Rule: 14 April 2003; Security Rule: 20 April 2005; OCR tracking-technology bulletin: December 2022 (updated March 2023)
Max penaltyUp to $1.9 million per violation category per calendar year (as adjusted for inflation); criminal penalties also apply under 42 U.S.C. 1320d-6
Status in-force

The OCR tracking-technology bulletin: what changed in 2022-2023

Before December 2022, HIPAA compliance guidance on website analytics focused primarily on electronic health record portals and patient-facing applications. The HHS Office for Civil Rights bulletin published in December 2022, and substantially updated in March 2023, shifted the analysis to cover all online tracking technologies used by covered entities and their business associates - including pixels, session-replay tools, analytics platforms, and device fingerprinting.

The bulletin's core holding is that when a tracking technology on a covered entity's website collects an individually identifiable piece of data (including a device identifier, IP address, or device fingerprint) in combination with information about the individual's interaction with the site that relates to health conditions, treatment, or payment, the resulting data is PHI. The covered entity cannot transmit that data to a third-party vendor without either a signed BAA with that vendor or a valid patient authorisation under 45 CFR 164.508.

The bulletin does not create new law. It interprets the existing HIPAA Privacy Rule (45 CFR Part 164, Subpart E) and Security Rule (45 CFR Part 164, Subpart C) as applied to a category of data collection that post-dates the original rulemaking. OCR's position is that the rules have always covered this data; the bulletin makes the application explicit.

When does a device fingerprint become PHI?

PHI is defined under the Privacy Rule as 'individually identifiable health information' that is created, received, maintained, or transmitted by a covered entity or business associate in connection with the provision of health care, health plan operations, or health care payment. The 'individually identifiable' element requires that the information either identifies the individual or could reasonably be used to identify them.

A device fingerprint in isolation - a hash derived from browser and hardware signals - does not obviously identify a health condition. The PHI question turns on context: what page was the fingerprint collected on, and what does visiting that page reveal about health? OCR's bulletin identifies several categories of URL and event patterns that, when combined with a device identifier, constitute PHI. Examples include: a URL that contains a condition name or treatment term, a URL for a patient portal login page, event-level data indicating that the user searched for a specific medication on a pharmacy benefits page, or interaction data on a symptom-checker tool.

The key test from OCR's bulletin is whether the combination of the identifier and the browsing data could reasonably be used to infer health information about a specific person. A device fingerprint collected on a hospital's homepage contact page is at lower risk than the same fingerprint collected on a page titled with a specific condition or clinic department. However, OCR notes that even a homepage visit, when the covered entity's website is dedicated to a specific condition (an oncology centre, a fertility clinic), can implicate PHI because visiting the site at all is associated with a health interest.

Business Associate Agreements and fingerprinting vendors

Under 45 CFR 164.502(e) and 164.504(e), a covered entity may not disclose PHI to a third party unless that party is a business associate with whom the covered entity has a signed BAA, or unless a Privacy Rule exception applies (such as a valid patient authorisation under 45 CFR 164.508). A fingerprinting vendor that receives PHI, even passively through an SDK or API call embedded in the covered entity's site, is a business associate.

The BAA must specify: what PHI the vendor may use or disclose; that the vendor will use appropriate safeguards and, for electronic PHI, comply with the Security Rule; that the vendor will report breaches to the covered entity; and that the vendor will make its practices available to OCR for audit. A standard vendor data-processing agreement or terms-of-service is not a BAA. Covered entities using off-the-shelf device fingerprinting tools should confirm in writing whether the vendor will sign a HIPAA-compliant BAA before any PHI touches the vendor's infrastructure.

If a fingerprinting vendor refuses to sign a BAA, the covered entity has two compliance paths: (1) deploy the fingerprinting technology on unauthenticated pages only, conduct a facts-and-circumstances analysis confirming no PHI is transmitted to the vendor in those contexts, and document that analysis; or (2) implement a server-side fingerprinting architecture where the vendor's SDK never receives PHI directly - the covered entity's own backend handles the data and transmits only non-PHI signals to the vendor. Either path requires legal review.

HIPAA applicability by deployment scenario

Deployment scenarioPHI likely?BAA required?Key condition
Fingerprinting on authenticated patient-portal pagesYes - user identity is established; all session data is presumptively PHIYesVendor must sign BAA before any data is transmitted
Fingerprinting on a condition-specific or clinic-department landing page (unauthenticated)Likely yes - URL context implies health interestYes, if PHI confirmedConduct page-level facts-and-circumstances analysis; document conclusion
Fingerprinting on a general hospital homepage or generic contact page (unauthenticated)Fact-specific; lower risk but not zeroIf PHI confirmedAnalyse whether site purpose links all visitors to a health condition; document
Fingerprinting on a pharmacy benefits portal (authenticated)Yes - medication search and purchase data is PHIYesVendor must sign BAA; Security Rule safeguards apply to ePHI
Fingerprinting on a health-insurance member portal (authenticated)Yes - plan data is PHIYesVendor must sign BAA; audit logs required under Security Rule
Fingerprinting on a general consumer wellness app (non-covered entity)Not HIPAA-covered; FTC HBNR may applyNo BAA (HIPAA does not apply)Assess FTC Health Breach Notification Rule obligations separately
Fingerprinting on an employer wellness portal outside a group health planNot HIPAA-coveredNo BAA (HIPAA does not apply)FTC HBNR and applicable state law govern; HIPAA does not
Server-side fingerprinting where vendor never receives PHIPHI handled by covered entity only; vendor receives non-PHI outputPotentially no (depends on what the vendor receives)Architecture must ensure PHI does not leave covered entity's environment; get legal sign-off

The Security Rule and electronic PHI from fingerprinting

When PHI is in electronic form, the Security Rule (45 CFR Part 164, Subpart C) imposes additional obligations. A device fingerprint that constitutes ePHI must be protected by administrative safeguards (risk analysis under 45 CFR 164.308), physical safeguards (access controls over systems that store ePHI), and technical safeguards (encryption, audit controls, integrity controls). A business associate that receives ePHI through a fingerprinting SDK is itself subject to the Security Rule's requirements.

For covered entities, the Security Rule's risk analysis requirement is particularly important in the tracking-technology context. OCR's guidance specifies that covered entities must assess the risks of transmitting ePHI to third-party tracking vendors and implement reasonable and appropriate safeguards. A covered entity that deploys fingerprinting on authenticated pages without a risk analysis documenting how ePHI flows to or through the vendor is exposed to a finding of Security Rule non-compliance, separate from any Privacy Rule issue with the BAA.

OCR enforcement context for online tracking

OCR has pursued settlements and corrective action plans against covered entities for sharing patient data with online advertising platforms. In 2023 and 2024, OCR announced multiple investigations into health system use of web tracking tools - including pixels and analytics SDKs - on patient-facing websites. Several of these investigations were triggered by journalists' and researchers' findings that hospital websites were transmitting identifiable patient data to third-party advertising platforms without BAAs.

While OCR has not published a settlement that specifically names 'device fingerprinting' as the violating technology, the legal theory applied to pixels and analytics SDKs is directly applicable: any tracking technology that collects PHI and transmits it to a vendor without a BAA violates 45 CFR 164.502(e). Covered entities that have deployed third-party device fingerprinting on authenticated pages, or on condition-specific unauthenticated pages, without a BAA should treat those deployments as presenting the same risk profile as the pixel-related investigations.

OCR's published penalty structure under 45 U.S.C. 1320d-5 (as amended by HITECH and adjusted for inflation) ranges from $137 per violation for unknowing violations to $1.9 million per violation category per calendar year for wilful neglect not corrected. A finding that a covered entity transmitted PHI from fingerprinting to a vendor without a BAA would typically fall in the 'reasonable cause' or 'wilful neglect' tiers if the covered entity had been notified of the risk and did not act.

FTC Health Breach Notification Rule: the non-HIPAA gap

HIPAA applies only to covered entities (health plans, health care clearinghouses, most health care providers) and their business associates. Consumer-facing health apps, wellness platforms, fitness trackers, and employer wellness programs that are not affiliated with a group health plan are outside HIPAA's scope. The FTC Health Breach Notification Rule (16 CFR Part 318) fills part of this gap for personal health record (PHR) vendors and related entities.

The FTC significantly expanded the HBNR's scope in a 2024 final rule, clarifying that health apps, connected devices, and similar services that collect health information are covered 'PHR-related entities' under the rule if they draw information from multiple sources or from a covered entity. A breach of individually identifiable health information - which the FTC has interpreted to include the unauthorised disclosure of health data to a third-party tracking vendor, including through device fingerprinting - triggers a notification obligation to affected consumers, the FTC, and in some cases the media.

The FTC's 2023 policy statement on health apps and connected devices (published in September 2023 and consistent with the 2024 HBNR rulemaking) makes explicit that sharing health information with tracking and analytics vendors without proper authorisation can constitute a 'breach of security' triggering notification. Non-covered health apps that use device fingerprinting and share the resulting data with third parties should assess HBNR compliance separately from any HIPAA analysis.

Practical compliance steps for covered entities deploying fingerprinting

  • Inventory all third-party tracking technologies on covered-entity digital properties, including device fingerprinting SDKs, and map which pages each technology touches.
  • Classify pages by authentication status and health-specificity. Authenticated pages and condition-specific unauthenticated pages require immediate BAA assessment; general public pages require a documented facts-and-circumstances analysis.
  • Request and execute a HIPAA-compliant BAA with each fingerprinting vendor before that vendor receives any PHI. Verify the BAA covers the Security Rule obligations for ePHI.
  • For vendors unwilling to sign a BAA, assess whether a server-side fingerprinting architecture can prevent PHI from reaching the vendor's systems, and document the assessment.
  • Update the covered entity's risk analysis under the Security Rule (45 CFR 164.308(a)(1)) to include tracking-technology data flows as a risk category.
  • Update the Notice of Privacy Practices to disclose the use of tracking technologies on digital properties and the conditions under which data may be shared with business associates under BAAs.
  • For non-covered health apps using fingerprinting, conduct a separate FTC Health Breach Notification Rule assessment.

How Benny the Doorman fits into a HIPAA-aware deployment

Benny's output is a risk verdict, not a general-purpose health-data pipeline. When deployed for fraud detection and account-takeover protection on authenticated patient portals, Benny produces signals that support security decisions - the same narrow purpose that covered entities are most likely to need on high-risk authenticated pages.

For covered entities, the BAA question is the first step. Before integrating any fingerprinting tool on authenticated pages or condition-specific unauthenticated pages, the covered entity's legal or compliance team should confirm whether the vendor will execute a HIPAA-compliant BAA. For deployments where the covered entity's backend handles fingerprinting logic server-side and limits what data reaches the vendor's infrastructure, the BAA scope may be narrower, but legal review is still required.

Benny does not replace a covered entity's HIPAA risk analysis or BAA process. It is an SDK that produces device-risk verdicts; the legal obligations surrounding PHI handling are the covered entity's responsibility, supported by their privacy counsel and HIPAA compliance officer.

Frequently asked questions

Is browser fingerprinting illegal under HIPAA?

HIPAA does not categorically prohibit browser or device fingerprinting on healthcare websites. However, OCR's December 2022 bulletin (updated March 2023) establishes that when a covered entity's website uses fingerprinting and the resulting data combines a device identifier with health-related browsing activity, that data is Protected Health Information. Using or disclosing PHI without a Business Associate Agreement or valid patient authorisation violates the Privacy Rule. The deployment is not inherently illegal; the compliance requirements depend on where fingerprinting is deployed and what data flows to which vendors.

Does HIPAA cover browser fingerprinting?

HIPAA's Privacy and Security Rules apply to PHI created, received, maintained, or transmitted by covered entities and their business associates. Browser fingerprinting on a covered entity's digital property can produce PHI when the device identifier is combined with health-related browsing activity. In that case, HIPAA's handling requirements apply to the resulting data, and any third-party fingerprinting vendor that receives that PHI must be a business associate under a signed BAA.

Is a device fingerprint PHI under HIPAA?

A device fingerprint is not automatically PHI. The Privacy Rule defines PHI as individually identifiable health information: information that identifies an individual or could reasonably be used to do so, and that relates to health conditions, treatment, or payment. A fingerprint hash in isolation does not relate to health. The PHI determination depends on context: a fingerprint collected on an authenticated patient portal, or on a URL that reveals a health condition or treatment, combined with the device identifier, likely constitutes PHI. A fingerprint collected on a generic homepage with no health context is lower risk, but covered entities should conduct a page-level analysis rather than a blanket determination.

Do I need a Business Associate Agreement for a fingerprinting vendor?

If the fingerprinting vendor's SDK or API receives PHI from a covered entity's digital property, the vendor is a business associate and a BAA is required before any PHI is transmitted to the vendor. This means covered entities must evaluate BAA requirements before deploying fingerprinting on authenticated pages or condition-specific unauthenticated pages, not after. If the vendor will not sign a HIPAA-compliant BAA, the covered entity must either restrict fingerprinting to contexts where PHI is not transmitted to the vendor, or implement a server-side architecture that prevents PHI from leaving the covered entity's environment.

Does HIPAA apply to unauthenticated web pages?

Yes, potentially. OCR's tracking-technology bulletin applies to both authenticated and unauthenticated pages. On authenticated pages (patient portals, member logins), the PHI determination is generally straightforward because the user's identity is known. On unauthenticated public pages, PHI status depends on whether the combination of the device identifier and the page context could reasonably identify a health condition. A public page for a specific condition clinic or a symptom-checker tool on a hospital website can still produce PHI even without a login. Covered entities should analyse each page category rather than treating unauthenticated pages as a blanket exemption.

What is the FTC Health Breach Notification Rule and how does it relate to fingerprinting?

The FTC Health Breach Notification Rule (16 CFR Part 318) applies to personal health record vendors and related entities that are not covered by HIPAA - consumer health apps, wellness platforms, and connected devices that collect health information. A 2024 FTC rulemaking expanded the rule's scope and clarified that unauthorised disclosure of health information to third-party tracking vendors, including through device-level tracking technologies, can trigger breach notification obligations. Non-covered health apps that use device fingerprinting and share data with analytics or advertising vendors should assess HBNR compliance separately from any HIPAA analysis.

Can I deploy fingerprinting on a healthcare site without a patient authorisation or BAA?

Only if the deployment is structured so that no PHI reaches the third-party fingerprinting vendor. This typically requires a server-side architecture where the covered entity's backend handles the fingerprinting logic and the vendor's SDK or API never receives PHI-bearing data. Even in that structure, a legal review is required to confirm that PHI does not flow to the vendor through any path. On authenticated pages or condition-specific unauthenticated pages where a standard client-side SDK deployment would transmit PHI to the vendor, either a BAA or a valid patient authorisation is required under 45 CFR 164.502(e).

What enforcement risk does OCR pose for healthcare tracking-technology violations?

OCR has announced multiple investigations since 2023 into covered entities that shared patient-identifying data with third-party web tracking vendors without BAAs. While not all of those investigations have resulted in published settlements naming specific fingerprinting technologies, the legal theory applied to pixels and analytics SDKs applies equally to device fingerprinting: transmitting PHI to a vendor without a BAA violates 45 CFR 164.502(e). Civil monetary penalties under 42 U.S.C. 1320d-5 range from $137 per violation for unknowing violations to approximately $1.9 million per violation category per year for wilful neglect. Criminal liability under 42 U.S.C. 1320d-6 is also possible where PHI is knowingly disclosed without authorisation.

Tooling

Benny the Doorman is built for this compliance posture.

Free, cookieless fingerprinting that defers to your consent management platform, runs on Indian infrastructure, and ships with a DPA addendum sized for the jurisdiction above.

Last reviewed 2026-07-12