The FTC Health Breach Notification Rule (16 CFR part 318), explained

The FTC’s rule requires health apps and other personal health record vendors outside HIPAA to give notice of breaches, which since the 2024 amendments expressly include unauthorized disclosures. Individuals hear within 60 calendar days of discovery, and the FTC at the same time when 500 or more people are affected.

The rule answers four questions for an organization that collects health information outside HIPAA: whether it is covered, what counts as a breach, who must be told and by when, and what the notice must say. The answers below come from the regulation text and the FTC’s 2024 final rule.

Who is covered

The rule implements section 13407 of the American Recovery and Reinvestment Act of 2009. It applies to foreign and domestic vendors of personal health records, PHR related entities and third party service providers that maintain information of U.S. citizens or residents, and it does not apply to HIPAA covered entities or to any entity to the extent it acts as a business associate of one [2]. The 2024 amendments were made in part to clarify the rule’s coverage of developers of many health applications [1].

Coverage turns on several linked definitions in 16 CFR 318.2 [2]:

  • Personal health record: an electronic record of PHR identifiable health information on an individual that has the technical capacity to draw information from multiple sources and is managed, shared and controlled by or primarily for the individual.
  • PHR identifiable health information: information about an individual’s health, care or payment for care that identifies the individual, or could reasonably be used to identify them, is created or received by a covered health care provider, health plan, employer or clearinghouse, and includes information provided by or on behalf of the individual.
  • Covered health care provider: includes any entity furnishing health care services or supplies.
  • Health care services or supplies: any online service, such as a website, mobile application or internet-connected device, that provides mechanisms to track diseases, conditions, diagnoses, treatment, medications, vital signs, symptoms, bodily functions, fitness, fertility, sexual health, sleep, mental health, genetic information or diet, or provides other health-related services or tools.
  • Vendor of personal health records: a non-HIPAA entity that offers or maintains a personal health record. A PHR related entity offers products or services through the website or online service of a PHR vendor, or of a HIPAA covered entity that offers personal health records, or accesses unsecured PHR identifiable health information in a personal health record or sends it to one.

The FTC’s preamble gives examples. A purely informational health website is not a personal health record. A logged-in symptom tracker is an electronic record of PHR identifiable health information but is not a personal health record if the consumer is its only source. The same tracker becomes one if it also draws data from another source, such as geolocation through an API or information from a data broker. The FTC calls coverage a fact-intensive inquiry [1].

In our reading, because coverage depends on the product, not the industry, an organization outside healthcare can be in scope if it offers such a tool and is not acting under HIPAA. The preamble notes that when it was published, the FTC had brought two enforcement actions under the rule, against GoodRx Holdings, Inc. and against Easy Healthcare Corp., developer of the Premom ovulation-tracking app [1].

What counts as a breach

A breach of security is the acquisition of unsecured PHR identifiable health information in a personal health record without the individual’s authorization. Unauthorized access is presumed to be acquisition unless the entity has reliable evidence that there was not, or could not reasonably have been, unauthorized acquisition. A breach includes unauthorized acquisition that results from a data breach or from an unauthorized disclosure [2]. The 2024 amendments revised the definition to make clear that both are covered [1], so sharing data with a third party without the individual’s authorization can be a breach even where no system was attacked.

“Unsecured” means information not protected by a technology or method specified in HHS guidance under section 13402(h)(2) of the Recovery Act [2].

Who must be told, and when

  • Individuals: each affected U.S. citizen or resident, without unreasonable delay and no later than 60 calendar days after discovery [2].
  • Media: prominent media outlets serving a state or jurisdiction where 500 or more residents are affected, on the same timetable [2].
  • The FTC, 500 or more individuals: contemporaneously with the notice to individuals [2].
  • The FTC, fewer than 500: a log of such breaches may be sent annually, no later than 60 calendar days after the end of the calendar year [2].
  • Third party service providers: notify the official designated in their contract, or a senior official, at the vendor or PHR related entity, identify affected customers, and obtain acknowledgment that the notice was received, within the same 60-day limit [2].

A breach is treated as discovered on the first day it is known, or reasonably should have been known, to any employee, officer or other agent other than the person committing it. The entity bears the burden of showing that notices were made as required, and notice is delayed if a law enforcement official determines it would impede a criminal investigation or damage national security [2].

How notice is given and what it says

Written notice goes to the last known address, or by electronic mail if the individual has specified it as the primary method. In this rule, electronic mail means email combined with a text message, within-application messaging or an electronic banner, and electronic notices must be clear and conspicuous. If contact information is insufficient or out of date for ten or more people, substitute notice is required: a conspicuous 90-day posting on the home page or notice in major print or broadcast media, with a toll-free number active for at least 90 days [2].

Under 16 CFR 318.6, the notice must be written so that it is easy to understand and include, to the extent possible [2]:

  • what happened, with the dates of the breach and of discovery, and the identity of any third parties that acquired the information, if known;
  • the types of information involved, which may include a person’s use of a health-related app or a device identifier (in combination with another data element);
  • steps individuals should take to protect themselves;
  • what the entity is doing to investigate, mitigate harm and protect against further breaches; and
  • at least two contact methods from: toll-free number, email address, website, within-application, or postal address.

Enforcement and relationship to other law

A violation is treated as a violation of a rule under section 18 of the FTC Act on unfair or deceptive acts or practices, subject to civil penalties adjusted for inflation [2]. The rule preempts state law as set out in section 13421 of the Recovery Act, and it stops applying to breaches discovered after the effective date of regulations under any new legislation that sets notification requirements for the same entities [2]. HIPAA entities follow the HHS breach notification rule instead; see our HIPAA breach notification checklist.

The eCFR text dated November 1, 2026 shows part 318 as amended in 2024 [2]. This explainer describes the rule; it is not legal advice, and organizations should confirm with counsel whether their products are covered.

Moraph’s teams help organizations with work like this. See our solutions.

Spotted an error? Tell us and we will check it and correct the explainer where needed.

  • FTC
  • Health Breach Notification Rule
  • 16 CFR part 318
  • health apps
  • personal health records
  • breach notification
  • consumer health data