Google Play restricted permissions policy: fixes and checks

By The Draftbit team · Updated
Sources checked

This guide is for Google Play apps using dangerous, special, signature, or otherwise restricted permissions.

An Android permission being available doesn’t mean every app can request it. Google’s restricted-permission rules add eligibility and data-handling conditions beyond the operating-system prompt.

Check necessity and refusal

Identify the core feature requiring access and inspect what happens when someone declines. We’d keep unrelated features usable and provide reasonable alternatives where possible, such as manual entry instead of reading a record.

Remove unnecessary access

Remove permissions that aren’t justified by the actual feature, including declarations inherited from libraries. Apply the relevant specific policy and User Data requirements. The policy describes rare exceptions for compelling cases with no alternative; don’t assume an exception without evidence.

Test the submitted build with granted and declined access, and inspect its manifest. Give Google the necessary feature, narrower alternatives considered, and any required declaration. The runtime prompt alone doesn’t establish policy eligibility.

Messages this guide can help with

Restricted permissions; Restricted permissions policy violation; Restricted permissions rejection; Restricted 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.

Your next stepSubmit a Google Play release with working review access