Google Play Review and Policy Basics

• Publishing needs a Google Play developer account, which has a one-time $25 registration fee.
• New personal accounts must run a closed test with at least 12 testers for 14 continuous days before production.
• Organization accounts skip that test but go through business verification instead.
• From August 31, 2026, new apps and updates must target Android 16, API level 36.
• The data safety form, privacy policy and permissions must match what the app really does.
• Apps that let users create accounts must also let them delete those accounts.

This guide covers what Google Play checks before and after an app goes live: the account you publish from, testing requirements, target API levels, store listing and data safety, permissions, account deletion and how to plan the timeline. Put plainly: plan for Google Play's rules from the first week, not the last one.

Google Play's requirements change often. Check the current Play Console Help and policy pages before you plan a launch.

Personal or organization. Businesses should usually register as an organization, under the business's legal name.

Organization verification. Google checks business details, which can take time. Start early.

Owned by the business. The account should belong to the company, with staff and agencies given access, never ownership.

One-time fee. Google Play charges a one-time $25 registration fee.

Who it applies to. Personal developer accounts created after November 13, 2023.

What it requires. A closed test with at least 12 testers who have been opted in for the last 14 days continuously, before you can apply for production access.

It's per app. Each new app on such an account needs its own closed test.

Plan the time. The 14 days can't be shortened. Start the closed test early, while you finish the store listing.

Real use counts. Testers should open and use the app during the test, not just join the list.

Organization accounts. Not subject to this rule, which is one more reason businesses should publish as an organization.

What it is. The Android version your app is built to work with.

The 2026 deadline. From August 31, 2026, new apps and app updates must target Android 16, API level 36 (Android Developers).

Existing apps. Apps that fall behind can lose visibility to new users on newer devices.

A yearly task. The target moves up every year, so it belongs in your maintenance plan, as covered in app maintenance.

Store listing. Title, descriptions, screenshots and graphics that describe the app accurately.

Content rating. A questionnaire that sets the app's age rating.

Target audience. Apps aimed at children have extra rules.

Data safety form. A declaration of what data the app collects, why, whether it's shared and how it's protected. It must match what the app and its third-party libraries really do.

Privacy policy. A public link that explains your data practices.

Ask only for what you need. Each permission should support a feature users can see.

Sensitive permissions need declarations. Access to things like background location, text messages or call logs requires extra explanation in Play Console, and may be refused.

Explain in the app. Tell users why you need a permission before the system asks.

Check your libraries. Third-party code can request permissions or collect data you didn't plan for. Shared code across platforms is covered in React Native strategy.

The rule. Apps that let users create an account must let them request deletion of that account and its data.

Inside the app and on the web. Users should be able to start deletion from the app, and from a web page you list in Play Console.

Explain what's kept. If some records must be kept for legal reasons, say so.

Digital goods and subscriptions. Selling them inside the app is subject to Google Play's billing rules, which vary by country and have changed in recent years.

Physical goods and services. Usually paid through your own payment processor.

Check the current rules. Before designing checkout, confirm what applies in the countries where you sell, as noted for Latin American markets.

Review times vary. Many apps are reviewed within days, but some take longer. Build in buffer.

Staged rollouts. Release updates to a percentage of users first and watch for problems.

Pre-launch reports. Google tests your app on real devices and reports crashes and issues.

Respond to rejections calmly. Read the policy cited, fix the issue and resubmit with a clear note.

The iPhone side. The App Store has its own review process, covered in building an iPhone app.

Policy updates. Google updates policies regularly and announces deadlines in Play Console.

Yearly target API updates. Plan them like any other maintenance, as costed in app maintenance: the cost after launch.

Keep forms current. Update the data safety form whenever the app or its libraries change.

Watch your inbox. Policy notices go to the account's contact emails; make sure someone reads them.

Time to production. From first upload to public release.

Review outcomes. Approvals, rejections and the policies cited.

Policy warnings. Notices received and how quickly they were resolved.

Target API compliance. Whether each app meets the current requirement before the deadline.

Crash-free sessions. After each staged rollout.

Register as an organization and start verification. Plan target API, permissions, data collection and account deletion from the start. Write the privacy policy.

If your account is personal, start the 12-tester, 14-day closed test early. Complete the store listing, content rating and data safety form. Declare any sensitive permissions.

Submit for review with buffer time, release in stages and watch pre-launch and crash reports. Put target API updates and policy checks on the yearly maintenance calendar.

Astra Results Marketing plans Google Play's rules from the first week of every Android project. We set up the developer account in your business's name, build to the current target API, keep permissions minimal and complete data safety, privacy and account deletion requirements accurately.

We plan around testing and review times, release in stages and keep apps compliant as policies change. Engagements begin with a launch readiness review through our Android app development team.

Related reading

• App Maintenance Response Times and Severity Levels
• Android Apps for Latin American Markets
• App Maintenance: The Cost After Launch

Google Play charges a one-time $25 registration fee for a developer account. Building, testing and maintaining the app are separate costs.

Personal developer accounts created after November 13, 2023 must run a closed test with at least 12 testers opted in for 14 continuous days before applying for production access. Organization accounts aren't subject to it.

An organization account, registered in the business's name. It avoids the closed testing rule for personal accounts and keeps ownership with the company, though it requires business verification.

From August 31, 2026, new apps and updates must target Android 16, API level 36. The requirement rises every year, so plan updates annually.

A Play Console declaration of what data your app collects and shares, why, and how it's protected. It must match what the app and its third-party libraries really do.

Yes. Apps that let users create accounts must let them request deletion of the account and its data, both in the app and through a web page listed in Play Console.

Ready to launch on Google Play without last-minute surprises? Astra Results Marketing plans for Google Play's rules from week one: the right account, current target API, minimal permissions, accurate data safety and account deletion, with testing and review time built into the schedule. ▸ CALL (786) 321-2866 · ▸ REQUEST YOUR CONSULTATION