Google is taking away the broad contacts write access that many Android apps request today. From the next major Android release, due in 2027, apps that target it can no longer edit contacts directly with WRITE_CONTACTS. Nothing changes on your phone today. The protection arrives as apps update for that release.

Why Google is restricting the Android contacts permission
WRITE_CONTACTS is the permission an app asks for when it wants to save or change a contact. Google’s problem with it is scope.
But that permission grants broad access, allowing an app to make widespread changes to contacts across the device in the background, even without user interaction.
That’s from Google’s Android Developers Blog post published on October 21. Google’s point is that most apps need far less than that. Saving one number from a chat doesn’t require a device-wide pass over your address book.
How saving a contact will work instead
Apps targeting the 2027 release will open a standard system contact editor instead. You see a half-sheet form, which can expand, and you confirm the change yourself. The trade-off is one extra tap whenever an app saves a contact.
The new editor is available to all apps on the new OS, whatever version they target. Phone makers can restyle it, but its behaviour has to stay consistent across devices. Google labels its current mockups as not final.
MANAGE_CONTACTS: the new permission for contact-heavy apps
Some apps genuinely manage contacts, and they get a separate route. MANAGE_CONTACTS arrives in Android 17 QPR2 in the fourth quarter of 2026. It is a special app access permission, not a pop-up. You switch it on yourself under Settings > Special app access > Manage contacts.
The permission covers reading, adding, editing and deleting contacts. Apps on Google Play must also file a Play Console declaration explaining why the standard editor isn’t enough.
Google lists these as apps that likely qualify:
- Contact managers: dedicated contact apps and dialer replacements.
- Caller ID and spam apps: ones that mass-update contact entries.
- Sync tools: enterprise or cloud background sync.
- Backup and transfer: bulk backup, restore or phone-to-phone moves.
- Ringtone apps: ones that set per-contact ringtones.
Apps that don’t qualify include those that save a contact from a chat, business card or order. Adding a number to an existing contact, picking contacts to invite or pay, and branded contact screens don’t qualify either.
Calling and messaging apps that add their own call rows to your contacts get a different home. Google wants them to move to a new People Directory, also arriving in Android QPR2 in Q4 2026.
Timeline
- October 21, 2026: Google Play announces the MANAGE_CONTACTS policy.
- 2026, Android 17 QPR2: MANAGE_CONTACTS becomes available.
- 2027, upcoming Android release: WRITE_CONTACTS stops granting write access to apps targeting that release, and contact intents are standardized across devices.
- 2027, not earlier than that release: Play Console declaration and Play policy compliance required.
The catch: it depends on app updates
This is a clear privacy win for Android users. An updated app won’t be able to rewrite your address book in the background unless you’ve granted it Manage contacts access in Settings. However, apps that keep targeting older Android versions keep today’s behaviour. The protection reaches you only as each app updates its target.
For more on that update, see our coverage of Android 17 QPR2 Beta 7.
Source: Android Developers Blog






