Google Play: Policy announcement (April 15, 2026)
Google Play’s April 15 policy announcement is mostly about ‘narrower access by default’: new Contacts Permissions rules (use the Contact Picker unless you genuinely need broad access), a required Play Console account transfer workflow, and tightened guidance on precise location.
Original post (source): Play Console Help - “Policy announcement: April 15, 2026” (April 15, 2026)
The headline
Google Play is pushing harder on minimal access + safer defaults, and it is packaging that as policy (not just “best practice”).
What changed (key items)
- New Contacts Permissions policy: apps that don’t need broad contacts access should use the Android Contact Picker instead.
- New Account Transfer policy: if you are transferring a developer account, you must use Play Console’s official Transfer ownership workflow.
- Updated Location Permissions guidance: Google recommends the new location button as a minimum scope for precise location.
There are also reminders and clarifications (news/magazines declaration, Health and Fitness data guidelines, prediction markets pilot).
Why this matters (practically)
Two reasons this shows up as a growth issue:
- Permission asks and “broad access” are now more likely to become review friction and user trust friction.
- Account and policy workflow changes can become launch blockers at the worst possible time.
Tiny win
Find one place you request contacts or precise location, and ask: “Could we ship a picker or just-in-time ask instead?” If yes, write the change as a ticket and measure support volume on that flow for two weeks.
Read the original: https://support.google.com/googleplay/android-developer/answer/16926792?hl=en
Want help with ASO?
If you want this implemented for your app, check out our services - or run your workflow in APPlyzer.