SamoTech

TECHNOLOGY • APPS • IDEAS

SamoTech / Android Is Taking Away Apps' Silent Write Access to Your Contacts: What Changes, What Does Not and What MANAGE_CONTACTS Is

Android Is Taking Away Apps' Silent Write Access to Your Contacts: What Changes, What Does Not and What MANAGE_CONTACTS Is

Android and Privacy

Google has announced that apps built for a future Android release will lose the broad permission they use today to change your contacts. This article explains what Google says is changing, what you will notice as a user and what is still undecided. It is based on Google's Android Developers' Blog post of October 21, 2026, a Google Play policy notice from October 5 and Android Authority's coverage of Android 17 QPR2. It did not test any of this on a phone.

What is changing

Today an app that asks for the WRITE_CONTACTS permission can add, edit and delete entries across your whole address book, including in the background. Google says most apps do not need that. Apps that target the upcoming Android release will no longer be able to write to contacts directly. Their writes will be rejected with a SecurityException or a permission denial. Instead they are told to hand the job to the system's contact editor through three standard intents: ACTION_INSERT, ACTION_EDIT and ACTION_INSERT_OR_EDIT.

What you would see as a user

  • A standard editor: Google says the intents will open a half-sheet form for a new contact, or let you search for an existing contact to add information to. You can expand it to a full page. Google marks the mock-ups it shows as "UX not final".
  • You stay in control: because the system editor does the saving, the app does not need write permission to add one contact you asked for.
  • Consistent behavior: Google says the three intents behaved differently from device to device, for example dropping a contact photo or saving when you pressed Back. It says devices running the new release must follow the same standard. Manufacturers may restyle the editor, but the behavior is meant to stay the same.
  • Picking contacts: an app that only needs contacts you choose can use the Contact Picker, which Google says has been available since Android 17 and needs no permission.

The exception: MANAGE_CONTACTS

For the small set of apps that really manage contacts, Google adds a new special app access permission called MANAGE_CONTACTS. It arrives in Android 17 QPR2, and Android Authority's QPR2 overview says a new permission system for apps editing contacts lands with that release. It is not a pop-up. You would turn it on under Settings, Special app access, Manage contacts. It covers reading, adding, editing and deleting contacts. Google's examples of apps that likely qualify are dedicated contact managers and dialer replacements, caller ID and spam apps that update many entries, apps that sync with an enterprise or cloud account in the background, backup and transfer apps, and apps that set custom ringtones for individual contacts. Google says an app with its own branded editing screen does not qualify on that basis alone.

Apps that want to publish on Google Play with MANAGE_CONTACTS will need to submit a declaration in Play Console explaining why the intents are not enough.

What does not change right away

  • Google says the WRITE_CONTACTS change applies only to apps that target the upcoming Android release and later. Apps that target older versions keep their current behavior.
  • The new standardized editor is meant to be available to all apps on the new OS, whatever their target version.
  • There is no intent for deleting contacts. Only apps with MANAGE_CONTACTS could delete them directly.

Reading contacts is a separate rule

A Google Play notice from October 5 covers the READ_CONTACTS permission. It says that from January 27, 2027, Google Play will enforce a declaration requirement on apps that target Android 17 or later (SDK 37 or higher) and use READ_CONTACTS. Developers can submit a declaration, ask for a 30 day self extension, or remove the permission and use the Contact Picker. That rule is about reading, and the Android blog post is about writing.

What is still unknown

  • Which Android version Google means by "the upcoming Android release". The blog post does not name it and gives only 2027.
  • The exact date the write restriction takes effect. Google's timeline gives "2027" for the restriction and for the Play declaration.
  • Which specific apps will apply for MANAGE_CONTACTS.
  • How the final editor will look. Google's images are marked as not final.
  • How any of this behaves on a real phone. Neither Google's posts nor this article is a hands-on test.

Related: another change Google has announced for app developers, the April 2027 foldable and large-screen requirements on Google Play, is covered in Google Play Will Require Foldable-Ready Apps From April 2027.

Sources, read in full November 19, 2026: Android Developers' Blog, A more reliable way to add and edit contacts on Android; Google Play Developer Community, Contacts Permissions policy notice; Android Authority, what's new in Android 17 QPR2. Based on those pages, not a hands-on test.

Join the discussion on Blogger