Android 17 Breaks Away from “All or Nothing” With a Powerful New Contact Permission Manager

Tech media outlet Android Authority reported on November 14 that Android 17 is set to introduce a brand-new “Contact Picker,” a native tool designed to finally eliminate the long-standing “all-or-nothing” contact permission problem and deliver a major boost to user privacy.

According to the report cited by ITHome, the current contact-permission model in Android has been a persistent privacy headache. When an app requests access to your contacts, the system only offers two choices: grant full access to your entire address book, or deny it completely.

This broad, outdated approach forces users to give many apps far more information than they actually need, creating unnecessary exposure and increasing the risk of personal data leaks.

To address this issue, Google is preparing to roll out an all-new Contact Picker in Android 17. Code found in the latest Canary build reveals that this picker will function as a standalone system-level app with elevated processing priority.

When an app requests contact access, Android will invoke the new picker, allowing users to manually select one or more specific contacts to share—rather than handing over their entire contact list.

The new Contact Picker also enhances privacy by design. First, the contact information shared with an app will be “one-time only.” Even if a user later updates that contact—such as changing phone numbers—the app will not be able to retrieve the updated data. This prevents silent, long-term tracking.

Second, the updated mechanism allows developers to specify which data fields they need. For instance, an app can request only a name and phone number without gaining access to addresses, birthdays, or other sensitive details, enabling much finer-grained permission control.

To ensure broad adoption, the report notes that Google may follow the same strategy it used for the system-level Photo Picker. This would include back-porting the feature to older Android versions, offering official support through developer libraries, and eventually enforcing its use through Google Play Store policy requirements.