Ren Hollis

Google Play Pre-Flight: the deadlines and declarations that block Android launches

Short answer: Google publishes no equivalent of Apple's transparency report — there are no official Play submission or rejection totals to quote, and this page won't borrow Apple's numbers and pretend they're Google's. What Google does publish is the machinery that blocks launches: hard deadlines (target API 36 for new apps and updates since August 31, 2026), per-permission declarations, a Data safety form you're legally responsible for, and an enforcement ladder where the difference between a rejection and a suspension is the difference between a delay and a strike against your account. All of it is checkable before you submit.

Decode a Play rejection — free
The decoder has a Google Play mode with 12 Play policy patterns.

The Play numbers that are actually published (Play Console Help, October 2026)

RequirementCurrent figureWhat happens if you miss it
Target API — new apps & updatesAPI 36 (Android 16) since Aug 31, 2026 (Wear OS / Automotive: API 35; TV / XR: API 34)Play Console blocks the submission before review. An extension to November 1, 2026 exists — once, and it doesn't renew.
Target API — existing appsAPI 35 minimum to stay visibleBelow that, new users on newer Android versions simply stop seeing your app. No email, no rejection — your installs just die.
Closed testing gate (new personal accounts)12 testers opted in for 14 continuous days, accounts created after Nov 13, 2023No production access at all until the test completes and Google approves your application.
Enforcement ladderRejection → Removal → Suspension (strike) → Account terminationMultiple strikes can terminate your developer account — and related accounts with it.

What Play blocks on, and what Pre-Flight checks

  • Target API level — deterministic: your bundle's targetSdk against the current floor for your form factor. The full requirement →
  • Permissions declarations — photo/video access, foreground service types (with the demo-video requirement), exact alarms, health permissions. Each restricted permission is a form, a justification, and a review. Permissions declarations →
  • Data safety accuracy — the form must match your app and every SDK in it, and agree with your privacy policy. Google states plainly that its review is not designed to verify your declarations; a wrong form can pass review and be enforced later. Data safety mistakes →
  • Deceptive behavior & Families — listing claims you can't demonstrate, and target-audience rules when children are in scope. Deceptive behavior →
  • Process gates — the closed-testing requirement and knowing which enforcement action you actually received before you respond. Closed testing →

Shipping on iOS too? Apple's side runs on published rejection data — 2,093,244 rejections in the 2025 transparency report — and a different rulebook: App Store Pre-Flight →

One pre-sale covers both stores

The Pre-Flight Founding pre-sale ($29) includes the Google Play check alongside the App Store check — same gate, same terms: the full checker is built only if at least 10 founding pre-sales land within 30 days of first traffic; if the gate is missed, every pre-sale is refunded in full and the decoder and guides stay live.

Get the $29 Founding pre-sale

Frequently asked questions

Why are there no Play rejection statistics on this page?

Because Google doesn't publish them. Apple releases an annual transparency report with submission and rejection totals; Google Play has no equivalent public report, so any "Play rejection rate" you see quoted elsewhere is estimated, borrowed, or invented. We'd rather show you the published deadlines and rules — which are what actually block your launch.

Is a Play rejection the same as a suspension?

No, and confusing them is expensive. A rejection blocks one submission and doesn't touch your account standing. A suspension removes the app, bans the bundle, and counts as a strike. The decoder's enforcement pattern walks through which one you got and what route back applies to each: decode the notice.

Does the free decoder work for Play messages?

Yes — toggle it to Google Play. It covers 12 Play patterns: target API, closed testing, photo/video permissions, foreground services, exact alarms, health declarations, Data safety, privacy policy, account deletion, deceptive behavior, Families, and the enforcement ladder.

Sources

  • Play Console Help, Target API level requirements for Google Play apps — API 36 floor from August 31, 2026; API 35 existing-app floor; extension to November 1, 2026. Retrieved October 23, 2026.
  • Play Console Help, App testing requirements for new personal developer accounts — 12 testers, 14 days, accounts created after November 13, 2023. Retrieved October 23, 2026.
  • Play Console Help, Enforcement Process — rejection, removal, suspension, restricted account, and termination definitions. Retrieved October 23, 2026.
  • Google Play Developer Policy Center — Permissions and APIs that Access Sensitive Information; User Data policy and Data safety; Deceptive Behavior; Families policies. Retrieved October 23, 2026.

Last updated October 23, 2026. Play deadlines move every August; the target API figures above are the ones in force on the date shown.

Decode your rejection — free

The decoder covers 41 documented rejection patterns across the App Store and Google Play, grounded in the stores' own published rules. Three free decodes; the $29 Pre-Flight Founding pre-sale unlocks unlimited decoding plus a full pre-flight check credit when the checker ships.

Open the free decoder

The decoder classifies and guides from the message you paste. It cannot see your app or your binary, and it never promises an approval outcome — that decision is always the store's.