Clear sensitive permissions and unexpected declarations
Complete the forms Play Console asks for and remove permissions your app does not need, including ones added by dependencies.
By The Draftbit team · Updated
Sources checked
This guide is for Apps requesting sensitive access or completing Google Play's App content dashboard, including apps with no health or financial features.
Play Console is asking about health or financial features your app doesn’t have. You may still need to complete those forms and say so. Work through every required declaration, then check the permissions in the build you’re actually submitting.
Ask your developer or build provider for the permissions added by the app and its dependencies. For each one, identify the feature that needs it and the least access that will let that feature work.
Finish the App content forms
Open App content and check the outstanding declarations. Covered closed, open, and production apps need the health and financial-feature forms completed. If the app has neither type of feature, say so in the forms rather than skipping them.
Health declarations can cover wellness, sleep, or fitness features even without medical claims.
Check photo and video access
For apps targeting API 33 or later, broad media permissions need a qualifying core use and a declaration explaining why the system picker isn’t sufficient.
If users only need to choose specific files, prefer the platform’s picker. Remove unnecessary broad permissions from the build and test the picker flow.
For a notice naming READ_MEDIA_IMAGES or READ_MEDIA_VIDEO, use the photo and video rejection guide. It covers choosing the access route, checking dependencies, and inspecting the final bundle and included version codes.
Review location and other sensitive permissions
Check the policy, disclosure, consent, and declaration requirements for each feature. The contacts and location changes in the requirement above have their own scope; check whether they apply to your app.
Removing a permission or changing runtime behavior needs a corrected build. Update Data safety too if data practices change.
If a permission still appears in the bundle
Check dependencies that add permissions through configuration or merged manifests. Editing a questionnaire won’t remove a permission from an existing bundle.
Before submitting, confirm that required declarations are complete, every permission supports a real feature, and the final build asks only for the access it needs.
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Sensitive permissions and APIs Checked 22 September 2026
- Health apps declaration Checked 22 September 2026
- Financial features declaration Checked 22 September 2026
- Prepare your app for review Checked 22 September 2026
- Comply with photo and video permission requirements Checked 22 September 2026