Skip to content
TrustList
News

Google Play sets dates for new location, contacts, local network and AppFunctions rules

Editorial

By TrustList Editorial

Google Play will require apps targeting Android 17 to use the location button for one-off requests and to declare any use of precise location from 27 January 2027, with contacts, AppFunctions and local network rules following in 2027.

About Google Play sets dates for new location, contacts, local network and AppFunctions rules

Google Play sets dates for new location, contacts, local network and AppFunctions rules

18 November 2026: Google Play has published a schedule of changes to its policy on permissions and APIs that reach sensitive information. Its Play Console Help article now carries a notice that changes are coming, with three effective dates in 2027. The first, on 27 January 2027, changes how apps that target Android 17 may ask for a user's location.

Not yet independently verified. The dates and rules are from Google Play Console Help, which marks them as coming changes and does not give the date they were announced. Google says its policy summaries are overviews and the full policy takes precedence. Press coverage reported the changes on 18 November 2026. We will update this when it can be confirmed, and remove this note.

From 27 January 2027: location and contacts

Apps targeting Android 17 (API level 37 and above) must use the Android location button for one-time or infrequent location requests. To use ACCESS_FINE_LOCATION, the permission for precise location, a developer must submit a Play Console declaration "justifying why coarse location or the location button is insufficient".

The same date brings a restriction on broad access to a user's contacts. An app that does not need broad access for its core functionality must use the Android Contact Picker, which lets a user hand over only the contacts they choose.

From 14 April 2027: AppFunctions

AppFunctions is the Android interface through which an app exposes actions that AI agents and assistants can call. From 14 April 2027, developers must make sure their AppFunctions do not deceive or manipulate AI agents, bypass security controls or interfere with other applications.

From 25 August 2027: managing contacts and the local network

The Manage Contacts permission, which lets an app change the address book, will be limited to core app functionality where the system pickers are not enough. Apps targeting Android 18 (API level 38) or higher must declare their use in Play Console, and all other apps must use narrowly scoped platform intents. The Local Network permission, used to find and talk to devices on the user's network, is restricted in the same way, and apps targeting Android 17 or higher must declare it.

What app teams should do now

Audit your manifests for ACCESS_FINE_LOCATION, READ_CONTACTS, WRITE_CONTACTS and local network access, and for each one write down which feature needs it. Where a feature needs location only once, such as finding the nearest branch, plan the switch to the location button. Where precise location is truly needed, as in navigation or delivery tracking, draft the declaration now, with screenshots of the feature, so it is ready when the form opens.

Move contact selection to the Contact Picker where you can, which also tends to reduce the privacy questions users ask. If your app publishes AppFunctions, review what each function does and how it describes itself to an agent. Put the three dates in your release plan: the Android 17 targeting deadline will push most apps into the January rules within the year, and Google says its full policy text, not the summary, is what counts in a review.

Related on TrustList:

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in