Google Play body sensor permissions policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for Google Play phone and tablet apps requesting body-sensor data such as heart rate, oxygen saturation, or skin temperature.
A sensor permission needs a supported health-related purpose and appropriate data handling. Google’s rule covers both legacy body-sensor permissions and the more granular permissions used by apps targeting Android 16 or later.
Compare target version and data type
Inspect the final target SDK and the specific readings used. Apps targeting Android 16 or later must use the applicable granular permissions for APIs that previously required broad BODY_SENSORS access. We’d verify this against Android’s target-version guidance before rebuilding.
Request only the approved feature’s data
Match the request to the relevant fitness, medical, research, or companion use case. Follow the health-app and User Data rules, including necessary approvals and disclosures.
Test refusal, allowed readings, and any background collection. Give Google the permission set, user benefit, and declaration evidence. A sensor added by a library still needs an eligible purpose in your app.
Messages this guide can help with
Body sensor permissions; Body sensor permissions policy violation; Body sensor permissions rejection; Body sensor permissions 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.
- Google Play: Body sensor permissions Checked 22 September 2026