Google Play in 2026: The Policy Changes That Actually Affect Your Launch
Target API 35, the 12-tester rule, tightened data-safety enforcement, and account deletion — the changes most likely to get a 2026 submission rejected, and how to stay clear.
Google ships dozens of policy updates a year, but only a handful change what you must do before you can hit "submit." Here are the ones that matter most for a 2026 launch.
Target API level 35 is now mandatory
Every new app and every update must target Android 15 (API level 35). Submissions below that threshold are rejected at upload. If your Gradle config still points at an older compile or target SDK, fix it before anything else — no listing work matters until the bundle is accepted.
The 12-tester, 14-day rule still bites new accounts
Personal developer accounts created after November 2023 must run a closed test with at least 12 testers for 14 continuous days before requesting production access. Plan for this early; it is the single biggest cause of "why can't I publish?" support tickets.
Data safety enforcement got stricter
Google now cross-checks your declared data collection against the SDKs detected in your bundle. A mismatch — declaring "no data collected" while bundling an analytics SDK — is a fast rejection. Declare every SDK that touches user data, including crash reporters.
Account deletion is non-negotiable for accounts apps
If your app lets users create an account, you must provide an in-app and web path to request account and data deletion. Missing this is a common last-minute blocker.
How to stay clear
Run a full compliance pass before you build your store listing. Fixing a bundle-level issue after you've written descriptions and uploaded screenshots wastes the most time. Playstore Wizard checks all of the above automatically before you submit.