Google Play’s new contacts-permission policy is moving into its next phase. During September 2026, developers whose apps request READ_CONTACTS are being prompted in Play Console to either submit a declaration showing that broad contacts access is required for core functionality or remove the permission and use Android’s more limited Contact Picker.
The policy applies to apps targeting Android 17 or later (API level 37+). Full enforcement is scheduled for January 27, 2027.
What Google Play is changing
Google’s policy is based on a minimum-scope principle: apps should not request broad access to personal and sensitive data when a system picker can provide the specific data the user chooses to share.
For contacts, that means an Android 17+ app may request READ_CONTACTS only when the Android Contact Picker is not sufficient to provide the app’s core functionality.
If the app continues to request READ_CONTACTS, the developer must complete a Play Console declaration explaining the access need and why the minimum-scope alternative is technically insufficient.
The timeline developers need to know
- April 15, 2026: Google announced the Contacts Permission policy.
- September 2026: Play Console begins prompting developers with apps that carry
READ_CONTACTSto submit a declaration or remove the permission and use Contact Picker where appropriate. - January 27, 2027: Compliance becomes mandatory for apps targeting Android 17 or later. Google says a 30-day automatic self-extension will be available in Play Console.
After the enforcement date, in-scope apps that are not compliant can be subject to policy enforcement.
When can an app still use READ_CONTACTS?
The permission is not disappearing. Google says it remains available when broad access is genuinely required for a user-facing core function and the app passes the appropriate review.
The key question is whether the application actually needs access to the user’s entire contacts dataset or whether the user can select the specific contact information needed for the task.
Examples such as full contact management may justify broader access more readily than a feature that only needs the user to choose one person.
What is the Android Contact Picker?
Android’s Contact Picker is the minimum-scope alternative Google wants developers to prefer. Instead of granting an app ongoing access to the address book, the user selects the contact data they want to share.
Google recommends using Intent.ACTION_PICK_CONTACTS for the Android 17 Contact Picker. The newer picker can request multiple data fields and supports scenarios such as work-profile contacts.
Google’s Play Console guidance also notes that the Android 17 Contact Picker is not backported to older Android versions. For apps targeting Android 17+, the system can upgrade existing Intent.ACTION_PICK flows to the new picker interface, but developers are encouraged to use the dedicated action directly.
What should developers audit now?
Before the January deadline, review every code path and dependency that can introduce READ_CONTACTS. The permission may come from your own manifest or from a library merged into the final application.
A practical audit should answer:
- Which user-facing feature requires contacts data?
- Does that feature need the entire address book or only user-selected contacts?
- Can Contact Picker provide the necessary fields?
- Is
READ_CONTACTSstill present in the merged release manifest? - If broad access is essential, can you clearly explain why to Google Play?
- Does your privacy disclosure accurately describe how contact data is used?
Why this matters beyond Play Console compliance
Contacts are highly sensitive because they contain information about people who may never have installed the app. Reducing broad access lowers the impact of an account compromise, malicious SDK or accidental data collection.
This fits a wider Android trend toward scoped access. Photo Picker reduced the need for broad photo-library permissions, and newer Android releases continue to move user data behind more explicit selection flows.
For an overview of Android’s permission model, see our Android App Permissions Guide 2026. Developers preparing for the current platform transition should also review our Android 17 features guide and our coverage of the September 30 Android developer verification requirements.
Who is exempt?
Google’s current Play Console guidance states that private and enterprise device-management apps are exempt from this contacts-policy declaration requirement. Developers should still review the complete policy for their distribution model rather than assuming an exemption based only on app category.

Start the conversation
Corrections, useful experiences and focused questions are welcome. Keep discussion respectful and on topic.