Join our Newsletter — 33% off our NHI Course
Home› Guides› FTC Health Breach Notification Rule Guide: Health Apps…
Guide Regulations & Frameworks

FTC Health Breach Notification Rule Guide: Health Apps and PHR Vendors

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 15 min read
On this page

Health apps, wearables and connected devices that sit outside HIPAA are still bound by a federal breach notification duty, and the Federal Trade Commission has shown it treats sharing health data with advertisers as a breach. The Health Breach Notification Rule (16 CFR Part 318) requires vendors of personal health records, PHR related entities and their service providers to notify individuals, the FTC and sometimes the media after a breach of unsecured health information. This guide explains scope, the 2024 amendments, deadlines, notice content, penalties and the engineering controls that keep a product out of trouble. It is written for security, privacy and engineering leads at digital health companies and the vendors that serve them. Status checked on 27 October 2026 against the eCFR text and FTC pages.

Key takeaways

  • HIPAA's gap is covered. The rule applies to vendors of personal health records and PHR related entities that are not HIPAA covered entities or business associates, foreign or domestic, holding information of US citizens or residents.
  • A breach includes unauthorised disclosure. Since the 2024 amendments a "breach of security" covers both security incidents and disclosures the user did not authorise, such as sending health data to an ad platform through an SDK or pixel.
  • Sixty calendar days is the outer limit. Notice to individuals must go without unreasonable delay and no later than 60 calendar days after discovery; for 500 or more people the FTC is told at the same time.
  • Penalties are per violation. A violation is treated as a violation of an FTC trade regulation rule, with civil penalties currently up to $53,088 per violation.
  • Machine data flows are the risk. Most enforcement has turned on tracking code, API integrations and service accounts moving data to third parties, so the inventory of non-human data paths is the core compliance artefact.

Scope: who and what is covered

The rule implements section 13407 of the American Recovery and Reinvestment Act of 2009. Section 318.1 applies it to foreign and domestic vendors of personal health records, PHR related entities and third party service providers that maintain information of US citizens or residents, irrespective of the jurisdictional tests in the FTC Act. It does not apply to HIPAA covered entities, or to an entity acting as a business associate of one. If your organisation is under HIPAA, see the HIPAA Breach Notification Rule Guide instead.

Role (16 CFR 318.2)Definition in briefTypical exampleWho it notifies
Vendor of personal health recordsA non-HIPAA entity that offers or maintains a personal health recordA fitness or diet app combining user entries with data synced from a wearable or another sourceIndividuals, FTC, media (500+ in a state)
PHR related entityA non-HIPAA entity that offers products or services through a PHR vendor's or covered entity's online services, or that accesses or sends unsecured PHR identifiable health information to a PHRA wearable maker whose device sends data into health appsIndividuals, FTC, media (500+ in a state), for data obtained through its products
Third party service providerProvides services to a vendor or related entity and as a result accesses, holds or uses unsecured PHR identifiable health informationCloud hosting, billing, analytics or debt collection supplierThe vendor's designated official, with acknowledgment of receipt

The key definitions

  • Personal health record: an electronic record of PHR identifiable health information that can draw information from multiple sources and is managed, shared and controlled by or primarily for the individual. The FTC's business guidance says an app is likely covered even if some users never connect a second source, because the capability is what counts.
  • PHR identifiable health information: health information that identifies, or can reasonably be used to identify, an individual, including information provided by or on behalf of the individual.
  • Health care services or supplies: added in 2024 and explicitly includes online services such as websites, apps and connected devices that track conditions, medications, vital signs, fertility, sleep, genetic information and similar items. This is how a consumer app becomes a "covered health care provider" for the purposes of the definition.
  • Unsecured: not protected by a technology or methodology specified by HHS guidance. HHS names encryption consistent with NIST SP 800-111 for data at rest, SP 800-52, SP 800-77 or SP 800-113 for data in motion, keys held separately from the data, and destruction per NIST SP 800-88.

Key obligations

What counts as a breach

Section 318.2 defines a breach of security as acquisition of unsecured PHR identifiable health information without the individual's authorisation, including both data security incidents and unauthorised disclosures. Unauthorised acquisition is presumed to include unauthorised access unless the entity has reliable evidence otherwise. The FTC's guidance gives three examples: sharing users' medical details with an ad network for targeted marketing without consent (even without names, if people could still be identified), accidentally sending health information to a social media platform, and losing an unencrypted laptop.

Who must be told, when and how

RecipientTriggerDeadlineMethodSource
Each affected individualAny breach of securityWithout unreasonable delay, no later than 60 calendar days after discoveryWritten notice to last known address; email (plus text, in-app or banner) only if the individual chose email as primary contact318.3, 318.4, 318.5
FTC (500 or more people)Breach involving 500+ individualsAt the same time as notice to individualsOnline "Notice of Breach of Health Information" form on ftc.gov318.4(b), FTC guidance
FTC (fewer than 500)Breach involving fewer than 500Log, then submit within 60 days after the end of the calendar yearSame FTC form318.4(c)
Prominent media outlets500+ residents of a single state affectedWithin 60 calendar days of discoveryOutlets serving that state318.3, 318.5
Vendor or related entity (by a service provider)Service provider discovers a breachWithin 60 calendar days of discoveryNotice to the designated official, acknowledgment obtained, affected customers identified318.3(c), 318.4
  • Discovery: a breach is treated as discovered on the first day it is known, or reasonably should have been known, to the entity. Knowledge of any employee or agent other than the person who committed the breach counts. A tracker that has been leaking for a year is "discovered" when someone should reasonably have noticed, not when legal is told.
  • Substitute notice: if contact details are insufficient or out of date for 10 or more people, post a conspicuous notice on the home page for 90 days or use major print or broadcast media, with a toll-free number active for at least 90 days.
  • Burden of proof: the entity must be able to show that notices were made and that any delay was reasonable.
  • Law enforcement delay: where an official determines notice would impede a criminal investigation or harm national security, notice is delayed in the manner set out in 45 CFR 164.528(a)(2).
  • Service provider status: vendors and related entities must tell their service providers that they are covered, so the provider knows its notification duty applies.

Content of the notice (318.6)

  1. A brief description of what happened, with the date of the breach and of discovery, and the full name or identity (or a description where naming creates risk) of any third parties that acquired the information.
  2. The types of unsecured information involved, such as health conditions, medications, location or account details.
  3. Steps individuals should take to protect themselves.
  4. What the entity is doing to investigate, mitigate harm and protect against further breaches.
  5. Contact procedures, including at least two of: toll-free number, email address, website, in-application contact or postal address.

The notice must be in plain language and "clear and conspicuous" as section 318.2 defines it. A drafting starting point is the Customer Breach Notification Letter Template, adapted to these five elements.

Timeline and current status

DateEvent
25 August 2009Rule issued (74 FR 42980)
24 September 2009Applies to breaches discovered on or after this date (318.8)
1 February 2023FTC announces its first enforcement action under the rule, against GoodRx
Before April 2024Action against Easy Healthcare, publisher of the Premom app, later cited by the FTC as a rule violation
26 April 2024FTC announces final amendments, approved 3-2
30 May 2024Amendments published (89 FR 47054); effective 60 days after publication, shown in the eCFR as 29 July 2024
17 January 2025Current inflation-adjusted maximum of $53,088 per violation applies to penalties assessed after this date (16 CFR 1.98)

Section 318.9 contains a sunset clause: if Congress enacts new breach notification requirements for these entities, the rule stops applying to breaches discovered on or after the effective date of the implementing regulations. No such replacement was in force when this page was checked. Penalty figures are adjusted annually, so confirm the current figure in 16 CFR 1.98 before relying on it.

Enforcement and penalties

Under section 318.7 a violation is treated as a violation of a rule under section 18 of the FTC Act regarding unfair or deceptive acts or practices, and the FTC enforces it with its FTC Act powers. That makes civil penalties available, currently up to $53,088 per violation under 16 CFR 1.98. Rule cases often run alongside Section 5 deception counts; see the FTC Act Section 5 Data Security Guide.

  • GoodRx (February 2023): the FTC alleged the company shared prescription and health condition information with Facebook, Google, Criteo, Branch and Twilio despite promising not to, and failed to notify consumers, the FTC and the media. The proposed order included a $1.5 million civil penalty, a permanent ban on sharing health data for advertising, a requirement to direct third parties to delete data, retention limits and a privacy programme. The FTC described it as the first action under the rule.
  • Easy Healthcare (Premom): the FTC cited this case, alongside GoodRx, in announcing the 2024 amendments as an earlier rule violation involving an ovulation tracking app.

The lesson from both cases is that the "breach" was a deliberate integration, not an attacker. Marketing SDKs and pixels were configured to send events that revealed health information.

What it means for AI agents and non-human identities

The rule does not mention AI or machine identities, but its definitions apply to any data flow a product makes. In practice the parties that "acquire" health data without authorisation are usually software: SDKs, server-side event APIs, data pipelines and, increasingly, AI services.

  • Tracking SDKs and conversion APIs: each one authenticates with an app ID, pixel ID or API token. Inventory them as non-human identities with an owner, a data scope and a consent condition. The Cookie and Tracking Technology Compliance Guide covers tag governance.
  • LLM and AI agent integrations: sending symptom logs or chat transcripts to a third-party model API is a disclosure. If users did not authorise it, and the data is identifiable and unsecured in the HHS sense, it can fit the breach definition. Check provider retention and training terms, and record the decision.
  • Service accounts and API keys: a leaked cloud key to a bucket holding PHR data is a classic security breach. Unauthorised access is presumed to be acquisition, so logs must be good enough to rebut the presumption. See the API Key Management Guide.
  • Wearable and device integrations: OAuth tokens that let a device maker push data into your app, or your app pull from theirs, define the PHR related entity relationship. Scope tokens to the minimum health data needed and log every grant.
  • Agent actions: an agent that can export or email records needs the same least privilege and audit trail as a human operator, because its knowledge of an event may count as the entity's knowledge for discovery.

Compliance steps

  1. Classify the organisation. Decide in writing whether you are a HIPAA covered entity, business associate, PHR vendor, PHR related entity or third party service provider, product by product. The multiple sources test usually decides PHR vendor status.
  2. Map health data flows. Build a data map of every system, SDK, API and service account that receives PHR identifiable health information, including derived signals (for example, an event named after a medication). See the Data Mapping and ROPA Guide.
  3. Remove or gate third-party disclosures. Turn off health-revealing events to advertising platforms by default; where sharing is needed, obtain authorisation the user actually gives, and record it.
  4. Secure the data in the HHS sense. Encrypt at rest and in transit to the NIST publications named in HHS guidance, keep keys separate, and destroy media per SP 800-88, so lost devices or exposed storage may not be "unsecured".
  5. Write service provider clauses. Tell providers you are covered, name your designated official, and require notice within the 60 day window with acknowledgment.
  6. Build the notification runbook. Pre-draft the five-element notice, the media list by state, substitute notice text, the FTC form process and the under-500 annual log. Rehearse with a tabletop that starts from a misconfigured SDK.
  7. Evidence everything. Keep the decision log, timestamps for discovery and notice, and forensic evidence, since the entity bears the burden of proof.

Decision guidance

SituationLikely positionAction
App only stores one source of user-entered data and cannot import any otherPossibly not a PHR; take adviceDocument the analysis; revisit when an integration is added
App syncs a wearable or imports lab resultsLikely PHR vendorFull programme above
Startup acting for a hospital under a BAABusiness associate, HIPAA applies to that activityFollow HIPAA notification for that activity; check any direct consumer product separately
Analytics vendor receiving app eventsThird party service providerNotify the client's designated official; get acknowledgment
Lost laptop with encrypted, key-separated dataData likely not "unsecured"Record encryption evidence; notification may not be triggered

Small companies should start with steps 1 to 3, because most exposure comes from default tracking configuration. Larger groups with many apps need a central register of SDKs and tokens per app, with release gates that block new third-party destinations without privacy review.

Common failure patterns

  • Assuming "not HIPAA" means "no rules": the HBNR exists precisely for non-HIPAA health products.
  • Treating ad sharing as marketing, not a breach: GoodRx shows the FTC treats unauthorised disclosure to platforms as a breach requiring notice.
  • Event names that leak health facts: pixel events or URLs containing condition or drug names reveal health information even without a name field.
  • No logs to rebut the presumption: without access logs on storage and service accounts, unauthorised access is presumed to be acquisition. Scope then defaults to everything the credential could reach.
  • Silent suppliers: contracts that do not tell providers they are serving a covered entity, so the provider never notifies.
  • Clock starts late: counting 60 days from legal sign-off rather than from when the issue was, or reasonably should have been, known.

Detection and measurement

  • Monitor: outbound network destinations from apps and servers (allow-list per environment), SDK version and configuration changes, storage access logs, API key usage anomalies and OAuth grants to device partners.
  • Metric: percentage of third-party destinations receiving health data that have a documented authorisation basis (target 100%).
  • Metric: median days from first indicator to classification decision (well inside 60).
  • Metric: percentage of PHR data stores encrypted to the HHS named methods with separate keys.
  • Metric: percentage of service provider contracts with a notification clause and named designated official.
  • Metric: number of release builds blocked for new, unreviewed data destinations.

Framework mapping

Rule elementNIST CSF 2.0NIST SP 800-53 Rev 5
Know your legal status and dutiesGV.OC-03PT-2
Data flow inventoryID.AM-07PT-3
Secured (encrypted) dataPR.DS-01, PR.DS-02SC-28, SC-8
Supplier notification dutiesGV.SC-05, GV.SC-07SA-9, SR-3
Access logging to rebut presumptionDE.CM-03AU-2, AC-6
Notification to individuals, FTC, mediaRS.CO-02, RS.CO-03IR-6, IR-8

Practitioner checklist

  • Record, per product, whether you are a PHR vendor, PHR related entity, service provider or HIPAA entity.
  • Inventory every SDK, pixel, conversion API, AI service and service account that touches health data, with an owner.
  • Remove health-revealing events and parameters from advertising and analytics destinations.
  • Encrypt PHR data to the NIST methods named by HHS and keep keys separate.
  • Log access to PHR stores and key usage well enough to rebut the access presumption.
  • Put notification clauses and a designated official in every service provider contract.
  • Pre-draft the 318.6 notice, the state media list and substitute notice text.
  • Run the under-500 annual log and the FTC form process with named owners.
  • Check 16 CFR 1.98 each year for the current penalty figure.

Standards and references

Related NHI Mgmt Group resources: Health Data Privacy Beyond HIPAA Guide (My Health My Data) · HIPAA Breach Notification Rule Guide · Breach Notification Laws by Country Guide · Healthcare Cyber Regulation Map. This guide summarises the FTC Health Breach Notification Rule as published in the eCFR on 27 October 2026 and is not legal advice.

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.