Google Overhauls Android Contact Permissions in Upcoming Release to Enhance User Privacy and Ecosystem Consistency

Google has announced significant security and privacy changes coming to the Android ecosystem, fundamentally altering how applications interact with user contacts. In an upcoming Android release, applications targeting the new platform version will no longer be permitted to directly write to a user’s address book using the traditional WRITE_CONTACTS permission. Instead, developers will be directed to utilize standardized system contact intents, a shift designed to eliminate background modifications and create a more uniform user experience across various device manufacturers.

The impending policy shift addresses long-standing vulnerabilities within the Android permissions model. Previously, applications requesting the WRITE_CONTACTS permission were granted broad, sweeping access to create, modify, and delete contact data across the entire device. This level of access allowed background processes to alter address books without direct user interaction or awareness. Furthermore, while alternative methods like contact intents have existed for some time, their implementation varied wildly across different device manufacturers. Some custom editors dropped crucial data such as contact photos, while others suffered from inconsistent user interface behaviors, driving developers to rely on direct writes.

Under the new standards, standard contact intents—specifically ACTION_INSERT, ACTION_EDIT, and ACTION_INSERT_OR_EDIT—will behave consistently across all devices running the upcoming Android release and will require no special permissions at all. When an application invokes these intents, the Android operating system steps in to manage the heavy lifting, presenting a clean, standardized editor interface. For new entries, the system opens a streamlined half-sheet form, while updates to existing contacts allow users to easily search and integrate new information. Users retain the seamless option to expand these interfaces into full-page editors to input comprehensive details, all without granting the third-party application direct write privileges.

To facilitate a smooth transition for developers, Google is introducing optional data payloads known as Extras, which can be passed alongside intents to streamline the creation process. For instance, developers can pre-fill information such as names, phone numbers, target accounts, and even contact photos using properties like EXTRA_PHOTO_URI. Applications that previously executed complex batch operations through ContentProviderOperation and ContentResolver to save or update contact data will now need to restructure their workflows around these system-managed activities.

For developers whose applications require limited read access, Google highlights the Contact Picker, which has been available since Android 17 and operates entirely without permissions, enabling users to share specific contacts selectively. Meanwhile, calling and messaging applications that historically injected custom "Call with" or "Message with" rows directly into the user’s address book are being encouraged to adopt the upcoming People Directory. Arriving in Android 17 QPR2 in the final quarter of 2026, the People Directory provides a dedicated system directory where applications can publish reachability metadata, allowing users to initiate communications from the Phone or Contacts app without altering underlying contact records.

While the vast majority of applications will find their contact management needs completely fulfilled by the new intents and system directories, Google recognizes that a small subset of software requires broad, continuous access. To accommodate these specialized use cases, the company is introducing a new special app access permission called MANAGE_CONTACTS, arriving alongside Android 17 QPR2. Google Play published updated guidelines concerning contact access and the new permission to help developers determine their application’s compliance path.

The MANAGE_CONTACTS permission is strictly intended for applications whose core functionality revolves around comprehensive contact administration, where standard system intents are insufficient. This includes dedicated contact managers, dialer replacement applications, caller ID and spam protection services that perform mass updates to address books, background synchronization tools for enterprise or cloud accounts, bulk backup and restore utilities, device-to-device transfer tools, and applications that assign custom ringtones to individual contacts.

Conversely, applications that merely save contacts from a chat thread, scan business cards, add numbers or emails to existing entries, or let users pick contacts for payment or sharing purposes do not qualify for MANAGE_CONTACTS and must rely on standard intents or pickers. Developers requiring the special permission will be able to guide users to the system settings interface to grant access, though Google Play will require formal declarations from qualifying applications.

The rollout of these changes follows a defined timeline leading up to the release of the upcoming Android version. Google Play announced the MANAGE_CONTACTS policy in October 2026, setting the stage for the permission’s arrival in Android 17 QPR2. In 2027, with the launch of the upcoming Android release, the WRITE_CONTACTS permission will cease to grant write access for apps targeting the new platform version, and contact intents will be standardized across the ecosystem. Later that year, the Play Console will begin requiring declarations from applications utilizing the MANAGE_CONTACTS permission to ensure full policy compliance.