Google Play policy announcement (Apr 15, 2026): Contacts access, account transfer, and tighter location expectations
A quick summary of Google Play’s April 15 policy announcement, including a new Contacts Permissions policy, a new Account Transfer policy, and updated guidance around location permissions and the Android location button.
Original announcement (source): Google Play Console Help, “Policy announcement: April 15, 2026”
What changed (in plain English)
Google Play published an April 15, 2026 policy announcement that includes new policies plus updates/clarifications. The headline is consistent: reduce broad data access, and make “who has control” clearer.
New policy: Contacts Permissions
Google is introducing a Contacts Permissions policy aimed at limiting broad access to users’ contacts.
If your app does not truly need broad contact access, Google points you toward using the Android Contact Picker instead, which reduces data collection and improves user safety.
New policy: Account Transfer
Google is introducing an Account Transfer policy that requires developers to use the official “Transfer ownership” workflow inside Play Console (when eligible) to transfer a developer account.
This is mostly an operational governance change, but it matters if you acquire apps, restructure publisher accounts, or work with studios.
Updated policy: Location Permissions
Google says it is updating Location Permissions policy and introducing the Android “location button” as the recommended minimum scope for precise location, aligned with user data and sensitive permissions requirements.
In practice, this is a nudge away from “always-on precise location” unless you have a very clear, defensible user value moment.
Why this matters
- Permission design is conversion design. A stricter policy posture usually means fewer aggressive permission asks, which can improve early experience, but it forces product teams to be honest about what is essential.
- Compliance is now tied to specific platform UX patterns. If you are not aligned with official workflows (contact picker, ownership transfer), you are one policy check away from a scramble.
What to do next (tiny wins)
- Audit your app for any place you request contacts access. If you are using it for “invite friends” or onboarding convenience, sketch a version that uses the Contact Picker instead.
- If your org owns multiple apps, confirm who actually controls Play Console ownership and whether you have a documented plan for transfers.
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.