# Checklist: getting a non-HIPAA health app ready for the FTC Health Breach Notification Rule

Thirteen steps for health apps, connected devices and their service providers outside HIPAA: whether the rule reaches you, why unauthorized sharing counts as a breach since 2024, the 60-day limit, and notice to people, the FTC and the media.

Checklist · Healthcare · Data & AI. Published November 14, 2026. Last reviewed November 14, 2026.

## The rule after the 2024 amendments

The Health Breach Notification Rule, 16 CFR part 318, applies to vendors of personal health records, PHR related entities and their third party service providers. It does not apply to HIPAA covered entities, or to any entity to the extent it acts as a business associate of one [1]. The FTC amended the rule in a final rule published on May 30, 2024 and effective July 29, 2024. The amendments clarify that the rule covers developers of many health apps, explain what it means for a personal health record to draw information from multiple sources, make clear that a breach of security includes unauthorized disclosures as well as data security breaches, modernize how notice may be given, expand what notices must say and change the timing for notifying the FTC [2]. The preamble describes the FTC’s first enforcement actions under the rule, brought in 2023, which ended in settlements that required civil penalties of $1.5 million and $100,000 [2].

## Using the steps

Steps 1 to 4 decide whether and how the rule applies; steps 5 to 8 prepare for a breach before it happens; steps 9 to 13 cover the notices. Citations are to the eCFR text current to November 12, 2026 [1] and to the FTC’s 2024 final rule [2] and business guidance [3]. Where a step is our suggestion, it says so. The owner under each step is a typical role, not one the rule names, unless the step says the rule names it. This page explains the rule; it is not legal advice, and state breach and health privacy laws may also apply.

Moraph’s teams help organizations with work like this. [See our solutions](https://www.moraph.com/solutions).

## The checklist

1. **For each product, confirm whether the company is a HIPAA covered entity or is acting as a business associate when it handles the data.** (Privacy counsel) Section 318.1(a) excludes HIPAA covered entities and any entity to the extent it engages in activities as a business associate [1]. The FTC’s guidance says HIPAA governs health records for most hospitals, doctors’ offices and insurers, while many companies behind fitness trackers, diet apps and connected blood pressure cuffs are not covered by HIPAA [3]. Checking product by product is our suggestion, since a company can act as a business associate for one service and not another.
2. **Test whether the product is a personal health record: an electronic record of identifiable health information that can draw information from multiple sources and is managed, shared and controlled by or primarily for the individual.** (Product lead, with privacy counsel) Section 318.2 defines personal health record and PHR identifiable health information [1]. The preamble says a product counts if it has the technical capacity to draw any information from multiple sources, even if only one source supplies health information, and gives the example of a health advice website that takes consumer inputs and collects geolocation data through an API [2].
3. **Check whether the health information comes from a covered health care provider, which now includes online services that track health and fitness.** (Privacy counsel) Section 318.2 defines covered health care provider to include any entity furnishing health care services or supplies, and defines those to include any website, app or connected device that tracks diseases, conditions, diagnoses, medications, vital signs, symptoms, bodily functions, fitness, fertility, sexual health, sleep, mental health, genetic information or diet, among others. PHR identifiable health information includes information provided by or on behalf of the individual [1].
4. **Record which role the company plays: vendor of personal health records, PHR related entity or third party service provider.** (Legal) Section 318.2 defines all three. A PHR related entity includes one that offers products or services through a vendor’s online services, or that accesses unsecured PHR identifiable health information in a personal health record or sends it to one [1]. The duties in section 318.3 differ by role [1].
5. **List every place the product sends health information to another company, including software development kits, analytics and advertising tools, and confirm each one is authorized by the consumer.** (Privacy engineering) The definition of breach of security in section 318.2 includes an unauthorized acquisition that occurs as a result of an unauthorized disclosure [1]. The preamble gives the example of an app whose disclosures let third parties use the data for their own purposes, such as targeted advertising, and says those disclosures are not authorized because they violate the app’s privacy representations and are inconsistent with consumer expectations [2]. The data flow inventory is our suggestion.
6. **If the company is a vendor or PHR related entity, tell its service providers that it is covered, and name in each written contract the official who should receive breach notices.** (Vendor management) Section 318.3(b) requires vendors and PHR related entities to notify their third party service providers of their status. A service provider must notify the official designated in the written contract, or a senior official if none is named, obtain acknowledgment, and identify each affected customer [1].
7. **Set an escalation path so any employee or agent who learns of a possible breach reports it at once.** (Security operations lead) Section 318.3(c) treats a breach 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 [1]. The escalation path is our suggestion, so the 60-day limit does not start before the incident team knows.
8. **Keep access logs good enough to show whether data that was accessed without authorization was actually acquired.** (Security engineering) Under section 318.2, unauthorized acquisition is presumed when there is unauthorized access, unless the company has reliable evidence that there has not been, or could not reasonably have been, unauthorized acquisition [1]. Which logs to keep is our suggestion.
9. **Send notices to individuals, and to the media where required, without unreasonable delay and no later than 60 calendar days after discovery, and keep the evidence.** (Incident response lead, with legal) Section 318.4(a) sets the 60-day outer limit for notices to individuals, to the media and from service providers. Section 318.4(c) puts the burden on the company to show every notice was made as required, including evidence for any delay, and section 318.4(d) provides for delay when a law enforcement official determines notice would impede a criminal investigation or damage national security [1].
10. **Notify the FTC: at the same time as individual notice when 500 or more people are affected, or in an annual log within 60 calendar days after the year ends for smaller breaches.** (Legal) Section 318.4(b) and section 318.5(c) set the timing and say notices go to the FTC according to instructions on its website [1]. The FTC’s guidance says to use its online Notice of Breach of Health Information form [3].
11. **Choose the notice method for each affected person: written notice to the last known address, or electronic mail if the person chose it as the primary method, with substitute notice when contact details for ten or more people are insufficient or out of date.** (Customer communications) Section 318.5(a) sets the methods, including notice to next of kin of a deceased individual where authorized, and substitute notice by a conspicuous 90-day posting on the home page or in major media, with a toll-free number active for at least 90 days. Section 318.2 defines electronic mail as email combined with a text message, in-app message or electronic banner, and sets what makes a notice clear and conspicuous [1].
12. **Prepare a notice template with the five contents the rule requires.** (Customer communications, with legal) Section 318.6 requires each notice to include, to the extent possible, a description of what happened, including the dates of the breach and its discovery and any third parties that acquired the information; the types of information involved; steps individuals should take; what the company is doing; and at least two contact methods from a toll-free number, email address, website, in-app channel or postal address [1]. Drafting the template in advance is our suggestion.
13. **Line up notice to prominent media outlets for any state or jurisdiction where 500 or more residents are affected.** (Communications lead) Section 318.3(a)(3) and section 318.5(b) require it [1]. A violation of the rule is treated as a violation of a trade regulation rule under the FTC Act and is subject to civil penalties, under section 318.7 [1].

## Sources

1. Electronic Code of Federal Regulations. 16 CFR part 318, Health Breach Notification Rule (eCFR current to November 12, 2026; checked November 14, 2026). <https://www.ecfr.gov/current/title-16/part-318> Checked November 14, 2026.
2. Federal Trade Commission, Federal Register (via GovInfo). Health Breach Notification Rule (final rule, 89 FR 47028, May 30, 2024). <https://www.govinfo.gov/content/pkg/FR-2024-05-30/html/2024-10855.htm> Checked November 14, 2026.
3. Federal Trade Commission. Complying with FTC’s Health Breach Notification Rule (business guidance), Internet Archive copy captured November 9, 2026. <https://web.archive.org/web/20261109075432/https://www.ftc.gov/business-guidance/resources/complying-ftcs-health-breach-notification-rule-0> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/checklist-ftc-health-breach-notification-rule-health-apps>
Publisher: Moraph Insights
