Google Play Health Connect minimum scope policy: fixes and checks

A Health Connect rejection may be about the breadth of access rather than the feature itself. Google requires requests limited to the data necessary for the product’s actual functionality.

Map each permission to a screen

List read and write permissions separately and name the current feature using each. We’d remove entries that exist only because a sample project or SDK requested them by default.

Narrow the declaration and code together

Remove unused requests from the app and update the corresponding console declaration and privacy explanation. If the feature needs historical or background access, justify that separately against current guidance rather than assuming ordinary read access covers it.

Test the app with only the reduced set granted. Check that unsupported data types aren’t requested later through another flow. Give Google the feature-to-permission mapping and corrected build. Future plans for a feature don’t establish a current need for its data.