Google Play policy announcement (July 15, 2026): verification, permissions, and ‘quiet’ compliance cliffs

Original post (source): Google Play Console Help - “Policy announcement: July 15, 2026” (July 15, 2026)

• https://support.google.com/googleplay/android-developer/answer/17134731?hl=en

The gist

This is one of those policy updates that looks “mostly for engineers”, but it directly changes whether you can ship updates and how messy your onboarding and verification flows become.

The three bits worth caring about

1) Phone number verification: READ_CALL_LOG can’t be justified by “account verification via phone call”

Google says the SMS and Call Log Permissions policy will no longer permit account verification via phone call as a use case for READ_CALL_LOG.

They point teams to alternatives like:

• Digital Credentials API (phone number verification)
• SMS Retriever API

Why it matters: permission removals tend to become release blockers and store-review friction.

2) Developer verification and app registration checks

Google says you must ensure your Play apps are registered in Play Console to avoid removal, and references the broader Android developer verification requirements.

Why it matters: this is “compliance ops”. If nobody owns it, it fails at the worst possible time, mid-release.

3) The Aug 31, 2026 target API requirement

The reminder is explicit: apps need to meet the latest target API requirements by August 31, 2026.

Why it matters: if you miss target API deadlines, your growth roadmap gets held hostage by update eligibility.

Tiny win (15 minutes)

Make a single checklist called “Android distribution cliffs” with owners and dates:

• target API deadline (Aug 31)
• billing library / dependency deadlines (if applicable)
• developer verification / app registration status

Then put it where growth teams will see it (release calendar, not an engineering wiki).