New Google Play rules for 28th October, 2026

If your app on Google Play requests permissions to access a user's contact or precise location, Google now requires you to justify those permissions on Google Play directly. The deadline for this requirement is the 28th of October, 2026.

Contacts

Apps built for Android 17 (API level 37) or later may only request the READ_CONTACTS permission if the Android Contact Picker is not enough. Essentially, these apps should switch to Android's Contact Picker to achieve this information. If your app still needs broad contacts access, you have to submit a declaration in Play Console explaining why the Contact Picker is not enough.

Location

Apps that request the user's device location, including the new Android location button, would need to go through a Play Console declaration and review. You must request the minimum scope your feature actually needs: coarse instead of precise, foreground instead of background. For apps targeting API level 37 or later, if precise location is only needed for a one-time, user-initiated action, such as finding nearby stores, you're required to use the Android location button instead of the ACCESS_FINE_LOCATION permission. Fine location access is only allowed where neither the location button nor coarse location can support the feature.

Note on the deadline

Both requirements are tied to targeting Android 17 (API level 37). Most apps are currently working toward API level 36 which is the target required by August 31, 2026. This permissions declaration process becomes mandatory from October 28, 2026 for any app that targets API level 37 or later. If you're not moving to API 37 yet, you have some runway, but the declaration requirement is worth planning into your next target API update rather than leaving for the deadline itself.