Did Google Play change developer account rules around verification or required info?

Did Google Play change developer account rules around verification or required info

Yes. Google Play changed developer account onboarding and verification rules, and it now asks for more identity and contact information than it used to. For new accounts, Google links the developer profile to a Google payments profile, verifies identity details, and requires contact details that stay reachable for the life of the account.

The part people miss is that this is not only about whether you can create an account. Google also uses the verified information to decide whether you can publish or keep publishing. If Google cannot verify the legal name, legal address, or contact details, the developer presence and apps may be restricted or removed until the account is re-verified.

For personal accounts, Google now asks for developer name, legal name, legal address, contact email, contact phone number, and developer email address. Google says the legal name and address come from the linked Google payments profile, and the contact email, contact phone, and developer email must be verified with a one-time password and remain operational.

For organization accounts, Google asks for organization name, organization address, organization phone number, organization website, contact name, contact email, contact phone number, developer email address, and developer phone number. In practice, this means teams that used to treat signup as a light form now need to treat it as an identity record that must stay current.

The inconvenient part is public disclosure. Google says it will display some verified identity details on Google Play, and in certain regions it requires additional information that may also be shown publicly, such as a phone number or full address. Merchant accounts that monetize through paid apps or in-app purchases must show a full address on Google Play.

Google also added ongoing maintenance rules. If your legal name, address, organization details, or contact information changes, you are expected to update the developer account information and, when needed, the payments profile used for verification. Failing to keep the data accurate can affect account standing and app availability.

Another change people get wrong is confusing account verification with app testing rules. Google Play also introduced a separate requirement for newly created personal developer accounts after November 13, 2023, where a closed test must run with at least 12 opted-in testers for 14 continuous days before production access can be requested. That is a publishing gate, not the same thing as identity verification.

The test requirement has a sharp edge: if your tester count drops below 12 or the testers are not continuously opted in for the full 14 days, the clock does not help you. The review can send you back to more testing, which is why teams often keep a larger buffer of testers than the minimum before they try to publish.

The old mental model, where a developer could sign up, verify later, and publish with little upfront detail, no longer matches current Google Play onboarding for new accounts. Google says it introduced these requirements to improve trust, user safety, and transparency, and it now expects the account owner to keep the profile accurate over time.

If you are checking whether your own account is affected, the practical step is to open Play Console and review the account owner, legal name, legal address, contact details, and any public developer contact fields. If the account is new, or if your legal identity has changed, do that before you plan a release. That is faster than discovering a blocked production track after your closed test is already running.

For teams that also test on iOS, it helps to keep the rules separate. Apple TestFlight has its own tester limits and does not use Google Play’s 14-day closed test gate, so an iOS process does not satisfy a Google Play requirement. Mixing those two workflows is a common reason release plans slip.

If you want a simple rule to remember, use this: Google Play now asks for more verified identity and contact information up front, and it expects that information to stay current. For new personal accounts, publishing also has a separate closed-test requirement before production access.

If you are organizing testers for a Play launch, DevConnect can help with that part of the workflow, and the platform is free to use. The useful habit is to keep the identity and verification work separate from the tester recruitment work, because Google treats them as different checks. DevConnect is one place to handle the testing side without mixing it into account verification.

What changed in Google Play developer verification

Google expanded the data it asks for, added stronger verification steps, and made account information something you have to maintain, not just provide once. The important shift is that Google now ties the developer account to verified identity and reachable contact channels.

What information does Google Play now require

For personal accounts, the required set includes developer name, legal name, legal address, contact email, contact phone number, and developer email address. For organization accounts, the list expands to organization name, organization address, organization phone number, website, contact name, contact email, contact phone number, developer email address, and developer phone number.

What gets shown publicly on Google Play

Google says some verified details can be displayed on Google Play, including legal name, legal address or country depending on account type and region, and developer contact details. In certain regions, additional items such as phone number or full address may also appear.

What happens if the information is wrong or out of date

Google says inaccurate or unverifiable account information can lead to restrictions, app removal, or loss of publishing access until the information is corrected and re-verified. That is the part people regret ignoring, because it usually shows up when they are trying to ship.

Does this include the 12 tester rule

No. The 12 tester, 14 day closed test requirement is separate from verification of developer identity and contact information. It applies to newly created personal developer accounts after November 13, 2023, and it affects production access.

What should I check before I publish

Check whether your account type is personal or organization, confirm that your legal identity details match the linked payments profile, verify that your contact email and phone still work, and make sure your closed test has enough opted-in testers for long enough if your account is new. That sequence avoids the most common release failure points.