A permission change can alter a release’s policy obligations even when the user-facing feature looks unchanged. Google Play limits use of broad photo and video permissions where a narrower system picker is sufficient. A manifest entry alone does not prove that an app is compliant or non-compliant.
What matters
- Google Play’s photo and video permissions policy covers READ_MEDIA_IMAGES and READ_MEDIA_VIDEO for apps targeting Android 13 (API 33) or later.
- Broad access is expected to support a qualifying core function. One-time or infrequent selection is often better served by Android Photo Picker.
- Permissions can enter the final manifest from dependencies. Check the merged manifest and the actual released artifact, not only one source manifest.
Step-by-step investigation
A worked example (synthetic)
Previous release has no READ_MEDIA_IMAGES entry; candidate adds READ_MEDIA_IMAGES for a profile-image picker. This is a change that deserves review against Photo Picker alternatives, not an automatic determination that the app violates policy.
Compare the previous and candidate releases
Keep a record of what you actually know. In the free browser tool, enter a verified previous-release snapshot and candidate-release snapshot. Run the comparison to inspect changed fields and export a report. Unknown information should stay unknown.
Use the release comparison tool
No account or real release required to try a sample. Your entered snapshots are processed in your browser.
Open free comparison tool →What this guide cannot verify
Official documentation
- Google Play — Restricted permissions and minimum-scope alternatives
- Google Play — Permissions accessing sensitive information
Editorial note: Content checked against the linked official sources on October 28, 2026. This independent guide is informational, not legal advice or a guarantee of Google Play approval.