Summary
Google rejected the app because health-related permissions, data declarations, or user-benefit explanations are incomplete or unsupported.
Google Play App Review issue
Google Play health permissions rejected
Google rejected the app because health-related permissions, data declarations, or user-benefit explanations are incomplete or unsupported.
google play health permissions rejectedhealth data rejection google playgoogle play health permissions
Fix Google Play review issues before the next submission
Use LogicSpring to run a free precheck, regenerate the right policy or disclosure pack, and shorten the loop from rejection notice to resubmission.
What this means
Health data permissions and health-related data categories are treated as higher-risk and need extra justification.
Google expects a narrow use case, strong user-facing explanation, and accurate Data Safety coverage.
If the app is AI-enabled, reviewers may scrutinize how health data is processed or inferred.
Common causes
- The app requests health-related access without clearly proving the feature needs it.
- The privacy policy or Data Safety form does not explain health data processing, storage, and sharing clearly enough.
- Prominent disclosures or consent language are missing or too abstract.
Step-by-step fix
- Step 1
Document the exact health-data use case and remove any health-related access that is not central to the feature.
- Step 2
Update policy, Data Safety, and in-app disclosures with explicit health-data handling language.
- Step 3
Prepare reviewer notes and screenshots that show how the user consents before health data is accessed.
What to update
- Health-related permission declarations
- Data Safety form
- Privacy Policy health-data sections
- Consent and disclosure UI
How LogicSpring helps
- LogicSpring helps teams rebuild high-risk data disclosures with less manual rewriting.
- Precheck is useful when the rejection spans policy, disclosure UI, and form fields at the same time.
- You can keep one structured record of why the app needs the data and reuse it across submission surfaces.
FAQ
Can I resubmit to Google Play without changing the binary?
Only for pure listing or form corrections. If the shipped build still requests the wrong permission, bundles the wrong SDK, or behaves inconsistently, resubmitting the same build is risky.
What evidence should I prepare before resubmitting?
Prepare the updated public policy URL, the exact store fields you changed, screenshots for permission or disclosure flows where relevant, and a short reviewer note explaining what changed and why it now matches the app.
Should the privacy policy, store form, and in-app disclosure all match?
Yes. Review teams compare these surfaces together. If one says you collect or disclose something and another says you do not, the mismatch itself often becomes the next rejection.