A Google Play account terminated for "high risk behavior" means Google has closed your developer account, usually citing prior policy violations or an association with a previously terminated account. The most important thing to know is what not to do: creating a new account will not fix it, because any new account you open will also be terminated, with no refund, since evading enforcement is itself a violation. The only real path forward is to appeal through the official form in your enforcement email, calmly and with evidence.
Short answer
"High risk behavior" termination is Google closing your account, typically for prior violations, association with a terminated account, or a harmful app or SDK. Per Google's enforcement process, repeated or serious violations end individual and related accounts. Do not open a new account: Google states a new account will also be terminated without a refund. Instead, appeal through the official termination contact form, following the instructions in your enforcement email. If the cause is a false association or a violating third-party SDK, say so clearly and provide evidence. Submit one calm, factual appeal rather than several.
What "high risk behavior" termination means
Termination is the most severe enforcement action Google Play takes: your developer account is closed, all your apps are removed, and you can no longer publish. "High risk behavior" is the phrasing Google often uses when its systems judge an account to be linked to abuse or to a previously banned developer, rather than pointing at one specific app.
Because it is the top-level penalty, it also extends to related accounts. Google's policy is that a termination affects individual and related developer accounts, which is why the enforcement can feel broader than a single app or a single login. Understanding that it is an account-level action, not just an app rejection, is the starting point for responding to it correctly.
Why it happens: prior violations, association, or a bad SDK
There are a few distinct triggers behind a high-risk termination, and identifying yours shapes your appeal. The most common is prior violations, meaning an earlier app or account of yours breached the policies. Another is association: Google's systems linked your account to a previously terminated one through signals such as a shared device, network, payment method, or identity. A third is a genuinely harmful app, sometimes caused by a violating third-party SDK you included.
The table below maps the stated reason to a likely cause and your path.
| Stated reason | Likely cause | Your path |
|---|---|---|
| Prior violations | An earlier app or account breached policy | Appeal; resolve the original if it is yours |
| Associated with a terminated account | Shared device, network, payment, or identity | Appeal; give evidence of no association |
| High risk behavior | An automated risk flag on the account | Appeal; provide identity and context |
| Malware or harmful app | A violating app or third-party SDK | Appeal; identify and remove the SDK |
| Fraud or deceptive behavior | Manipulation, fake installs, misrepresentation | Appeal only if it is a genuine error |
The reason matters because the appeal differs. An association flag is answered with evidence that you are not the banned party; a harmful-app finding is answered by identifying and removing the offending component. Reading the enforcement email closely is how you tell which case you are in.
Was it a third-party SDK?
It can be. Some terminations trace not to anything you wrote, but to a third-party SDK bundled in your app that was flagged for malware, data collection, or policy violations. If a previously acceptable SDK later turns malicious or breaks a policy, apps that include it can be caught in the enforcement.
If you suspect an SDK, audit your dependencies for anything known to be flagged, and check whether the enforcement notice references app behavior rather than account association. Removing a bad SDK does not by itself reverse a termination, but it is essential context for an appeal and prevents the same trigger if you are reinstated. This is also where scanning your build before release pays off, by surfacing risky components early.
Can I just make a new account?
No, and this is the single most important point. Google explicitly states that if your account is terminated, any new account you register will also be terminated, without a refund of the registration fee. Opening a new account to get around a termination is circumventing enforcement, which is itself a violation, and Google's systems are specifically designed to detect it through the same association signals that may have flagged you in the first place.
The temptation is understandable, but it makes things worse, not better. A new account does not give you a clean slate; it usually gives you a second termination and a stronger association trail. If you believe the original decision was wrong, the sanctioned and far more effective response is to appeal, not to re-register.
How to appeal a termination
Appealing is the only legitimate path, and it starts in your enforcement email. That message names the reason and links to the appeal process, and Google also provides a dedicated form to contact it about an account termination, app removal, or suspension. Use the official channel rather than unofficial ones, because that is where the decision is actually reviewed.
The checklist below covers a clean appeal.
| Step | Action | Why |
|---|---|---|
| 1 | Read the enforcement email in full | It names the reason and the appeal link |
| 2 | Use the official termination appeal form | The only sanctioned channel |
| 3 | State your account and app details clearly | Lets Google locate your case |
| 4 | Explain calmly, with evidence | Facts beat frustration |
| 5 | Address association directly if it is cited | It is the common false-positive path |
| 6 | Submit once and wait | Duplicate appeals get closed |
Keep the whole thing factual and specific. The reviewers see a large volume of appeals, so a clear account identifier, a direct explanation, and concrete evidence do more than length or emotion. Submit a single appeal and wait, because duplicate submissions are typically closed without review.
What to put in your appeal
A strong appeal is short, factual, and targeted at the stated reason. Identify your account and the app clearly, state plainly that you are appealing the termination, and then address the specific cause. If it is association, explain your situation and provide evidence that you are not connected to the terminated account, such as your own identity and history. If it is an app or SDK issue, explain what the component was and that you have removed or will remove it.
Avoid two common mistakes. Do not argue in generalities about how much work you put in, because that does not speak to the policy question, and do not admit to or invent things that are not true. State what you know, provide what you can prove, and ask Google to re-examine the decision. Honesty and specificity are what give a false-positive appeal its best chance.
If you were associated with a previously terminated account
Association is the hardest case, and it needs a specific approach. Google's guidance is that if your account was terminated because it is linked to a previously terminated account, you first need to resolve that original termination by appealing it. In other words, the block is the old account, and clearing the old account is what can clear you.
If the associated account is genuinely not yours, for example you bought a used device, shared a network, or reused a payment method, say exactly that and provide what evidence you have. If the associated account is yours, resolving its violation is the prerequisite. Either way, pretending the association does not exist rarely works, because it is usually the specific thing the reviewer is looking at.
Realistic expectations and timelines
Be honest with yourself about the odds and the wait. Google does not publish a response time for termination appeals, and replies can take days to weeks. Some legitimate false-positive terminations are reversed on appeal, but many appeals are denied, especially where a real violation occurred. A calm, well-evidenced appeal improves your chances; it does not guarantee reinstatement.
Plan for both outcomes. While you wait, avoid actions that worsen your standing, above all opening new accounts. If the appeal succeeds, you will want your app clean and your dependencies vetted so the same trigger does not recur. If it fails, you will at least have a clear, documented record of what happened.
Prevent it next time: scan and vet before you ship
Not every termination is preventable, but the app-content and SDK triggers are the ones you can reduce. Vetting your third-party SDKs, removing anything unmaintained or flagged, and checking your build for embedded secrets, insecure configurations, and suspicious behavior all lower the chance that your own app is what draws enforcement.
A scanner like PTKD.com analyzes your .apk and returns findings ordered by severity and mapped to OWASP MASVS, so you can catch risky components and security issues before they ship. To be clear about the boundary: PTKD cannot reverse a termination, judge Google's account-association signals, or file your appeal. What it does is reduce the app-based risk that leads to enforcement, which is the part of this problem you actually control.
What to take away
- A high-risk-behavior termination closes your account, usually for prior violations, association with a terminated account, or a harmful app or SDK.
- Do not open a new account: Google terminates new accounts too, with no refund, and it worsens your standing.
- Appeal through the official form linked in your enforcement email, once, calmly, and with evidence.
- If you were flagged for association, resolve or disprove the original terminated account rather than ignoring it.
- Vet SDKs and scan each build with PTKD.com to reduce the app-based risk you can actually control.
