Google Play’s Oct 29 restricted permissions are a picker-first test — a branded contacts UI does not qualify
The Oct 29 Google Play updates extend an existing pattern — use the platform picker or intent unless you can technically justify why it cannot provide core functionality, then file a Google Play Console declaration — to MANAGE_CONTACTS and ACCESS_LOCAL_NETWORK; a custom branded contacts UI is explicitly not a qualifying reason, and the real enforcement clocks are mid/late 2027, not “30 days from the announcement.”
It is the same test Google Play already uses for photos and contacts
Google Play's help page on restricted permissions with minimum scope alternatives says an app should only request and carry these sensitive permissions if minimum scope alternatives (system pickers, platform intents, Sharesheet) are not sufficient to provide core app functionality. Photos and videos went through this first (full compliance mandatory May 28, 2025). READ_CONTACTS followed: announced April 15, 2026, mandatory January 27, 2027 for apps targeting Android 17 or later (API level 37+), with the Android Contact Picker as the alternative. On October 29, 2026 Google Play added two more permissions to the same pattern.
Manage Contacts (MANAGE_CONTACTS)
- Alternative: platform intents.
ACTION_INSERTcreates a contact,ACTION_EDITchanges one, andACTION_INSERT_OR_EDITcovers both. They open the system editor, where the user reviews and confirms the change, and your app can pre-fill fields such as name and phone number. - Who qualifies: apps whose core functionality relies on programmatic or bulk contact management. Google Play's examples are dedicated contact manager apps and enterprise sync adapters.
- What does not qualify: the help page FAQ asks whether an existing custom contact creation or editing interface qualifies an app. The answer is no: wanting to keep a custom, branded user experience is not a reason to get this permission. An app that only adds or edits a single contact, for example from a chat thread, should move to the intents.
- Related change: the same page says that for apps targeting API level 38 or higher,
WRITE_CONTACTSno longer lets an app create, modify, or delete contacts. Writes to the Contacts Provider will throw aSecurityException, which your app should handle rather than assume the write succeeded. An app that qualifies forMANAGE_CONTACTSdoes not need to requestREAD_CONTACTSseparately for standard contact management.
Local Network (ACCESS_LOCAL_NETWORK)
- Scope: apps targeting Android 17 or higher (API level 37+) may request it only if it is necessary for core functionality and device pickers such as
NsdManagerare not sufficient. TheNsdManagerdevice picker runs on Android 13 or higher (API level 33+) with up-to-date Google Play system updates. - Declaration use cases listed: peer-to-peer interaction (local multiplayer, device-to-device file transfer), smart device and IoT control, network infrastructure and diagnostics, and media casting.
- Casting option: apps using the Google Cast SDK can opt in to the System Output Switcher (Android 13 and higher) to cast without requesting
ACCESS_LOCAL_NETWORK. This is optional. - Not affected: the
INTERNETpermission stays available. For apps targeting Android 16 and lower it still gives local network access.
The calendar: two official wordings, quoted separately
| Google Play Console prompt | Mandatory date, help page | Mandatory date, Policy Deadlines table | |
|---|---|---|---|
MANAGE_CONTACTS | Summer 2027 | “August 2027” (all apps; 30-day automatic extensions in Console) | 2027-08-25 |
ACCESS_LOCAL_NETWORK | June 2027 | “August 25, 2027” (apps targeting Android 17+; 30-day automatic self-extension) | 2027-08-25 |
For Manage Contacts, the help page gives a month and the deadlines table gives a day. We quote both rather than merge them. Check both pages again before you set an internal date.
Why “at least 30 days” is not your deadline
The October 29, 2026 announcement says you will have at least 30 days from that date to comply and points to the Policy Deadlines page. That sentence is a minimum notice period. For these two permissions, the Policy Deadlines table and the help page put the mandatory dates in 2027. Nothing on those official pages sets a late-November 2026 deadline for these two permissions.
What to do now
- Inventory. List every build that declares or requests
MANAGE_CONTACTS,ACCESS_LOCAL_NETWORK,WRITE_CONTACTS, orREAD_CONTACTS(the last one matters once you target Android 17). Include SDKs that add permissions to your merged manifest. - Switch where you can. Use the contact intents for single-contact create or edit flows, the Contact Picker for selecting contacts, and the
NsdManagerdevice picker for finding one device or service on the local network. Then remove the broad permission. - If you still need the broad permission, prepare the case first. The published declaration forms for
READ_CONTACTSandACCESS_LOCAL_NETWORKask which user-facing features need the permission and why the picker is not sufficient. ForMANAGE_CONTACTS, Google Play asks you to be ready to explain why the platform intents are not sufficient from a technical standpoint. Write it per feature. “Our own UI looks better” is the answer the FAQ already rules out. The restricted permissions page also exempts private and enterprise device management apps. - Plan by the published dates, not by the announcement date plus 30 days: the Console prompt (Summer 2027 or June 2027), then the mandatory date, then the 30-day automatic extension available in Google Play Console.
What this article is not
It is not about the trader status declaration or developer identity verification. Those are account checks; this is a per-app permission declaration (see [/insights/play-trader-status-three-steps/](/insights/play-trader-status-three-steps/) and [/insights/google-play-dev-verification-4-countries/](/insights/google-play-dev-verification-4-countries/)). The October 29 update also includes AppFunctions (2027-04-14) and subscriptions with ongoing eligibility-based discounts (2027-01-27). Those work differently; see the Policy Deadlines page.
Not legal advice. Wording is paraphrased from Google Play's public help pages as fetched on 2026-11-10. Check the current pages before you act.
Sources
- Policy announcement, October 29, 2026 https://support.google.com/googleplay/android-developer/announcements/13412212?hl=en
- Policy Deadlines https://support.google.com/googleplay/android-developer/table/12921780?hl=en
- Understanding Restricted Permissions with minimum scope alternatives https://support.google.com/googleplay/android-developer/answer/16935362?hl=en
- Permissions and APIs that Access Sensitive Information https://support.google.com/googleplay/android-developer/answer/16909972?hl=en
- Google Play Policies (Android Developers) https://developer.android.com/distribute/play-policies
- Google Play PolicyBytes, October 2026 policy updates https://www.youtube.com/watch?v=3eyIKAAzY9Y