Skip to content
HIPAA ComplianceConsulting

HIPAA Guide

HIPAA Compliance for Mobile Health Apps

Whether HIPAA, the FTC Health Breach Notification Rule, or both apply to your health app — and the mobile-specific risks: device storage, push notifications, analytics SDKs and tracking.

5 min read Reviewed

The first question for any health app is not "how do we comply with HIPAA?" but "does HIPAA apply at all?" The answer depends on who the app is built for and on whose behalf it handles data — not on how sensitive the data is. Two apps that collect identical blood pressure readings can sit under completely different legal regimes.

This guide covers the applicability question, the FTC's parallel rules for consumer apps, and the mobile-specific security issues that come up in nearly every app review.

Key points

  • HIPAA applies when the app is offered by, or on behalf of, a covered entity or business associate.
  • Consumer health apps outside HIPAA may be subject to the FTC Health Breach Notification Rule and the FTC Act.
  • Analytics and advertising SDKs are a leading source of unintended health data disclosure.
  • OCR's tracking technology guidance was partly vacated by a federal court in 2024; verify current guidance.

Does HIPAA apply to your app?

HHS has published scenarios explaining when app developers are business associates. The core principle: if a covered entity (or its business associate) contracts with you to provide the app, or the app exchanges PHI with the covered entity on its behalf, HIPAA applies. If a consumer independently downloads your app and chooses to enter or import their own data, HIPAA generally does not — even if that data originally came from their doctor.

Common scenarios (based on HHS health app guidance)
ScenarioHIPAA likely applies?
A hospital contracts with you to provide a patient portal appYes — you are a business associate
A health plan offers your care-management app to members under a contractYes
A consumer downloads your fitness app and enters their own dataGenerally no
A consumer directs their provider to send records to your app via the right of accessGenerally no, if you are not acting for the provider
A provider recommends your app, but has no contract and does not send PHI on its behalfGenerally no
Your app is white-labeled and offered by a clinic to its patientsYes

When the FTC rules apply instead

Consumer health apps outside HIPAA are not unregulated. The FTC Health Breach Notification Rule (16 CFR Part 318) requires vendors of personal health records and related entities to notify consumers, the FTC and in some cases the media after a breach of security of identifiable health information. The FTC has interpreted "breach" to include unauthorized disclosures — such as sharing health data with advertising platforms without the user's authorization — not only cyberattacks. The FTC amended the rule in 2024 to clarify its application to health apps.

Separately, Section 5 of the FTC Act prohibits unfair or deceptive practices, which the FTC has used against health apps whose privacy promises did not match their data sharing. State consumer health data laws add further obligations; confirm which apply with counsel.

Mobile-specific security considerations

Data stored on the device

Minimize what is cached locally. Use platform-provided secure storage (iOS Keychain, Android Keystore) for tokens and keys, rely on OS-level encryption, and avoid writing PHI to shared storage, logs or the clipboard. Plan for lost and stolen devices: short session lifetimes, remote session revocation, and no PHI in backups you do not control.

Push notifications and lock screens

Notifications pass through Apple and Google infrastructure and can appear on a locked screen. Keep PHI out of notification payloads — "You have a new message" rather than test results or appointment types — and fetch the details only after the user authenticates in the app.

Authentication

Biometric unlock is convenient but typically unlocks a locally stored credential; the strength of the underlying account authentication still matters. MFA is a recommended practice that supports §164.312(d).

APIs and transmission

All traffic should use TLS (§164.312(e)). Consider certificate pinning for high-risk apps, enforce authorization server-side on every API call, and never trust the client to filter which records a user may see.

Analytics SDKs and tracking technologies

Third-party SDKs for analytics, crash reporting, attribution and advertising are the most common way health apps disclose data unintentionally. An SDK that receives a device identifier along with the fact that a user opened a medication-refill screen may be receiving PHI. If HIPAA applies, a vendor receiving PHI needs a BAA — and many analytics and advertising vendors will not sign one.

OCR issued a bulletin on the use of online tracking technologies by covered entities and business associates in December 2022 and updated it in March 2024. In June 2024, a federal district court in Texas vacated part of that guidance — the portion addressing tracking on unauthenticated public web pages in certain circumstances. Guidance about authenticated pages and mobile apps was not the focus of that ruling, but the landscape is evolving: verify the current status of OCR's guidance before making decisions, and involve counsel.

  • Inventory every SDK in each app build, including transitive dependencies.
  • Document what data each SDK receives, in which events, and with what identifiers.
  • Remove or reconfigure SDKs that receive PHI without a BAA.
  • Re-check after every SDK update; default data collection changes.

Questions to settle before launch

  1. 1

    Who is our customer?

    If a covered entity or business associate is paying for or offering the app, assume HIPAA applies and confirm with counsel. If consumers are, evaluate the FTC Health Breach Notification Rule, the FTC Act and state consumer health data laws.

  2. 2

    What data do we collect, and where does it go?

    Map every field from the device to the backend and to each third party — including analytics events, crash logs and support tools.

  3. 3

    Which vendors receive PHI?

    List each one and confirm a BAA is in place where HIPAA applies, or remove the data flow.

  4. 4

    What stays on the device?

    Decide what is cached, how it is protected, and what happens on logout, uninstall or device loss.

  5. 5

    Do our disclosures match reality?

    Compare the privacy policy, app store privacy labels and, where applicable, the notice of privacy practices against what the app actually does.

  6. 6

    Who responds to an incident?

    Define how a suspected disclosure is triaged and who decides whether HIPAA breach notification or FTC notification obligations are triggered.

App store and platform requirements

Apple and Google impose their own rules on health data collection, privacy labels and data safety disclosures. These are platform policies rather than legal requirements, but inaccurate disclosures can create FTC exposure and contradict your HIPAA notice of privacy practices or privacy policy.

Building it into your release process

Make the app part of the risk analysis rather than an afterthought. Include mobile builds, backend APIs, third-party SDKs and push providers in the inventory, and test them before release. Our HIPAA technical safeguards assessment covers app and API review, and HIPAA consulting for healthcare startups addresses the applicability questions early-stage teams face. For broader platform questions see HIPAA compliance for software companies.

Frequently asked questions

Is every health app subject to HIPAA?

No. HIPAA applies only when the app is provided by or on behalf of a covered entity or business associate. Many consumer health apps fall outside HIPAA but may be covered by FTC rules and state law.

What is the FTC Health Breach Notification Rule?

An FTC regulation (16 CFR Part 318) requiring certain non-HIPAA health apps and personal health record vendors to notify consumers and the FTC of breaches, which the FTC interprets to include unauthorized disclosures.

Can we use Google Analytics or similar tools in a HIPAA app?

Only if no PHI is disclosed to the vendor, or the vendor signs a BAA and the use is permitted. Review what each tool receives and verify OCR's current tracking technology guidance, parts of which were vacated in 2024.

Should push notifications contain PHI?

As a practice, no. Notifications can appear on locked screens and transit third-party infrastructure. Use generic text and show details after in-app authentication.

Authoritative sources

This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.

Talk through your HIPAA obligations with a consultant

Tell us about your organization, how you handle patient information, and what’s prompting the review. We’ll suggest a practical scope — and tell you if you don’t need us.