How to Respond to a Tracking Pixel PHI Disclosure Incident
A tracking pixel disclosure incident can occur when a website or app sends information to an analytics, advertising, or other third-party service without proper authorization. Whether the event triggers the HIPAA breach notification rule depends on what information was sent, whether it was protected health information (PHI), and the circumstances of the disclosure.
Act promptly to stop further transmissions, preserve evidence, assess the facts, and involve your privacy, security, and legal teams. HHS’s tracking-technology guidance notes that a federal court vacated part of the guidance concerning IP addresses linked to visits to certain unauthenticated public webpages; that fact pattern alone should not be treated as automatically establishing a HIPAA violation. HHS guidance on online tracking technologies
How should you contain a tracking pixel disclosure incident?
Stop the suspected disclosure while preserving information needed to investigate it. Disable the pixel, tag, or affected integration, or block its network requests; pause related campaigns or scripts if needed. Check other pages, apps, tag managers, and environments for the same code so the transmission does not continue elsewhere.
Coordinate changes with your incident-response team. Preserve relevant logs, configuration files, tag-manager history, network records, and system snapshots before making changes that could erase evidence. Record when the issue was discovered, who took each action, and when transmissions stopped. HHS identifies responding to known or suspected security incidents, mitigating harmful effects, and documenting the incident and its outcome as Security Rule requirements. HHS guidance on Security Rule incident procedures
Contact the tracking vendor through your incident-response and legal channels. Ask it to preserve relevant logs and records, explain what it received and retained, identify any onward disclosures, and describe available containment or deletion steps. Document the request and the vendor’s response; do not assume a vendor’s deletion statement by itself resolves the incident.
What information did the tracking pixel collect and transmit?
Determine what the specific pixel implementation sent, rather than relying on a generic description of the vendor’s product. Review the pixel code, tag-manager settings, network requests, vendor documentation, and available server, browser, and vendor logs. If evidence is incomplete, document what is unknown and how that limits your conclusions.
Depending on the implementation, transmissions may include page URLs and query strings, referrer URLs, event names, button clicks, form values, appointment or portal activity, timestamps, IP addresses, cookie or device identifiers, and account or patient identifiers. Establish which fields were actually sent, when they were sent, how many people may be affected, and whether the vendor or another recipient stored, viewed, used, or shared them.
Ask the vendor and relevant internal teams to preserve evidence that could answer these questions, including transmission logs, access records, retention information, and documentation of any downstream recipients. HHS recommends documenting incident discovery, affected systems and data, response and mitigation activities, forensic data collected, and outcomes. HHS OCR guidance on documenting security incidents
How do you determine whether the disclosed data was PHI?
Assess the data in context. HIPAA applies to individually identifiable health information held or transmitted by a covered entity or business associate, subject to HIPAA’s definitions and exclusions. Consider whether the transmitted information identifies a person, relates to that person’s health, care, or payment for care, and connects the person to your organization or its services.
A patient portal identifier, appointment details, a form submission, or a URL containing patient-specific information may provide a direct link to an individual and healthcare activity. Consider the information sent in combination: a field that seems non-identifying by itself may become identifiable when combined with an account ID, cookie, or other data. Do not treat every IP address or visit to a health-related public webpage as PHI automatically. HHS’s current tracking-technology page describes the scope of the court’s 2024 vacatur concerning one specific IP-address-and-public-page theory; evaluate other facts and applicable HIPAA requirements separately. HHS tracking-technology guidance and notice of court vacatur
Also determine whether the information was encrypted using a method recognized by HHS for rendering PHI unusable, unreadable, or indecipherable to unauthorized persons. The HIPAA breach notification rule concerns breaches of unsecured PHI, so the encryption status and the exact data exposed can affect the notification analysis. HHS Breach Notification Rule overview
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free TodayHow do you conduct and document a HIPAA breach risk assessment?
If unsecured PHI was impermissibly disclosed, HIPAA generally presumes a breach unless an exception applies or the covered entity or business associate demonstrates a low probability that the PHI was compromised. You may conduct and document a breach risk assessment to evaluate that probability, or provide required notifications without first performing that assessment. HHS Breach Notification Rule guidance
At a minimum, assess and document these four factors:
- Nature and extent of the PHI: Identify the data elements, identifiers, sensitivity, volume, and likelihood of re-identification.
- Recipient: Identify who received or could access the information, and whether that recipient was authorized, bound by a business associate agreement (BAA), or subject to other controls.
- Acquisition or viewing: Determine whether the information was actually received, accessed, viewed, retained, or further disclosed, using available evidence.
- Mitigation: Document steps taken to reduce the risk, such as stopping transmission, restricting access, or obtaining reliable evidence about deletion or non-use.
Keep the evidence, analysis, reasoning, decision, and approvals together. Record uncertainties and explain how they affect the assessment; do not assume that a vendor’s promise to delete data proves that it was never accessed or retained. HHS requires regulated entities to be able to demonstrate that required notifications were made or that notification was not required. HHS guidance on breach documentation and burden of proof
Which individuals and authorities must be notified?
If the incident is a breach of unsecured PHI requiring notification, the covered entity must notify affected individuals without unreasonable delay and no later than 60 calendar days after discovery. The notice must include, to the extent possible, a description of what happened and the information involved, steps individuals can take to protect themselves, what the organization is doing to investigate and mitigate the incident, and contact information for questions. A business associate that discovers a breach must notify the covered entity without unreasonable delay and no later than 60 days after discovery; the BAA may set a shorter deadline. HHS Breach Notification Rule guidance
The covered entity must also notify the Secretary of HHS through OCR. For a breach affecting 500 or more individuals, report it without unreasonable delay and no later than 60 calendar days after discovery. For a breach affecting fewer than 500 individuals, the report is due within 60 days after the end of the calendar year in which it was discovered. HHS OCR breach-reporting instructions
If a breach affects more than 500 residents of a state or jurisdiction, the covered entity must also notify prominent media outlets serving that area, without unreasonable delay and no later than 60 calendar days after discovery. A business associate should promptly provide the covered entity with available facts needed to identify affected individuals and prepare notifications. HHS guidance on individual, media, and Secretary notification
What corrective actions can prevent another disclosure?
After containment, review how the pixel was selected, configured, approved, and monitored. Remove unnecessary tracking code; limit or block data fields and page events sent to third parties; and test website and app changes to confirm what leaves the organization’s systems. Consider whether tracking technology is appropriate on patient portals, appointment flows, or pages that may process individually identifiable health information.
Review vendor relationships and permissions. If a vendor meets HIPAA’s definition of a business associate because it creates, receives, maintains, or transmits PHI on behalf of a covered entity or business associate, establish the required BAA and confirm that the disclosure is otherwise permitted. A contract labeled as a BAA does not, by itself, make a vendor a business associate. If a vendor is not a business associate, do not assume that a BAA is required in every relationship; evaluate the actual role, data, and applicable Privacy Rule permissions. HHS guidance on tracking vendors and business associate agreements
Update your risk analysis, policies, vendor reviews, and incident-response procedures based on the findings. Review relevant access controls, audit logging, and safeguards for electronic PHI, and train workforce members on the organization’s tracking-technology approval and escalation processes. The Security Rule requires risk analysis and risk management, as well as procedures to identify and respond to security incidents, mitigate harmful effects, and document incidents and outcomes. HHS summary of the HIPAA Security Rule
In summary, contain the transmission, establish what the pixel collected and who received it, determine whether the information was PHI, and document the breach risk assessment and notification decision. Then strengthen technical controls, vendor oversight, and review processes to reduce the risk of another impermissible disclosure.
FAQs
When does tracking pixel data qualify as PHI?
Tracking pixel data may qualify as PHI when it identifies an individual, relates to that person’s health, care, or payment for care, and is held or transmitted by a HIPAA covered entity or business associate. Assess the complete transmission and its context, including whether URLs, portal activity, appointment details, or identifiers connect a person to healthcare information. An IP address paired with a visit to an unauthenticated public health webpage does not automatically establish PHI under the specific theory addressed by the court’s vacatur of part of HHS’s guidance. HHS online tracking guidance
How quickly must affected individuals be notified after a reportable breach?
Notify affected individuals without unreasonable delay and no later than 60 calendar days after discovering a reportable breach of unsecured PHI. The 60-day limit is an outer deadline, not a reason to delay notification unnecessarily. HHS Breach Notification Rule guidance
Does a tracking pixel vendor need a business associate agreement?
A BAA is required when the vendor meets HIPAA’s definition of a business associate by handling PHI on behalf of a covered entity or business associate. The answer depends on the actual relationship and data flow: the mere presence of tracking software or a contract labeled as a BAA does not establish business associate status. Separately, a disclosure of PHI must have an applicable Privacy Rule permission or authorization. HHS guidance on tracking technologies and BAAs
What records should be preserved during the investigation?
Preserve pixel and tag-manager configurations, change history, network requests, relevant server and vendor logs, access records, affected URLs and events, vendor communications, and documentation of containment and mitigation. Also retain the incident timeline, affected systems and data, risk assessment, notification decisions, and corrective actions. HHS identifies forensic data, response and mitigation activities, root-cause analysis, and incident outcomes as useful elements of security-incident documentation. HHS OCR guidance on documenting security incidents
Table of Contents
- How should you contain a tracking pixel disclosure incident?
- What information did the tracking pixel collect and transmit?
- How do you determine whether the disclosed data was PHI?
- How do you conduct and document a HIPAA breach risk assessment?
- Which individuals and authorities must be notified?
- What corrective actions can prevent another disclosure?
- FAQs
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free Today