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.
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
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:
- Location. Google introduces the location button as the recommended minimum scope for precise location. Its announcement says that for apps targeting Android 17 (API 37 and higher), the Android location button is mandatory for one-time or infrequent location requests. Apps that use
ACCESS_FINE_LOCATIONmust complete a Play Console declaration explaining why coarse location or the button is not enough. - Contacts. Apps that do not need broad access must use the Android Contact Picker.
- Call log. Account verification by phone call stops being an allowed use of
READ_CALL_LOG. Google points to the Digital Credentials API or the SMS Retriever API instead, and its announcement adds the SMS User Consent API as another alternative. A separate new exception lets Government or Authorized Mobile Network Operator apps useREAD_CALL_LOGfor Quality of Service reporting. - Foreground services. Geofencing is removed as an approved foreground service use case. Google says to use the Geofence API instead.
- Subscriptions. Subscriptions with ongoing eligibility-based discounts, such as student plans, must clearly disclose eligibility criteria, the verification process, and post-eligibility pricing and benefit changes.
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
- 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. - 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.
- 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.
- 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.
- 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
- What Google will do on a missed date. The announcement gives at least 30 days from 29 October for updates, and the deadlines page lists dates, not penalties.
- How strictly "core functionality" will be judged in declaration reviews.
- Whether the Play Console form for the August permissions is live. A secondary report (heise online, 18 November 2026) says the Local Network form will appear in June 2027. We did not find that on Google's pages.
This guide was prepared with AI assistance and reviewed on 19 November 2026.
Sources
- Google Play Console Help, Policy Deadlines (read 19 November 2026)
- Google Play Console Help, Policy announcement: October 29, 2026 (read 19 November 2026)
- heise online, Google will require Android apps to justify location access starting in January (18 November 2026; the June 2027 form timing appears here only, not on Google's pages)