MOBILE August 4, 2026 · 4 min read

Google Play's August Deadline Crunch: API Level 36 and AI Data Policy Both Land This Month

Two pressing Google Play deadlines converge in August 2026: new app updates must target Android 16 (API 36) by August 31, and Google's July policy update now explicitly requires User Data disclosures for any third-party AI integrations in your app.

By the AppsOps news desk · August 4, 2026 · Original source ↗

Two significant Google Play compliance items converge this August. By August 31, 2026, new apps and app updates must target Android 16 (API level 36) — or face being blocked from publishing updates. Simultaneously, Google's July 15 policy announcement made clear that any third-party AI integrations your app relies on now fall explicitly under Play's User Data requirements. If you ship on Android, this month has deadlines you cannot ignore.

The August 31 Target API Level Deadline

Google Play raises its minimum target API level annually, forcing apps to adopt the latest platform APIs and security protections. This year's enforcement has two distinct lines:

App type	Required target API	Deadline
New apps & app updates	Android 16 (API 36)	August 31, 2026
Existing apps (no recent update)	Android 15 (API 35)	August 31, 2026

The practical consequence of missing the existing-apps bar: your app stops appearing to new users on devices running a newer Android version than your target SDK. That's a quiet visibility penalty — not an immediate delisting, but a discovery gap that compounds as Android 16 adoption grows across the install base.

Google does offer an extension to November 1, 2026, but you must request it proactively through Play Console. Extensions are not automatic — silence is not tolerance.

What API 36 actually requires

Targeting Android 16 extends the edge-to-edge display enforcement that began with Android 15, and adds per-window large-screen adaptations covering foldables, tablets, and Chromebooks. Apps that haven't been tested against the current emulator targets may surface visual regressions in exactly the premium screen sizes Google is prioritising for discovery. If your Play Store screenshots still show the old notch-era status bar, they are already misleading users about how your app looks on current hardware — the edge-to-edge screenshot impact post from earlier this year covers the ASO implications in detail.

Your AI SDK Is Now Explicitly a Data Policy Concern

The more easily-missed change from the July 15 announcement: Google has clarified that its User Data requirements apply to third-party AI integrations specifically — not just SDKs in general. The policy already covered third-party libraries, but by calling out AI integrations by name, Google is signalling that it expects developers to actively document what those integrations do with user data, rather than assuming the model provider handles disclosure on their behalf.

If your app passes any user data — text inputs, voice, images, usage context — to an AI provider's API, you are now responsible for disclosing and documenting:

What data is sent to the AI provider, and in what form
The purpose for which it is sent
Retention and deletion behavior on the provider's side
User consent mechanisms and in-app disclosures

Reports suggest this clarification was partly driven by the surge in apps embedding LLM APIs without updating their Data Safety sections. Google's position is unambiguous: the developer — not the model provider — owns the disclosure obligation. If your Data Safety section says you collect no data but your app is quietly forwarding chat transcripts to a cloud model, that is now an explicit compliance gap, not a grey area.

It's not yet clear whether enforcement will come through automated review or targeted audits, but the safe assumption is that any app with AI features that hasn't revisited its Data Safety form since integrating an LLM API has an open compliance item. Pull up your Play Console Data Safety section and cross-reference it against every AI SDK or API call in your codebase.

Other Changes Effective This Month

Two smaller items from the July 15 announcement complete the picture:

Child safety / anonymous chat (August 26 deadline): New restrictions prohibit anonymous or random chat apps from targeting children, and the Families policy now explicitly bars such features. If your app has any chat or user-matching functionality and touches the Families policy at all, review the updated Child Safety Standards now — this deadline falls before the API level one.
Unrated apps: Google is formalising that apps without a completed content rating are not permitted on Google Play. If you have apps sitting without a rating in Play Console, remediate before they are flagged in review.

Quick Compliance Checklist

Check your current targetSdkVersion — aim for 36, minimum 35 for existing apps.
Test edge-to-edge and large-screen layouts against the API 36 emulator or a physical Android 16 device.
Audit every third-party AI API call in your codebase; update your Data Safety section to reflect what user data is transmitted.
If you need more time on the API level, request the extension in Play Console before August 31.
Verify every app has a completed content rating — unrated apps are now explicitly non-compliant.

For apps targeting multiple territories, Android 16 adoption will roll out unevenly across markets — a discovery penalty in a high-value tier-1 market can skew revenue significantly. AppsOps's territory overview and PPP pricing calculator can help you think through where compliance gaps hurt most.