Google Play policy update (July 15, 2026): phone verification via READ_CALL_LOG is out, and app registration is now a hard requirement
Google’s July 15 policy announcement has two practical ‘don’t get removed’ items: (1) you can no longer justify READ_CALL_LOG for account verification via phone call, and (2) you must register your Play apps in Play Console (including apps you distribute outside Play, if you want installs on certified devices). It also clarifies that User Data rules apply to third-party AI integrations.
Original article (source): Play Console Help - “Policy announcement: July 15, 2026” (July 15, 2026)
The headline
This is a compliance update that can quietly break shipping if you leave it to the last minute.
Google bundles a few changes together, but there are two that are immediately actionable for most teams.
1) READ_CALL_LOG can’t be justified for phone-call verification anymore
Google states that the SMS and Call Log Permissions policy will no longer permit account verification via phone call as a use case for the READ_CALL_LOG permission.
They point developers toward alternatives:
- Digital Credentials API (phone number verification)
- SMS Retriever API
If you are still leaning on call log access for onboarding flows, this is a “refactor now” warning.
2) App registration in Play Console is now a hard requirement
To meet Android developer verification and Play Console requirements, you must register your Play apps in Play Console.
They note that most apps were registered automatically, but the action item is explicit: check Play Console and register any remaining apps you want to continue distributing.
They also add a second-order implication that matters for distribution strategy: you can register apps you distribute outside of Google Play so they can still be installed on certified Android devices.
Clarifications worth noting (AI + data safety)
Google also clarifies that User Data requirements apply to third-party AI integrations. That is the “you own the compliance” reminder if you are piping user data into an external model.
Tiny win
Make a one-page “policy surface” checklist for your next release:
- Do we request any sensitive permissions that we can replace with a modern API?
- Are all live apps registered in Play Console, including non-Play builds that need certified installs?
- If we use third-party AI, can we point to disclosure, consent, and limited-use compliance in one place?
Read the original: https://support.google.com/googleplay/android-developer/answer/17134731?hl=en
Want help with ASO?
If you want this implemented for your app, check out our services - or run your workflow in APPlyzer.