Google Play READ_CALL_LOG: the end of account verification by phone call

Who is concerned

Apps that use the READ_CALL_LOG permission to verify an account through a phone call.

Other uses of the call log remain governed by the rest of the policy.

What changes

• Account verification via phone call is removed as a permitted use case of READ_CALL_LOG.
• Google names the alternatives: the Digital Credentials API, used directly or through a verification provider built upon it, and the SMS Retriever API. The October 29, 2026 announcement adds the SMS User Consent API as a privacy-preserving option.
• The call log permission group (READ_CALL_LOG, WRITE_CALL_LOG, PROCESS_OUTGOING_CALLS) still requires the app to be actively registered as the default Phone or Assistant handler on the device.
• The October 29, 2026 announcement added an exception for Government or Authorized Mobile Network Operator apps that use READ_CALL_LOG for Quality of Service reporting.

What to do

• Find out whether your app reads the call log to verify accounts.
• Choose the replacement that fits: Digital Credentials API phone number verification, SMS Retriever or SMS User Consent.
• Remove the permission from the manifest when the new flow ships, and review your Play Console declaration for call log access.

What happens after the date

Google’s table gives the date and the removal of the use case. It lists no separate enforcement steps, so check your Play Console messages for any notice about your app.