Google Play Health Connect policy: fixes and checks

By The Draftbit team · Updated
Sources checked

This guide is for Google Play apps reading or writing Health Connect data, including health records.

Health Connect provides a shared place for health data and permissions, but each app still needs an approved purpose. Its data is personal and sensitive, including clinical records as well as ordinary activity measurements.

Map data types to visible features

List each requested read/write permission and the feature using it. We’d inspect the actual declaration and library behavior instead of assuming a broad health integration needs every data type.

Apply the additional requirements

The child pages cover appropriate use, limited use, minimum scope, and transparent user controls. Also meet health-app requirements and the User Data policy.

Test granted and revoked permissions with fictional records. Verify that writes are appropriate and that the feature handles unavailable data. Give Google the declared use case, data types, privacy information, and review steps. Access to Health Connect doesn’t establish that a medical use is approved or that every reading is accurate.

Messages this guide can help with

Health Connect; Health Connect policy violation; Health Connect rejection; Health Connect denied

Official sources

We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.

Your next stepSubmit a Google Play release with working review access