Google Play policy announcement (April 15, 2026): contacts access, account transfers, and tighter location defaults

Google Play posted a policy announcement with a few items that are easy to ignore until a release gets blocked. It is worth skimming if your app touches contacts, location, or you operate under a publisher group that might transfer accounts during M&A.

• Source: Google Play Console Help, “Policy announcement: April 15, 2026”
• Read: https://support.google.com/googleplay/android-developer/answer/16926792?hl=en

The one-line lesson

Google is tightening the “default expectation” for sensitive access: use the safer platform primitives first, then justify anything broader.

What changed (high signal)

• Contacts Permissions policy (new). If you do not truly need broad access to a user’s contact list, Google is pushing you to use the Android Contact Picker instead.
• Account Transfer policy (new). Transfers should use the official “Transfer ownership” workflow in Play Console, not credential sharing.
• Location Permissions policy (updated). A “location button” is positioned as the recommended minimum scope for one-time precise location use.
• Clarification: dating as an incidental feature. If matchmaking is not your core product, you may avoid some Play Console minor restriction settings, but only if you implement effective age-gating for the dating feature.

Why this matters (practically)

• Compliance work is now product work: permission UX and feature design decisions can become release blockers.
• “We only use contacts for invites” and “we only need precise location once” are exactly the cases where Google wants you off broad permissions.

Tiny win (45 minutes)

Make a quick list of every place your app requests contacts or precise location, then for each:

1. write the user-visible reason in one sentence
2. confirm you can replace broad access with Contact Picker or a one-time location flow
3. add an internal note: what will break if you remove the permission

That gives you a concrete migration plan before review pressure forces it.