Android developer verification: what changes on 30 September 2026

From 30 September 2026, an unverified developer's apps will be blocked from installing on certified Android devices in Brazil, Indonesia, Singapore and Thailand, and any Play app you have not registered in Play Console risks global removal on the same date. If you publish on Google Play and your apps were registered automatically, which Google says covers most of them, you may have nothing to do. Checking takes one page load, and the consequence of not checking is your app disappearing.

Two requirements share that date, and they are not the same thing.

Requirement one: register your apps in Play Console

This is the one that can bite an ordinary Play developer who has never heard of developer verification. Google's Policy Deadlines page, deadline 2026-09-30, announced 2026-07-15:

To meet Android developer verification requirements and Play Console requirements, you must register your Play apps in Play Console. While 99% of apps on Play have been registered automatically, you should check your Play Console Home page and register any remaining apps you want to continue distributing to avoid global removal from Google Play and ensure a seamless user installation experience.

You can also use Play Console to register apps you distribute outside of Google Play to ensure they can be installed on certified Android devices.

Note "global removal from Google Play". That phrase is not limited to the four countries. Open your Play Console Home page and look for anything unregistered. Google's own figure says 99% of apps were handled automatically, which is reassuring and also means one in a hundred was not.

Registration is how a package name gets tied to a signing key and an identity. If you distribute the same app both on Play and directly from your own site, the second sentence above matters: you can register a package you ship outside Play so that it still installs on certified devices.

Requirement two: verify your identity

This is the wider programme, and its scope is what makes it significant. It is not a Play Store rule. It is an Android platform rule about who is allowed to have apps installed on certified devices at all, whatever channel the app arrives through.

Google's wording:

These protections begin for users installing apps from participating stores (Google Play, HONOR App Market, OPPO App Market, Galaxy Store, Palm Store, V-Appstore, GetApps) in Brazil, Indonesia, Singapore, and Thailand, on certified devices running Android 7+. In 2027, we'll expand this globally to all apps on certified devices.

The published timeline is short:

When What
August 2026 Developer APIs, limited distribution accounts and the power user advanced flow launch
30 September 2026 Enforcement begins in Brazil, Indonesia, Singapore and Thailand, on certified devices running Android 7 or later
2027 Expansion "globally to all apps on certified devices"

And the consequence, from Google's FAQ:

If you do not verify your identity and register your apps by the September deadline, your apps will be blocked from being installed by users on certified Android devices in applicable regions.

"Blocked from being installed" applies to new installs. It is not a remote uninstall.

The two account types, and why the free one matters

Google has published two tiers, and the second one is the answer to the objection most people raised when this was announced.

Full distribution account. Requires government ID verification. Google describes a 25 dollar registration fee, in line with a Play Console account. Unrestricted distribution, and Google notes it "can use multiple signing keys for a single package".

Limited distribution account. No government ID. No fee: Google's wording is "We are waiving the fee for developers who qualify for a Limited Distribution account". It is described as being for "teachers, students, and hobbyists", and it is capped: you can "distribute apps to 20 devices". Google also states that once an account is upgraded to full distribution it cannot be converted back.

If you build an app for a classroom, a family, a club or a side project you never intend to sell, the limited account is the route and it costs nothing. Twenty devices is a real limit, not a soft one, so plan around it.

Organisation accounts are verified with a D-U-N-S number rather than an ID. If you do not already have one, Google's guidance on the Play Console side is that requesting one "can take up to 30 days so you should plan ahead". Start that now if it applies to you, because there is no realistic way to compress it.

What still works without verification

Google's FAQ names several carve-outs, and they are worth knowing before you assume the worst:

  • Installs over ADB work without verification, so your own development loop is unaffected.
  • Enterprise apps distributed through an organisation's own store do not require verification.
  • Developers in sanctioned countries are excluded from enforcement.
  • Uncertified devices are outside the scheme. The requirement is specifically about certified Android devices.

There is also an escape hatch for users rather than developers. Google describes an "advanced flow" for power users who want to install unverified apps, involving enabling developer mode, a 24 hour waiting period and biometric authentication, described as a one-time setup rather than a per-app prompt. Do not build a distribution plan on it. A 24 hour wait is a wall, not a door, for anyone who is not already determined.

The privacy question, stated accurately

There are two separate things here and they get merged constantly. Keeping them apart is the difference between a real concern and a rumour.

What the verification programme itself says. Google's FAQ states that "We use your personal information to verify your identity, and it is handled in accordance with Google's Privacy Policy", and that "Android Developer Verification does not collect information about the app content or functionality". The FAQ does not say that your legal name or address will be displayed to users. It also does not say that it will not be.

What Google Play already publishes, which is documented. This is where the concern is real, and it predates the verification programme. From Google's page on the information required to create a Play Console developer account, for a personal account:

Google will display your legal name, your country (as per your legal address), and developer email address on Google Play. If you decide to monetize on Google Play then Google will display your full address.

And the sentence after it:

In certain regions, developers are required to provide additional information which may be displayed on Google Play, like their phone number or full address.

For an organisation account:

To help improve transparency and user safety on Google Play, Google will display your legal name, legal address, developer email address, and developer phone number on Google Play.

So for a solo developer who charges for an app or sells anything in it, a full address goes on a public store listing. For most solo developers that address is where they live. Your legal name and address are taken from the Google Payments profile linked to the account, so there is no separate field to soften.

The mitigation that exists: your developer name, the one users see as the publisher, can differ from your legal name and can be changed at any time. The mitigation that does not exist: there is no supported way to publish a monetised app on Play without a displayed address. Some developers use a registered company address, an accountant's address or a virtual office for exactly this reason, and that is a legitimate and common answer. Whether a given service satisfies the requirements of your jurisdiction is a question for whoever registers your company, not for a store help page.

What the verification programme changes is reach. Publishing pseudonymously on Play was already difficult. From 2027, on Google's stated plan, an unverified identity means your app does not install on a certified device even if you never touch a store. That is the substance of the objection, and it is a fair one to raise without exaggerating what is currently documented.

What to do this month

  1. Open your Play Console Home page and look for unregistered apps. This is the 30 September item with the words "global removal" attached to it. Do it first, it takes a minute.
  2. Check which account type you need. If you sell anything, or distribute to more than 20 devices, that is a full distribution account with ID verification. If you genuinely do not, the limited account is free.
  3. If you need a D-U-N-S number, start now. Up to 30 days, per Google, and there is no expedited path you can rely on.
  4. If you ship an APK from your own website, register that package too. Google's page says explicitly that you can, and from 2027 the plan is that unregistered packages will not install on certified devices anywhere.
  5. Decide your address now, not at signup. If you are about to monetise for the first time and you work from home, sort the address out before the payments profile is created, because that is where the displayed value comes from.
  6. If you ship to Brazil, Indonesia, Singapore or Thailand, treat 30 September as hard. Everyone else has until the 2027 expansion, and no specific date for it has been published.

AppSubmit surfaces the store-side account and registration state alongside the release, because the failure mode this creates is an app that looks perfectly healthy right up to the moment it stops installing. Every check above is one you can do yourself in Play Console today, and if you only do one, do the Home page.

Sources

Last reviewed 2026-08-17. Apple and Google change their rules without notice, so check anything decision-critical against their live documentation.