What is the difference between general wellness and Software as a Medical Device (SaMD)?

General wellness covers claims about maintaining or encouraging a general state of health or a healthy activity, with no reference to a specific disease. Software as a Medical Device is software intended for a medical purpose — to diagnose, treat, cure, mitigate, or prevent a disease — which can meet the FDA's device definition and face regulation. To qualify for the general wellness policy a product must meet both prongs of the FDA's test: intended for general wellness use only, and low risk (not invasive, not implanted, no unsafe technology).

Does calling my app 'for wellness only' keep it out of FDA regulation?

No. A 'wellness only' disclaimer does not cure a disease claim. The FDA infers intended use from what you actually claim and how you market the app, so if your copy says the app detects, diagnoses, or treats a condition, it can be treated as a device regardless of a disclaimer that says otherwise. Your marketing language is effectively a legal surface — write claims deliberately.

Does the FDA regulate how my fitness app stores or shares data?

No. The FDA's concern is the safety and effectiveness of medical claims, not data privacy. Privacy and security obligations come from other sources — the FTC, state consumer-health laws, and GDPR for EU users. Staying within the general wellness policy answers whether you are an FDA device, not whether you are compliant overall; see the HIPAA and 'is fitness data PHI' pages for the data side.

Does the FDA Regulate Fitness Apps?

Q: Does the FDA regulate fitness apps?

Usually not. Low-risk apps intended for general wellness use — step counting, calorie and sleep tracking, general-fitness coaching, monitoring pulse or oxygen during exercise — typically fall under the FDA's general wellness policy, where the agency applies enforcement discretion rather than regulating them as medical devices. That is a policy posture, not a statutory exemption, and the guidance was refreshed in early 2026, so verify the current text before relying on it.

Q: My app detects AFib or analyzes ECG data — is that a medical device?

Likely yes. A claim to detect a specific condition such as atrial fibrillation is a disease-detection claim, which generally makes the software a device and may require FDA clearance or authorization (for example, a 510(k) or De Novo pathway). AFib-detection features on consumer wearables have gone through FDA clearance or De Novo in the real world. If you are building a feature like this, plan for a regulatory pathway and verify the specific product route with a specialist rather than assuming a wellness disclaimer covers it.

If you are building a step counter, a calorie or sleep tracker, or a general-fitness coaching app, the short answer is usually no — the FDA does not regulate it as a medical device. Products like these typically fall under the FDA's general wellness policy, where the agency's Center for Devices and Radiological Health (CDRH) applies enforcement discretion rather than treating the software as a regulated device. What moves an app across the line is not the sensor or the data — it is the claim you make. Marketing that your app diagnoses, treats, cures, or mitigates a specific disease can turn it into Software as a Medical Device (SaMD) and pull it into FDA oversight. One caveat to hold onto throughout: general wellness is a policy and guidance posture, not a blanket statutory exemption, the FDA keeps its authority, and the guidance was refreshed in early 2026 — treat it as active and verify the current text. This page is general engineering guidance, not legal or regulatory advice; confirm your own product's pathway with a qualified professional.

Does the FDA apply to your app at all?

The FDA regulates medical devices — and software can be a device. The relevant guidance is the FDA's "General Wellness: Policy for Low Risk Devices," which describes when CDRH will exercise enforcement discretion and not regulate a low-risk general-wellness product as a device. Separately, the 21st Century Cures Act (Section 3060) removed certain "healthy lifestyle" software from the medical-device definition altogether.

Two things are worth being precise about:

Enforcement discretion is not the same as "exempt." The general wellness policy means the FDA is saying it does not intend to enforce device requirements against qualifying low-risk products — not that a statute carves them out. The agency retains authority and can change the policy (and did refresh it in early 2026). Do not describe it as a "blanket exemption."
The FDA does not regulate your data privacy. The FDA is concerned with the safety and effectiveness of medical claims, not how you store or share health data. Privacy obligations come from elsewhere — the FTC, state consumer-health laws, and GDPR for EU users. See the HIPAA page and is fitness data PHI? for who actually governs the data side.

The two-prong test for general wellness

A product qualifies for the general wellness policy only if it meets both of these:

Prong	What it means for your app
1. General wellness use only	The intended use — as shown by your claims and marketing — is about maintaining or encouraging a general state of health or a healthy activity, not diagnosing or treating a disease.
2. Low risk	The product is not invasive, not implanted, and does not involve technology that poses a safety risk without regulatory controls (for example, lasers or radiation).

If either prong fails, the product falls outside the policy.

Prong 1 has two acceptable kinds of claims

Category 1 — general wellness only. Claims about maintaining or encouraging a general state of health or a healthy activity, with no reference to a specific disease or condition. Examples the FDA gives include weight management, physical fitness, relaxation and stress management, mental acuity, self-esteem, sleep management, and sexual function.
Category 2 — healthy lifestyle linked to disease risk (well-established links only). Claims that connect a healthy lifestyle to reducing the risk of, or helping you live well with, a chronic disease or condition — but only where that link is well understood and established in peer-reviewed science or health-professional-organization statements. For example, "promotes a healthy weight, which may help you live well with type 2 diabetes."

Category 2 is a narrow, evidence-gated allowance — not a green light to reference diseases freely.

Concrete examples: which side of the line?

Generally general wellness (enforcement discretion likely):

Step counting and activity tracking
Calorie and nutrition tracking
Sleep tracking and sleep-management coaching
"General fitness" coaching and workout guidance
Monitoring pulse or oxygen "during exercise and hiking"
Stress, relaxation, and weight-management features

Can cross into medical-device / SaMD territory (disease claims):

"Detects atrial fibrillation (AFib)"
"Diagnoses sleep apnea"
"Treats depression"
"Monitors blood glucose for diabetes management" as a medical function

Software that claims to diagnose, treat, cure, or mitigate a specific disease generally meets the device definition and may need FDA clearance or authorization (for example, a 510(k) or De Novo pathway). In the real world, AFib-detection features on consumer wearables have gone through FDA clearance or De Novo — so if you are considering a feature like that, verify the specific product pathway rather than assuming a wellness disclaimer will cover it.

What this means for a fitness app

Your marketing copy is a legal surface. The intended use is inferred from your claims. The same heart-rate feature can be general wellness ("track your pulse during workouts") or a device claim ("detects AFib"). Write claims deliberately.
A "for wellness only" disclaimer does not cure a disease claim. If your app says it detects or diagnoses a condition, you are likely a device regardless of a disclaimer that says otherwise.
Staying general-wellness keeps you out of device territory, not out of regulation entirely. You still have privacy and consumer-protection obligations — see the sibling compliance pages. The general wellness policy answers "am I an FDA device?", not "am I compliant overall?"
If you are heading toward a disease claim on purpose, plan for a regulatory pathway (clearance/authorization) and get specialist advice early; it changes your product timeline, not just your copy.

A note on limits and change

The general wellness guidance is active and evolving: the guidance page reflects a January 6, 2026 update, and the FDA held a related town hall in February 2026. Treat the current text as the source of truth and verify it before you rely on any specific wording, category, or example — details in this area are being revisited in 2026. Whether a specific feature is "low risk" or crosses into a "disease claim" is a judgment call that depends on your exact wording and design, so this page is general guidance rather than a compliance determination. For your particular product, confirm your obligations with a qualified regulatory professional.

General engineering guidance, last reviewed July 14, 2026. This is not legal, medical, or regulatory advice. Health-data laws (HIPAA, GDPR, state privacy laws) and platform policies vary by jurisdiction and change often, and how they apply depends on your specific product, users, and data. Confirm your obligations with a qualified attorney or compliance professional and check the current official sources before you ship.