Google Play health app rejection: medical claims, misinformation and required disclosures

Google rejects health apps for one of two reasons: the app claims something it cannot support, or it does something regulated without declaring it. The first is a copywriting problem and usually cheap to fix. The second is a licensing problem and sometimes is not fixable at all in the market you were targeting.

How the rejection is worded

Health enforcement arrives as a policy email far more often than as an in-console note, and the email normally names the sub-policy. Typical shapes:

"Your app contains health claims that are not supported by scientific evidence, or that contradict existing medical consensus."

"Your app provides health services but you have not completed the required Health apps declaration."

"Your app facilitates the sale of prescription medication without the required authorisation."

The corresponding console entry lives under App content → Health apps, alongside the other declarations, and the enforcement itself shows on the app's Policy status page.

What it means

Play's health policy covers more ground than most developers expect. It reaches:

Health misinformation: content that contradicts established medical consensus, promotes unproven treatments, or discourages people from seeking care. This applies to content your app displays as well as content it generates, which now includes anything an LLM in your app says about symptoms, drugs or diagnoses.

Medical claims: assertions that the app diagnoses, treats, cures or prevents a condition. Saying an app "detects atrial fibrillation" is a diagnostic claim. Saying it "helps you track your heart rate" is not. That single distinction decides a great many of these rejections.

Regulated activity: telemedicine, prescriptions and pharmacy, clinical decision support, and anything that functions as a medical device in the markets you distribute to. Play expects you to declare this and, in many cases, to hold the relevant clearance or licence for each country.

Health research: apps that collect data for research require informed consent and, where applicable, review by an ethics board or institutional review board.

The Health apps declaration in App content is where you say which of these apply. It asks what kind of health app this is and asks you to attest that you comply with the relevant regulations. An incomplete or contradicted declaration is itself a violation, separately from whatever the app does.

Why it happens

• Marketing language crossed into medical claims. "Cures insomnia", "lowers blood pressure", "detects skin cancer", "clinically proven", often written for the store listing rather than the app, then applied to both.
• The declaration was skipped because the developer thought of the app as fitness or wellness rather than health. A symptom checker is a health app; so is a period tracker that offers interpretation; so is a meditation app that claims a clinical outcome.
• An AI feature answers medical questions. If a chat interface will discuss dosage or diagnosis, the policy applies to what it says, and "the model said it, not us" is not a defence.
• No disclaimer, or a disclaimer nobody sees. A line at the bottom of a settings screen does not offset a home screen that reads like a diagnosis.
• Sources are missing. Health content presented as fact with no attribution, no author credentials and no review process attracts scrutiny even where the content is correct.
• Regulated functionality shipped without clearance for a market the app is distributed in, usually because distribution was left at "all countries".
• User-generated health advice with no moderation.

How to fix it

1. Separate the claims from the features, line by line. Take the listing, the onboarding and the paywall, and mark every sentence that asserts a health outcome. Rewrite each into what the app actually does. "Track", "log", "monitor", "record" and "help you notice" are describable; "diagnose", "treat", "cure", "prevent" and "clinically proven" have to be earned.
2. Complete the Health apps declaration in Play Console → App content, matching what the app genuinely does. If you hold clearance, registration or a licence, name it there.
3. Add the disclosures the policy expects, where users will see them. At minimum: that the app is not a substitute for professional medical advice, what it does and does not do, and who to contact in an emergency. Put it in the flow that gives health information, not only in the terms.
4. Attribute and review your content. Name the sources, name the clinician or organisation that reviewed it, and date the review. This is the cheapest thing you can do to move an app from "unsupported claim" to "informational content".
5. Constrain AI output. If a model can discuss health, put guardrails on it, refuse dosage and diagnosis questions, and say plainly in the interface that responses are not medical advice.
6. Restrict distribution to markets you are cleared for. Set countries explicitly on the release rather than shipping everywhere and hoping.
7. Moderate user content if users can post health advice, reporting, blocking and removal, as with any other user-generated content.
8. Match the content rating and Data safety entries. Health data is sensitive; if you collect it, declare it, and make sure the privacy policy describes it specifically.

Appeal, or fix and resubmit?

Establish which enforcement you actually received, because the paths differ:

• Rejected: the release did not publish. Rewrite the claims or complete the declaration, then upload a new release. There is nothing to appeal.
• Removed: the app is off Play, existing installs still work. Fix and update.
• Suspended: off Play, and recorded against the developer account.

Appeals are made through the form linked in the policy email or from the app's Policy status page.

Appeal when the finding is factual and you can evidence it. If you hold regulatory clearance for the functionality cited, or your content is reviewed by named clinicians against cited guidance, attach it. Health is one of the areas where documentation genuinely moves the outcome.

Do not appeal a claim you cannot substantiate. Arguing that your users find the app effective is not evidence, and it reads as exactly the thing the policy exists to stop. Rewrite the copy and move on.

One thing worth being blunt about: health enforcement escalates. Google is dealing with a category where the harm from getting it wrong is real, and repeated findings put the whole developer account at risk rather than just the app. If you are genuinely operating a regulated service, treat the declaration as part of shipping, not as paperwork to be minimised.

What to send

The store listing and in-app copy have been revised to remove all diagnostic and treatment claims; the app is described as a tracking and information tool. Every health article now carries its sources, the name and credentials of the reviewing clinician, and the date of review. A prominent notice on each information screen states that the app is not a substitute for professional medical advice and directs users to emergency services where relevant. The Health apps declaration has been completed, and distribution is restricted to the countries in which we hold [clearance/registration], attached.

AppSubmit's listing lint flags unsupported outcome claims in store copy before you push it, and the rejection explainer will tell you which health sub-policy an email is actually citing, but the clinical review and the declaration are yours to do.