For developers · Checked 1 October 2026

Android Contact Picker and the new READ_CONTACTS rules

Short answer: apps that target Android 17 (API level 37) or later may request READ_CONTACTS only if the Android Contact Picker can’t support a core feature. Since September 2026 Play Console asks apps holding the permission to submit a declaration or remove it, and compliance is mandatory from January 27, 2027. The picker lets people share only the contacts and fields they choose, with no permission at all.

Does your use case justify READ_CONTACTS?

From Google’s declaration guidance and FAQ in Play Console Help, read 1 October 2026. Google reviews each declaration; examples are not exhaustive.

Use case	Declaration category	Google’s guidance
Contact manager, editing all contacts	Contact Management	Typically needs access
Dialer, SMS app, call history	Dialing or SMS, Call History	Typically needs access
Spam and call blocking	Call Screening	Typically needs access
Friend finder matching real-world contacts	Friend matching/search	Typically needs access
Contact backup and restore	Backup and Restore	Typically needs access
Keyboard autocomplete of names	Auto-Correct/Auto-Complete	Typically needs access
Invite or refer a friend, share a file	User-initiated selection	Typically should use the picker
Pick someone to pay or transact with	User-initiated selection	Typically should use the picker
Your own custom contact picker UI	None	Not a reason to keep access

How the Contact Picker works

Launch it with the ACTION_PICK_CONTACTS intent and list the fields you need, such as phone, email or postal address, as MIME types from ContactsContract.CommonDataKinds. The picker shows only contacts that have those fields, supports search, profile switching and multi-select with an optional limit, and returns a session URI you query with a ContentResolver. That URI grants temporary read access, so copy what you need right away. It is available on devices running Android 17 and higher.

Older target SDKs and existing ACTION_PICK code

For apps targeting Android 17 and higher, the system automatically upgrades an existing ACTION_PICK contact intent to the new picker. If you target a lower SDK, you can try the new behavior on Android 17 devices by adding the EXTRA_USE_SYSTEM_CONTACTS_PICKER extra to your ACTION_PICK intent.

Filling in the declaration

If you keep READ_CONTACTS, the Play Console declaration asks which user-facing features need it, choosing from the categories in the table or Other, and asks you to explain why the Contact Picker is not sufficient from a technical standpoint. Private and enterprise device management apps are exempt. The permission stays available after the deadline, but only for apps that pass this access review. Contacts count as personal and sensitive data under the User Data policy either way.

Other changes on the same date

January 27, 2027 also brings the location button as the recommended minimum scope for precise location, the end of READ_CALL_LOG for phone call account verification, and the removal of geofencing as a foreground service use case. All are summarized in Google Play policy updates 2026. For target API rules, see Google Play target API level.

Where Censuus fits

Asking for less builds trust at install; being found brings the installs. Censuus ranks apps by the visits they draw, and adding your app is free on the List my app form. Placement comes from traffic and sponsorship: apps climb on the visits they draw, and a sponsor can pay to rise higher.

Frequently asked questions

What is the Android Contact Picker?

A system interface in Android 17 and higher where people choose which contacts and which fields to share with an app, giving it temporary read access to only that data, without the READ_CONTACTS permission.

When does the Google Play contacts policy take effect?

Compliance is mandatory from January 27, 2027 for apps targeting Android 17 (API level 37) or later. Play Console started asking for declarations in September 2026.

Can I keep READ_CONTACTS for inviting friends?

Typically no. Google says apps that request it only for sharing files, collaborating, inviting or referring someone, or choosing a contact to transact with should not request it.

Does a custom contact picker justify READ_CONTACTS?

No. Google says an existing custom contact picking experience does not qualify as a reason to keep access.

Are any apps exempt?

Yes. Private and enterprise device management apps are exempt from the policy requirement.

Guides for app developers

Put your app in the ranking

Censuus ranks apps by the visits they draw and by sponsorship, no bots. Listing is free; sponsorship raises placement.

Submit your app See sponsorship Indie app landscape: apps and visits by category