# Google Play: Health Connect and health permissions not approved
> Google Play rejected or limited the app’s Health Connect or body sensor permissions. Request only the data types a feature uses and match the declared use case.
Canonical: https://app369.com/fix/google-play-health-connect-permissions/
Last updated: 2026-11-09
Health Connect is the Android service apps use to store and share health and fitness data, and Google Play approves its permissions per data type. Play checks that each requested permission backs a user-facing feature within an approved use case.
**Short answer**
List every health permission in the manifest and the feature that reads or writes it. Remove the ones no feature needs, including history and background reads. In Play Console, request only the remaining data types, pick the use case that matches the app, and make the privacy policy name the health data, its use, retention and deletion. Then read the feedback in Play Console and resubmit.
Rather not fix it yourself? [**App Fix Ticket**](https://app369.com/fixed-price/flutter-firebase-bug-fix/) starts with a fixed-price diagnosis, then a fixed price for the fix before any fix work.
## **Why Play refuses the permissions, and the fix**
1. 01 ### **The app asks for more data types than it uses**
> “Only request permissions and access data types that support the specific, user-facing health features you offer.” [**Google Play Console Help, Android Health Permissions: Guidance and FAQs**](https://support.google.com/googleplay/android-developer/answer/12991134) Play lists requesting a bulk list of permissions when not necessary as a common reason for denial. Keep only the types a shipped feature reads or writes, and drop READ_HEALTH_DATA_HISTORY or READ_HEALTH_DATA_IN_BACKGROUND unless a feature needs them.
2. 02 ### **The Play Console request doesn’t match the build**
> “When submitting your app in Play Console, request the specific permissions required for the data types your app needs to support its features.” [**Google Play Console Help, Android Health Permissions: Guidance and FAQs**](https://support.google.com/googleplay/android-developer/answer/12991134) The permissions requested in Play Console and the declared use case must match the data types and features the app actually has. Update the request whenever a release adds or removes a data type.
3. 03 ### **Consent and disclosure are missing**
> “You must comply with all detailed requirements for consent, runtime permission requests, and prominent disclosure outlined in the Google Play User Data policy.” [**Google Play Console Help, Android Health Permissions: Guidance and FAQs**](https://support.google.com/googleplay/android-developer/answer/12991134) Health data falls under the User Data policy. Explain in the app why each type is needed before the system permission prompt, and get the user’s consent.
4. 04 ### **The privacy policy is generic** Also check: the privacy policy must say which health and fitness data the app collects, how it is used, stored and shared, how long it is kept and how it is deleted, and how it is secured. Link it from the app and the store listing.
Checked against the vendor’s docs on November 9, 2026: [Play Console Help: Android Health Permissions, guidance and FAQs](https://support.google.com/googleplay/android-developer/answer/12991134).
## **Rather hand it over?**
Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.
- [from $450**App Fix Ticket**One reproducible bug in an existing mobile or web app, diagnosed and fixed.**See scope and start**](https://app369.com/fixed-price/flutter-firebase-bug-fix/)
[**All 127 Fiverr reviews**](https://app369.com/reviews/)
Related: [**Google Play prominent disclosure**](https://app369.com/fix/google-play-prominent-disclosure-consent/) · [**Google Play photo and video permissions**](https://app369.com/fix/google-play-photo-video-permissions/) · [**Google Play Data safety form rejected**](https://app369.com/fix/google-play-data-safety-form-rejected/) · [**Google Play SMS and Call Log**](https://app369.com/fix/google-play-sms-call-log-permissions/)
Questions
## **More on this launch**
**Where does Play say what was wrong? **+
In Play Console. Google says an incomplete or denied request gets feedback there, so fix each point it names before resubmitting.
**Does BODY_SENSORS count too? **+
Yes. The guidance covers android.permission.BODY_SENSORS and, from Android 16, the more granular android.permission.health permissions.
**Can you fix it for me? **+
If one bug is the whole problem, the App Fix Ticket covers it: a written diagnosis first, then the fix. If the app has more going on, the Launch Check is a written check of the whole app. Each issue found is rated critical, high, medium or low, with where it is and how it was confirmed. No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.
Something else?
## **Describe it and get a written quote**
Describe the app and where it is in the launch. You get a written scope, a fixed price and a timeline; Simon replies by email, usually within one business day.
[**Describe your problem **→](https://app369.com/contact/) [**All fixes**](https://app369.com/fix/)