AppReviewFix
Guideline library
Google Play — Technical Compliance

Account Integrity — Developer account integrity

Official source: Google Play Developer Program PoliciesTopic overview: The review process, app quality and enforcement
What this guideline means

This covers requirements around the developer account itself — accurate identity/business information, no use of multiple accounts to spread risk or evade enforcement, and no creating a new account after a previous one was terminated for policy violations.

Why apps actually get flagged

Most commonly triggered when a developer whose account was suspended creates a new account (sometimes with different identity details) to keep publishing, which Google's account-linking signals frequently detect.

A real example

"This developer account was created to circumvent a prior enforcement action taken against another Google Play Developer account, per the Play Console account integrity requirements."

The short version, in more detail

Google Play's account-integrity requirements are about the developer behind the apps, not only the apps themselves. Identity and business details must be accurate, developers should not spread risk by running many accounts, and a developer whose account was terminated should not return under a new one. Google uses a range of signals to connect accounts, so evasion attempts are often detected.

Why this rule exists

Enforcement only works if a violation has consequences that stick. If a banned developer could register again under another name, policies would have little effect and users would meet the same harmful apps repeatedly. Accurate identity details also give Google and users a way to hold a publisher accountable. The rules therefore treat the account as an entity with a history that follows it.

What this guideline covers

  • Accurate identity and contact information on the developer account.
  • Use of multiple accounts and their relationships.
  • Return of developers whose accounts were terminated.
  • Verification steps for personal and organisation accounts.

What usually triggers this rejection

  • Creating a new account after a termination to keep publishing.
  • Using different identity details to avoid being linked to an old account.
  • Operating several accounts to spread out policy risk.
  • Providing inaccurate or unverifiable business information.
  • Sharing or transferring accounts in ways that hide the real publisher.

How reviewers evaluate it

  • Google combines account data, devices, payment details and behaviour to find links between accounts.
  • Verification checks compare submitted identity documents with the account details.
  • Linked accounts can be affected together.
  • Enforcement can take place well after a new account is opened.

Common misunderstandings

  • A new email address does not make a new identity in Google's systems.
  • Having several accounts is not automatically banned, but using them to evade enforcement is.
  • Identity details need to be accurate even if the app itself is simple.

Common questions

Can I have more than one developer account?

There can be legitimate reasons, but accounts used to avoid enforcement are prohibited.

Why are accounts verified?

Verification helps ensure the publisher is a real, accountable person or business.

What happens when linked accounts are found?

Actions on one account can extend to accounts connected to it.

Platform rules change often. This page is a plain-language explanation written by AppReviewFix, not official guidance. Check the current Google Play Developer Policy Center for the exact wording.

Got this exact rejection?Paste it in and get a diagnosis specific to your app, free.
Decode my rejection
Related guidelines
1.5 — Developer informationStrikes System — Policy strikes and enforcement escalationApp Promotion — App promotion and incentivized installsRatings & Reviews — User ratings, reviews, and installsMisrepresentation — Store listing and ratings misrepresentation
AppReviewFix
ProductDecoderPricingGuideline library
CompanyAboutFAQContact
ResourcesGuidesTopic overviewsCommon rejection reasons
LegalTermsPrivacy
© 2026 AppReviewFixBuilt by a developer, not a committee.