Back to BlogStore review

Health App Rejected by Google Play? How to Fix and Resubmit

Why Google Play rejects health apps: Health apps declaration, medical claims, Health Connect permissions, privacy gaps. What to fix and how to resubmit.

Vaclav Skarka17 min read
In this guide

Short answer: Google Play rejects a health app when what you told Google does not match what the app does: the health features you declared, the data and permissions the app asks for, the Data safety form (your list of what the app collects) and the privacy policy. Health claims without a disclaimer and a missing way to delete an account also block releases. Fix everything you find, not only the issue the email names, then resubmit; appeal only when Google got it wrong. Two things can add weeks before a first release: health apps such as medical apps need an organization developer account, and a new personal account must first pass a 14-day closed test with at least 12 testers.

I take my own apps through store review on Google Play and the App Store: Health3 (lab results), Unbuzz (caffeine) and Spoonlet (food tracking). For a client, I took a training app for aesthetics clinicians through its first Google Play submissions and review, under Google's health app rules. This is my checklist, verified against official Google and Apple pages as of November 2026. It is not legal advice.

If you already have a rejection, three things first. A rejected update leaves your published version live, and a rejection by itself does not affect your account standing; repeated rejections can lead to a suspension (Enforcement Process). The email names one issue, but Google says its notices "may not indicate each and every policy violation", so check the whole app before you resubmit. And not every finding means changing the app: of four findings from review of my own health app in 2026, two were resolved by evidence in my reply. The next two sections say what to do today. The rest is the checklist behind each finding.

Rejection in hand? Send me the rejection email and a link to your app. I reply with what I would fix first, and that reply is free.

How do I read a Google Play rejection email?

Read it for three things: the outcome, the policy it names, and the part of your app it points to. The app's Policy status page in Play Console adds "any additional information that's available" (Policy status). What each outcome means (My app has been removed):

  • Rejected: the new app or update is not published; a previous version stays live.
  • Removed: the app is off Google Play until a compliant update, which restores its users and ratings.
  • Suspended: the app is gone with its users and ratings, and it counts as a strike.
  • Warning: fix it within the stated days, or the app is removed.

Read the named policy in full, then audit the whole app, because notices "may not indicate each and every policy violation" (Enforcement Process). I map each finding to the exact screen, listing text or declaration.

Where each kind of finding gets fixed:

The rejection namesWhat Google checkedWhere you fix it
Health Content and ServicesHealth claims, and the medical device declaration or "not a medical device" disclaimerStore description, screenshots and the app's first screens
Health apps declarationWhether what you declared matches your listing and featuresPlay Console, in the declaration form
Health Connect or health permissionsA feature the user can see, and a clear reason, for each data typeThe app's permission requests, the declaration and the explanation screen
Data safety or privacy policyWhether both cover everything the app and its SDKs collectThe Data safety form, the policy page and the link inside the app
Account deletionA way to delete the account in the app, and a web page for requestsThe app and a public web page
Target API levelThe Android version the app is built forA new build of the app

How do I fix and resubmit a rejected Google Play app?

Make the app, the store listing and your Play Console declarations agree, replace the old version on every track, then send the changes for review yourself:

  1. Fix the named issue, and check the app against every other policy too.
  2. Update every track carrying the old version, including test tracks.
  3. Upload the compliant bundle and deactivate the non-compliant one. Otherwise "your attempt to resubmit your app will fail" (resubmission steps).
  4. In Manage track, create a release, keep the old version under "Not included", and roll out to 100%.
  5. Changes are not sent automatically: click Send for review on the Publishing overview page (Publish your app).

These steps need someone who can change the app and upload a new version. If nobody on your side can, send me the rejection. I make the changes myself in apps built with Flutter, and I tell you before you pay anything what I can do for an app built another way. If your previous developer still holds the code or the store account, say so in your first message and I tell you what to ask them for.

What has review asked of my own health app?

Health3, my lab-results app, goes through review with every release and is live on both stores. Most releases pass the first time. Four findings from 2026 taught me the most. All four came from Apple, and I include them here because Google asks the same questions:

FindingApple guidelineWhat resolved itChange to the app?
A health data permission the reviewer could not see in use5.1.3A screen recording of the feature, in my replyNo
Where the reference ranges come from2.1, 1.4.1The sources, sent the same dayNo
A per-month price shown larger than the price charged3.1.2The plan screen rebuilt to show billed pricesYes
Store screenshots with a status bar that was not from iOS2.3.10Every screenshot re-renderedStore page only

From Google Play itself, my lessons are about the account and the declarations: start on an organization account, and treat the Health apps declaration as part of the app.

The first finding has a direct counterpart on Google Play: every Health Connect data type needs a feature the user can see. The fourth is the lesson Google states itself: fix the whole category a notice points at, not the one example.

Does my app need the Google Play Health apps declaration?

The Health apps declaration is a form in Play Console where you tell Google which health features your app has. Yes: every app on a closed, open or production track must complete it, even to certify it has no health features (Health apps declaration). Google reviews it with the app, so make it match your listing and features.

An app that uses health data for a non-health feature, such as a game reading step counts, is still in scope of the Health Content and Services policy. The categories in the Health apps declaration are also broad: a course app for healthcare professionals holds no patient records, yet "Medical Reference and Education" covers "Educational resources for healthcare professionals and patients". Check every category against your app.

I have completed the Health apps declaration, the Data safety form and the health disclaimers for a client's app and for my own health apps. The mistake I see most is treating the declaration as a formality: Google reads it against the store page and the app, and a mismatch is itself a reason for rejection.

Which health claims get an app rejected?

Google rejects misleading or potentially harmful health claims, and health apps that neither declare themselves a regulated medical device nor state that they are "not a medical device" (Health Content and Services). The policy asks for:

  • A medical device declaration or a disclaimer. A regulated medical device must show approval, clearance or certification on request; other health and medical apps state in their description that the app is "not a medical device and does not diagnose, treat, cure, or prevent any medical condition."
  • A reminder "to consult a healthcare professional for medical advice, diagnosis, or treatment."

Medical device status turns on intended purpose. Swissmedic writes that the intended purpose "as defined by the manufacturer, is definitive for qualification", so one sentence in your listing can change your status. "Keep a log of your blood pressure readings to share with your doctor" describes a record-keeping tool, while "find out if you have high blood pressure" reads as a diagnostic purpose. Review your store listing, screenshots and onboarding with that in mind. Guidance comes from the FDA (US), MHRA (UK), MDCG 2019-11 (EU) and Swissmedic.

What does Google require for Health Connect and health permissions?

For Health Connect, Android's shared store for health and fitness data, Google requires you to declare each data type your app uses, justify it with a feature the user sees, and request nothing more (Publish your health app). If you are the founder, take one rule from this section: ask only for data a feature uses, and say which feature. The rest is for whoever builds your app.

Google reviews every data type request, with "heightened scrutiny" for reproductive health, alcohol, clinical vitals and symptoms (Android Health Permissions). To pass:

  • Name the feature and its benefit in each justification; "Needed for app functionality" is Google's example of an incomplete one.
  • Show the same privacy policy as your Play listing when Health Connect sends ACTION_SHOW_PERMISSIONS_RATIONALE (Health Connect setup).
  • Never sell the data to data brokers or use it for ads or credit, insurance or employment decisions.

Location, activity recognition, Bluetooth, camera and microphone permissions are in scope too: a health app that requests any of them must prominently disclose how it uses the data and get the user's affirmative consent (Health app categories). Show that explanation in the app right before the permission prompt, and require a tap to accept (User Data policy). Apps targeting Android 16, now required, must use granular permissions such as READ_HEART_RATE instead of BODY_SENSORS (permissions policy).

What must the privacy policy and Data safety form say?

Both must cover all data the app collects, uses and shares, and match what it does. Link the privacy policy in Play Console and inside the app, on a public, non-geofenced web page, not a PDF (Health Content and Services); for health permissions it must also cover retention, deletion and security (Android Health Permissions).

The Data safety form must include data collected by SDKs. When I fill one in, I start from the list of SDKs in the app build, not from memory: analytics, crash reporting, push messaging and chat widgets all collect data that belongs on the form. Misstatements must be fixed, or the app faces blocked updates or removal.

Health data also has extra protection under EU, UK and Swiss data protection law (GDPR Article 9, UK GDPR Article 9, FADP Article 5), and Google's permissions policy reminds US developers that HIPAA can apply. Ask your counsel which apply to you before you fill in the form.

What are Google Play's account deletion rules?

If users can create an account, offer an in-app way to delete it and its data, plus a web page where they can request deletion without reinstalling the app (account deletion requirements). Deletion covers health and Health Connect data; you may keep data needed for security, fraud prevention or regulatory compliance if you tell users. Put the web link in the Data safety form.

Which other Play Console items block a release?

Three more items block releases: an outdated target API level, missing reviewer sign-in details, and clinical-service payments through Google Play billing.

  • Target API level: since August 31, 2026, new apps and updates must target Android 16, API level 36 (target API requirements).
  • Sign-in details: give reviewers working credentials for every login-protected area, and explain one-time passwords (Prepare your app for review). If your app is only for invited patients or paying members, create a reviewer account with the sample content a real user would see.
  • Clinical payments: "Transactions involving regulated clinical services should not use Google Play's billing system" (Health Content and Services).

When should I appeal a Google Play decision?

Appeal when the app already meets the policy; Google reinstates apps "if an error was made" (Managing Policy Violations and Appeals). You get one appeal per enforcement action (My app has been removed), through the email's link or, for a suspension, the Appeal button on Policy status (Policy status). Write the appeal as evidence: quote the policy, show where the app meets it, and attach a short screen recording.

Do I need an organization developer account for a health app?

Yes for a medical app, and Google recommends one for businesses. Google says you must choose an organization account if you provide "Health apps, such as medical apps and human subjects research apps", and advises one for any business engaged "in commercial, industrial, professional, or governmental activities" (Choose a developer account type). A clinic, course business or startup fits that description.

You need a D-U-N-S number, a free business identifier from Dun & Bradstreet that "can take up to 30 days" to get, plus a website and verified contact details. Request it first; the rest of the account setup waits on it.

This is the first thing I check, from experience. I have made this move myself: an app that began under a personal account and moved to an organization account before its Google Play release. A health app has to be on one anyway, and the move also takes the 12-tester test out of the way. An existing app can be transferred, and Google moves its users, ratings and reviews with it (Transfer apps to a different developer account). Do it before the first public release, not after a rejection.

How does the 12-tester, 14-day closed test work?

If your personal developer account was created after November 13, 2023, you must run a closed test with at least 12 testers opted in for 14 days in a row before you can apply for production access (App testing requirements):

  1. Start the closed test and keep all 12 testers opted in; a tester who leaves and rejoins starts over.
  2. Click Apply for production on the Dashboard and answer questions about the test, the app and its readiness.
  3. Review "usually takes seven days or less". With too few or disengaged testers, you may have to keep testing.

The 14 days are the easy part. The hard part is 12 real people who each opt in and stay opted in for all 14 days. For an app whose users are busy professionals, that is difficult to arrange. It is one more reason for a business to publish from an organization account, where this test does not apply.

When I take on a release, I set this test up and you invite the 12 people, or I move the app to an organization account when that is the faster route.

What does the App Store require of health apps?

Apple asks for much the same, in its own words: sources behind health figures (guideline 1.4.1), a privacy policy and account deletion that starts in the app (5.1.1), no health data for advertising (5.1.3), and a working demo account (2.1). The details are in Apple's App Review Guidelines, and if you disagree with a decision you can appeal to the App Review Board.

Google Play and App Store health app checklist

  • Organization account with D-U-N-S for health apps such as medical apps; on a newer personal account, 12 testers for 14 continuous days.
  • Health apps declaration matches the listing and app.
  • Listing, screenshots and onboarding state the intended purpose you mean.
  • Medical device proof or the "not a medical device" disclaimer; a reminder to consult a professional.
  • Only needed Health Connect data types, each justified; rationale screen shows your Play privacy policy.
  • Granular health permissions, not BODY_SENSORS.
  • Public privacy policy linked in Play Console and the app; Data safety form covers every SDK.
  • In-app account deletion plus a web deletion link.
  • Target API level 36; reviewer login with sample content.
  • App Store: guidelines 1.4.1, 2.1, 5.1.1 and 5.1.3.

Common questions

Can I pay someone to fix and resubmit a rejected health app?

Yes. Send me the rejection email and a link to your app. My first reply is free and says what I would fix first, and you get a fixed price in writing for the fixes and the resubmission before any work starts. Approval stays Google's and Apple's decision, so I commit to the work, not to the outcome.

How long does Google Play take to approve a health app?

Each fix is reviewed again, and some apps get extended reviews of "up to 7 days or longer in exceptional cases" (Publish your app). A new personal account first needs a 14-day closed test, then a production access review that "usually takes seven days or less" (App testing requirements). An organization account first needs a D-U-N-S number, which can take up to 30 days.

Does a rejection hurt my developer account?

Not by itself: a rejection does not affect your account standing, and a rejected update leaves the previous version live. Repeated rejections or removals can lead to a suspension, which counts as a strike (Enforcement Process).

Need help with this?

If your health app is stuck in review on Google Play or the App Store, send me the rejection email and a link to your app. My first reply is free.

If another team built your app and you want the whole product checked, the Product Rescue Audit ($500CHF 400) reviews its code, data handling and release path. For a new health product, the Health-tech MVP Sprint ($5,900CHF 4,800) is a focused pilot with access controls, audit logging and technical documentation; see also health app development and the ProFinity case study.

Sources

Rejection in hand?

Send me the rejection email and a link to your app. I reply with what I would fix first, and that reply is free.

Send me the rejection

Written by Vaclav Skarka, founder of HLT3 Studio in Zurich, software engineer since 2008 and former software architect at Avaloq.