Google Play minimum-scope permission alternatives policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for Google Play apps requesting broad access where a system picker, Sharesheet, or narrower API may meet the need.
A person choosing one file doesn’t necessarily need to grant access to all their files. Google’s minimum-scope rule expects sensitive permissions only when a narrower alternative can’t provide the core functionality.
Try the narrower workflow
Test the actual task with a system picker or share action. Can a user select a photo, contact, or document and finish the task? We’d record a concrete limitation if the narrower route fails, rather than say broad access is more convenient.
Change the implementation and build
Use the narrower route when it meets the feature. Remove unused broad permissions from the final manifest, including those added by dependencies. If broader access is necessary, follow that permission’s eligibility and declaration requirements.
Test selection, cancellation, and denied access on supported Android versions. Give Google the corrected bundle or a specific explanation of why the alternative can’t support the app’s core task.
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: Minimum-scope permission alternatives Checked 22 September 2026