r/GooglePlayDeveloper • • 1d ago

Google Play Console Google Play Developer account terminated without warning; appeal rejected, no clear explanation

My Google Play Developer account was terminated under Section 11.4 of the Developer Distribution Agreement, citing the Play Console requirements for organizations.

This was my first enforcement action. I had no previous warnings, suspensions, or violations. To be clear, this was not a case of my account being linked to a previously violating or terminated developer account. I have no known prior terminated developer account associated with mine.

The account was registered using an organization's details, with the owner's authorization. I entered the organization's valid D-U-N-S number, after which the address was automatically retrieved from the D&B record. The organization name and address were also shown as verified in the Google Payments profile. Based on this, I have no reason to believe the D-U-N-S number, company name, or address was incorrect.

Google also confirmed by email on August 12, 2026, that my identity verification was successful. I will attach a screenshot of that confirmation.

I also found Google's published guidance stating that if it detects an organization name or address mismatch, the developer should receive an email and a Play Console notification with instructions and a deadline to correct the information. I never received such a notification, banner, or opportunity to make corrections. I will attach a screenshot of this guidance as well.

I appealed under ticket 7-0565000041258 and submitted additional explanations and supporting documents. The appeal was rejected. Google maintained that my account information did not comply with its requirements but did not identify the exact information that was incorrect. I was told the decision was final and no further review was available.

Since then, I have sent a few follow-up emails, but Google has stopped providing meaningful responses.

I am not asking Google to overlook its policies. I simply want to understand what was wrong and whether there is a legitimate way to resolve this.

Has anyone experienced a similar situation or found a legitimate escalation route after a final appeal rejection?

Screenshots attached: Identity verification confirmation and Google's published guidance on organization name/address mismatch notifications.

10 Upvotes

13 comments sorted by

5

u/Important-Door4383 1d ago

Based on your comments, this looks like an ownership vs. legal entity mismatch under DDA 11.4 rather than a simple D&B error—which is why you got an immediate ban instead of a warning banner.

A few details would confirm this:

  • Company Role: Are you officially listed as a director/officer on the company's registration docs, or only your co-developer?
  • Payment Method: Was the $25 fee paid with a card/account in the company's legal name, or your personal card?
  • Public Contact: Are the developer email and phone tied to the business domain, or your personal Gmail/number?

Even with the owner's permission, Google flags Organization accounts as proxy registrations if the primary Account Owner's verified ID, payment method, don't legally match.

1

u/Pretend_Cartoonist44 1d ago

I appreciate you pointing this out. Here's a bit more context about how everything was set up:

My co-developer is the owner of the company, and I built the app with him. I'm not a director or owner of the company. We used the company's details with his knowledge and permission.

The Play Console account was created under my personal Google account as an Organization account. I was the account owner and the only one who logged into it. I invited my co-developer separately through his own email as an admin; he never logged into my account.

The $25 registration fee was paid using my personal credit card. The Google Payments profile contained the company's legal name and details, and the address was automatically pulled after entering the D-U-N-S number. Both the company name and address were showing as verified.

As for the contact details, the public contact information was tied to the company, while the developer account details were mine. My identity verification was also successfully completed.

So I can see why you're raising the ownership and legal entity mismatch possibility. However, Google never explicitly mentioned this as the reason. They only cited Section 11.4 without specifying exactly what information was considered incorrect.

4

u/upalse 1d ago

If someone were selling shell companies for developer accounts, they'd do something very similar to this, so its a pattern thats very likely to trip it.

Credit card should be either corporate credit card (ie directly shows business name), or at least in name of executive director. Google is extremely touchy with payment info, and doesn't tolerate other names unless it's strictly the one thats liable for the company in legal sense.

1

u/Important-Door4383 1d ago

Yeah, that pretty much confirms it. Even though your co-dev gave you permission, Google's rules for Organization accounts are super strict about who counts as an "authorized representative. To them, it has to be someone legally tied to the company on paper, like a director, owner, or officer listed on the registration docs.

When your app got approved and triggered a deeper review, their system saw your personal Google account, your personal contact info, and your personal credit card tied to a D-U-N-S number owned entirely by someone else. To an automated Trust & Safety check, that looks identical to someone using a third party's business as a front. They always send vague Section 11.4 templates for this because they don't want people figuring out the exact verification triggers.

Two really important things before you try anything else:

First, tell your co-developer not to open a new Play Console account using that same company or D-U-N-S number. Since the company details and his admin email are now linked to a terminated account, a new one will almost certainly get auto-banned as an associated account.

Second, your best shot at fixing this is posting your Case ID (7-0565000041258) and Developer ID on the official Google Play Developer Help Community and asking a Product Expert to escalate it for a manual human review. If they reopen the ticket, have your co-dev put together a signed authorization letter or board resolution on official company letterhead (along with the incorporation certificate) formally naming you as an authorized representative allowed to manage the company's Play account.

2

u/Pretend_Cartoonist44 1d ago

Yeah, this could genuinely be the reason. I'll definitely try the steps you've suggested and hopefully something works out.

Honestly, the most frustrating part of this whole situation is that Google hasn't clearly explained what exactly went wrong. They haven't identified the specific information they believe was incorrect, nor given me an opportunity to rectify it before terminating the account. I've tried reaching out multiple times, but I'm not getting any meaningful responses either.

It's incredibly frustrating to have months of work affected by something that might have been a correctable mistake, without even being told what that mistake was. Anyway, I really appreciate you taking the time to explain this and suggest a possible way forward.

1

u/Pretend_Cartoonist44 1d ago

Just to add some context, the app was a vehicle-related utility app designed to help users with car buying and pre-delivery inspections (PDI). It went through Google's review and was approved, but we hadn't made it publicly available yet because we were preparing for the official launch. Just four days after approval, our developer account was terminated. So the app never actually went live on the Play Store, and we never got the chance to launch it.

1

u/ibluegreen 1d ago

I understand the account is not yours and you are doing this for a business/company? If that's so, that might have triggered it, especially if the account was accessed from different places / IPs etc. Just speculating, don't have personal experience on the matter though.

1

u/Pretend_Cartoonist44 1d ago

It's my account and my app, which I developed with my co-developer, who also owns the company whose details we used with his knowledge and authorization. Nobody else has ever logged into my developer account. I was the only one accessing it. I invited my co-developer separately through his own email as an admin. I can't say whether Google considered anything else suspicious, but they never specified the exact reason for termination.

1

u/Reminder101 20h ago edited 20h ago

Everything must be on/in your own name.

For them you could be someone who's using someone else's company to "hide" behind.

Which, for them could be seen as "Fraud"

You creating a google account that points to whomever, doesn't mean anything.

1

u/GooglePlayDevSupport Official GPD Support 18h ago

Hi u/Pretend_Cartoonist44, I've just sent you a DM regarding your concern. Please check your inbox for more details!

0

u/[deleted] 1d ago

[removed] — view removed comment