Chrome extension removed and email account suspended after “suspicious bot activity” appeals, no resolution

[Lydia K]

Hi all,

I’m looking for guidance regarding a Chrome extension removal and email account suspension that I haven’t been able to resolve.

About a month ago, my email account that I used to publish the chrome extension was suspended for what was described as “suspicious bot activity and policy violations,” and my extension was subsequently taken down from the Chrome Web Store. I’ve submitted multiple appeals, but only received generic responses without details or actionable steps.

I also contacted Chrome Extension Developer Support. A support representative said they would relay my case to the appropriate team, but I haven’t received any follow-up, and the extension is now fully inaccessible.

The extension had ~70 active users across multiple countries (a small, legitimate niche community). I’ve temporarily made it available on Firefox and via manual Chrome installation, but this has been a significant barrier for non-technical users.

At this point, I’m unclear on:
• What specific activity triggered the suspension
• Whether this relates to user distribution, usage patterns, or something else
• Whether there is any remediation path
• Whether creating a new developer account or resubmitting would be safe, or likely auto-flagged

I want to comply fully with Chrome Web Store policies and am looking for clarity on how to proceed responsibly.

Any guidance from someone familiar with Chrome Web Store enforcement or account recovery would be appreciated.

Thank you!

[Toan Le Van]

Hi, I had a similar situation, but in my case it was related to the email account, not the extension itself.

I created a new email specifically to publish the extension. About 2 months later, that email was blocked for “suspicious activity,” and I lost access to my Chrome Web Store account. The extension itself was not taken down.

I resolved it by submitting an appeal and providing additional verification (like a phone number). After that, my email and developer account were restored.

So this might be more of an account trust/security issue rather than extension behavior. I’d recommend focusing on account recovery instead of creating a new developer account, since that could be auto-flagged.

Hope this helps.