Android

Google Play Publishing Requirements in 2026: Target API, Testing, Data Safety and More

What you need to publish an Android app on Google Play as of October 2026, from account type and D-U-N-S to target API level and the 12-tester rule.

2026-10-31 · 5 min

Publishing on Google Play takes more than uploading a build. Your account type affects what you must do first, the app has to meet a technical baseline, and you need to declare how it handles data. Skipping any of these can cost you weeks, so it's worth planning them before the final sprint. This guide covers Google's requirements as of October 2026. Check Play Console for the rules on your account, since it shows what applies to you.

Choose the right account type

Google Play offers personal and organization developer accounts, and both have the same core functionality. Personal accounts are meant for students, hobbyists and similar individual developers. Organization accounts are for businesses, including commercial and professional activity.

Some apps require an organization account. Google lists financial products and services, health apps, apps approved to use the VpnService class, and government apps. If your company is publishing a commercial product, the organization route is the natural choice anyway.

An organization account requires a D-U-N-S number, which Google uses to verify your organization. Applying through Dun & Bradstreet is free, and Google warns that some third-party services charge high fees for the same registration. Allow time for this step, as it sits outside your control.

Registration basics

You need to be at least 18, have an active Google Account, and accept the Developer Distribution Agreement. There is a one-time $25 registration fee, and Google doesn't accept prepaid cards. Identity verification is mandatory, and you may be asked for a government ID and credit card in your legal name. Google says the fee isn't refunded if the information is judged invalid, so enter details carefully. Personal accounts also have to verify access to an Android device through the Play Console mobile app before publishing.

The testing requirement for new personal accounts

Personal accounts created after November 13, 2023 must run a closed test with at least 12 testers who stay opted in for 14 consecutive days. If a tester opts out and comes back, their 14 days start again. Until this is done, Production and Pre-registration remain disabled in Play Console.

You then apply for production access by answering questions in three areas: your closed test, your app, and your production readiness. Google asks how easy testers were to recruit, how they used the app, what feedback you received, and what you changed as a result. Google says review usually takes seven days or less. It may also ask you to keep testing if testers weren't engaged enough, so give them real tasks rather than asking them only to install the app.

The help page we reviewed covers personal accounts only, so organization accounts should confirm their own status in Play Console.

Target API level

Google requires apps to keep up with recent Android versions:

  • From August 31, 2026, new mobile apps and updates must target Android 16 (API level 36) or higher.
  • Existing mobile apps must target Android 15 (API level 35) or higher to stay available to new users on newer Android versions.
  • Apps targeting lower levels remain available only on devices running Android versions at or below their target.
  • Wear OS, Android Automotive OS, Android TV and Android XR have their own thresholds.

Users who already installed your app keep access to it, but new users on newer devices won't find it. Google offers an extension to November 1, 2026 for developers who qualify, through a form sent to noncompliant apps. Apps restricted to an organization's internal users are exempt. Raising the target can also reveal behavior changes in your app, so allow time for testing rather than simply changing the number.

App format

New apps on Google Play must be published using the Android App Bundle, which has been required since August 2021. With this format, Google Play handles APK generation and signing. The compressed download needed to install an app can't exceed 4 GB, and asset packs have separate limits. Bundles don't support the older OBB expansion files.

Data safety and privacy policy

All developers with an app published on Google Play must complete the Data safety form, including apps on closed, open or production tracks. Even apps that collect no user data must complete it. Apps that are only on internal testing, system services and private apps are exempt.

You declare the following:

  • Which data types are collected or shared, including through third-party SDKs.
  • Why the data is used, such as app functionality, analytics or advertising.
  • Whether each data type is required or optional.
  • Whether data is encrypted in transit, and whether users can request deletion.

A privacy policy is also required. Your developers should list every SDK in the app and check what each one collects before anyone fills in the form, because you're responsible for accuracy, and Google can take enforcement action if app behavior doesn't match your declarations.

Android developer verification

Google is also rolling out developer verification across Android, including apps distributed outside Play. Its published timeline shows protections starting on September 30, 2026 in Brazil, Indonesia, Singapore and Thailand, with global expansion in 2027 and beyond. Google says Play automatically registers about 99% of apps, so apps on Play should see limited extra work, while anyone distributing outside Play should read the guidance closely.

A launch checklist

  • Correct account type chosen, with D-U-N-S number if needed.
  • Identity verification finished.
  • Build uploaded as an app bundle and targeting API level 36 or higher.
  • Closed test completed, if your account requires it.
  • Data safety form and privacy policy finished.
  • Time set aside for review.

Our team can help you prepare your Android app and handle the Google Play submission.

Talk to the team