Short answer. Most Chrome extension rejections cite permissions not justified by the extension's function, missing privacy disclosures, obfuscated or remotely hosted code, or a listing that does not match what the extension does. Remove unneeded permissions, complete the privacy fields, ship readable code and resubmit.
Need help applying this to your notice? Request a free written assessment: Chrome Web Store case assessment. We reply within one business day. Paid preparation is quoted separately; the platform decides the outcome.
Permissions
Request only what the main feature needs. Broad host permissions such as all URLs need a clear reason; optional permissions requested at runtime are often better.
User data
Complete the privacy practices tab, link a privacy policy and use data only for the stated single purpose.
Code rules
Minification is allowed; obfuscation is not. Code must be included in the package rather than loaded remotely, with Manifest V3 rules applied.
Listing accuracy
Description, screenshots and name must match the actual function. Keyword stuffing is a common rejection reason.
FAQs
How do I appeal a Chrome Web Store decision?
Through the developer dashboard's appeal option, after making the required changes.
Can repeated rejections suspend my account?
Yes, repeated or serious violations can affect the developer account.
Do I need a privacy policy if I collect no data?
Complete the disclosures accurately. A policy is required when user data is handled.
Official sources