OOmnistu

Blog / App Development Cost

App Development Cost

Google Play's 2027 permission deadlines: location, contacts, call log, AppFunctions and local network

Five Google Play permission changes land on 27 January 2027, with AppFunctions rules on 14 April and two restricted permissions on 25 August. The official dates, what each change requires, the exceptions, and what Google's pages do not say.

OOmnistu
Reviewed 2026-11-19 · 5 min read

Google's Play Console Help pages list a run of permission and API policy deadlines in 2027. Some were announced in April and July 2026, and the rest on 29 October 2026. Several land on 27 January 2027, so a team shipping an Android app now has about ten weeks. This guide lists each date and what Google's own pages say it requires. It does not interpret how Google will enforce them. Everything below comes from Google's Policy Deadlines page and its 29 October 2026 policy announcement, both read on 19 November 2026. We did not test any app.

The dates

Timeline of Google Play policy deadlines: 1 December 2026 Japan payments authorization; 27 January 2027 location button and fine location declaration, Contact Picker, call log account verification, geofencing foreground service removal, eligibility-based subscription disclosures; 14 April 2027 AppFunctions rules; 25 August 2027 local network and manage contacts declarations.

Original timeline by Omnistu from Google's Policy Deadlines page and 29 October 2026 announcement. Not Google's figure.

27 January 2027. Five changes share this date on Google's Policy Deadlines page:

14 April 2027. AppFunctions rules. Developers building AppFunctions must follow all existing Play policies, and AppFunctions are "strictly prohibited" from deceiving or manipulating AI agents, bypassing security controls, or interfering with other apps.

25 August 2027. Two new restricted permissions. The Local Network permission is limited to apps that need it for core functionality when device pickers are insufficient, and apps targeting Android 17 or higher must submit a Play Console declaration. The Manage Contacts permission is restricted the same way, and all other apps must use narrowly scoped platform intents.

Two dates outside the 2027 list

The same announcement reminds developers of two earlier items. If you sell into or out of Japan, you must complete authorization by 1 December 2026, or payments will be held globally. And from November 2026 developers must declare trader status in Play Console. The announcement also notes a February 2027 compliance deadline for new app quality requirements on memory and code optimization thresholds; that is an app-quality item, not a permission change, so it sits outside this guide. Check whether any of these apply to your account.

A short checklist, our suggestion

  1. List which permissions your manifest requests. Search for ACCESS_FINE_LOCATION, READ_CONTACTS, WRITE_CONTACTS, READ_CALL_LOG, any local network access, and foreground services declared for geofencing.
  2. For each, ask the question Google asks: is a system picker, the location button, or a narrower scope enough for the feature? If yes, switching is the lower-effort path.
  3. If not, plan the declaration. Google requires a written justification in Play Console for fine location, and later for Local Network and Manage Contacts. Write down the user-facing feature that needs it.
  4. Check subscriptions. If any plan has an ongoing eligibility discount, make sure the screen states who qualifies, how it is checked, and what happens after.
  5. Re-check Google's pages before shipping. Policy Deadlines can change, and Google says each linked policy page has the full text.

What these pages do not say

This guide was prepared with AI assistance and reviewed on 19 November 2026.

Sources