On this page (9 sections)
Do not create a replacement account
Google associates accounts by identity, payment details, devices, code, assets and other signals. New accounts created to bypass a termination are typically terminated in turn, and they strengthen the case that the original termination was correct. If you also run other Google Play accounts (company, client, personal), assume they are being looked at.
What termination means
- All apps removed from Google Play and publishing disabled for the account.
- The developer agreement is terminated for that account; the notice usually cites the Developer Distribution Agreement and one or more Developer Program Policies.
- Associated accounts can be terminated as well; the notice often says so explicitly.
- An appeal path exists, described in Play Console Help under account terminations. It is the only legitimate route back.
The appeal window
At the time of verification, Google’s Help documentation for account terminations describes a limited period after the termination notice within which an appeal can be submitted. The exact window stated in your notice is the one that applies. The calculator below is purely arithmetical: it adds a number of days to a date you provide.
Read the notice for four things
- The cited policy or agreement clause. “Prior violations”, “malicious behaviour”, “deceptive behaviour”, “association with a terminated account” and “repeated violations” each need a different response.
- The termination date and any stated appeal deadline.
- Whether association is mentioned. If the notice says your account is linked to another terminated account, your appeal must address that link directly.
- Whether specific apps are named. The history of those apps (warnings, removals, suspensions) is the enforcement timeline you need to reconstruct.
Reconstruct the enforcement timeline
Terminations for “prior violations” rest on a history. Build a dated list of every rejection, warning, removal and suspension across all apps in the account, what each cited, and what you did in response. This is the backbone of an honest appeal and it tells you whether the decision is likely to be reversed at all.
Gather evidence
- Ownership and identity documents matching the account details
- Proof that flagged issues were fixed (build numbers, diffs, screenshots) where they were
- Licences, authorisations or rights for content, brands or regulated categories
- For association cases: a factual explanation of any relationship with the other account, or evidence there is none
- Nothing fabricated. A single false document ends the appeal and any future one.
Appeal readiness
Submit one complete appeal through the official form rather than several partial ones. State plainly what happened, take responsibility where it is warranted, describe concrete changes, and attach the evidence. Keep it short. Do not argue that the policy is unfair; argue that the decision is mistaken or that the issue is fully resolved.
Account association cases
These are the hardest. If your account was terminated because Google links it to a previously terminated account — a former client, a contractor, an agency you worked with, shared code or assets — the appeal must explain the relationship truthfully and show why your account should be treated independently. Denial is rarely persuasive when the link is technical (shared signing keys, identical code, same payment profile).
Technical fixes alone may not reverse a termination
Fixing the app that caused the last violation is necessary but often not sufficient. Termination is a judgement about the account’s conduct over time. Be realistic about the likelihood of reinstatement, and do not pay anyone who guarantees it — including us. We do not.
What to send us
- The termination notice, exactly as written.
- The enforcement history for every app in the account.
- Any prior appeals and Google’s replies.
- A factual description of any other Google Play accounts you are connected to.
Do not include passwords, signing keys, keystores, API secrets, recovery codes, payment credentials or personal data belonging to your users. We do not need any of these to review a rejection and we will ask you to remove them if they are included.