Getting your Chrome extension approved: what reviewers look for
Privacy, permissions, and policy requirements that help your extension pass the Web Store review faster.
Chrome Web Store review can feel like a black box, but most rejections come from a few recurring issues: unclear or excessive permissions, missing or vague privacy practices, and policy violations. Addressing these up front greatly improves your chances of a smooth, fast approval.
Permissions: ask only for what you need
Request the minimum set of permissions and optional_host_permissions where possible. In the store listing and in-product, explain why each permission is used. Avoid broad host patterns (e.g. <all_urls>) unless you truly need them; narrow patterns reduce user concern and reviewer questions. If you need sensitive permissions (e.g. identity, storage, or host access), add a short note in the single-purpose description so reviewers see the justification immediately.
Privacy and data handling
Your privacy policy must be linked from the store listing and (if you collect data) from the extension. Clearly state what data you collect, how it’s used, and whether it’s shared or sold. If you don’t collect personal data, say so explicitly. Implement and describe data deletion options if users can create accounts or store data with you. Reviewers often check that the policy matches the extension’s behavior.
- Link the same privacy policy URL in the store and in the extension.
- Describe data collection, use, and sharing in plain language.
- Offer a way for users to request deletion of their data.
Single purpose and store listing
Extensions must have a single, clear purpose. The short description and store listing should focus on that purpose; avoid bundling unrelated features. Screenshots and the detailed description should reflect the actual experience. Misleading or placeholder content can trigger rejection. Before submitting, run through the program policies and developer documentation one more time—small fixes upfront save long review cycles.
More from the blog
View all posts