# Why Your Extension is Rejected in the Chrome Web Store in 2026 (and How to Avoid It)

> Real reasons for rejection in the Chrome Web Store following the August 2026 policies: permissions, written justification, installation notices, and privacy.

- **Source (source):** https://aitoolsforapps.com/chrome-extensions-manifest-v3-listing-dimensions-privacy-239/blog/why-your-extension-is-rejected-chrome-web-store-2026
- **Platform (platform):** AiToolsForApps
- **Language (language):** en
- **Updated (updated):** 2026-11-20

## In summary

- On **July 1, 2026**, Google published four changes to the Developer Program Policies of the Chrome Web Store and put them **into effect on August 1, 2026**: strict Limited Use, prominent disclosure of all data collection, prohibition of extensions that bypass AI service guardrails, and outside of real money predictive markets ([Chrome for Developers](https://developer.chrome.com/blog/cws-policy-updates-2026)).
- The changes **apply to the entire catalog**, not just to new submissions: a listing that you haven't touched since June can still be flagged.
- The number one reason for rejection remains the same as always: **excessive permissions**, accounting for about a third of rejections, with **one in five first submissions** rejected according to the review process analysis from [CWS Kit](https://cwskit.khanakia.com/blog/chrome-web-store-review-process-2026).
- The human reviewer checks three things: that the extension **does what the listing says**, that **each permission is justified by a visible function**, and that the **data processing matches the privacy statement**.
- You need a privacy policy **even if everything is processed locally**: what Google requires is an accessible and specific statement, and "I don’t collect anything" is a claim that needs to be written out, not omitted.

---

If you received an email with a strange color code —*Purple Potassium*, *Yellow Magnesium*— and the phrase "your extension does not comply with the program policies", you are not alone: the Chrome Web Store has tightened both the letter of its policies and the depth of manual review in 2026. This article breaks down the real reasons for rejection, permission by permission, and tells you exactly what to write in the justification and in the privacy policy. If you also want to tackle that part with automated help, **aiChrome**, the app from **AiToolsForApps** with [AI tools for Chrome extensions](/chrome-extensions-manifest-v3-listing-dimensions-privacy-239), is designed just for those who create, sell, or compete in the Chrome Web Store.

![Glass browser window under an inspection magnifying glass, with internal modules highlighted in amber](https://cdn.aistohire.com/i/7183-jige-whqz-iqze-qojh.webp)

## Why is your extension rejected in the Chrome Web Store in 2026?

Because the reviewer does not evaluate your intention, they evaluate the **consistency between three documents**: the manifest, the store listing, and the privacy statement. Most rejections are not due to malicious code, but rather due to a declared permission that no visible function uses, a description that promises more than what the uploaded build does, or a generic privacy policy copied from another product. Since **August 1, 2026**, there is a fourth piece that must fit: the data you collect must be *strictly necessary* for the unique purpose you declared.

Context helps to understand the severity. The catalog had **178,299 active extensions in March 2026**, a **22.70% increase** from a year earlier, and only in the first quarter of 2026 did **38,015** enter and **7,890** exit ([Chrome Web Store statistics 2026](https://konabayev.com/blog/chrome-extension-statistics-2026/)). With that volume, the review cannot be generous: it filters by mechanical signals and the first signal is the `permissions` block.

## What changed exactly on August 1, 2026

Google published the changes on **July 1, 2026** and started applying them on **August 1, 2026**. There are four, and three of them touch on data. The official notice itself warns that non-compliant extensions may face *enforcement* measures, including removal from the store.

| Policy Affected | What it says now | Who it practically affects |
|---|---|---|
| **Limited Use** | "Any user data collected by an extension must now be strictly necessary to the extension's disclosed single purpose" | Any extension that collects something "just in case": browsing analytics, broad telemetry, complete histories |
| **Disclosure Requirements** | All data collection must be prominently disclosed, **even if it is closely related to the single purpose**; and there must be proactive notification of subsequent changes in processing | Anyone who changes the backend or adds a provider without notifying already installed users |
| **Malicious and Prohibited Products** | Extensions designed to "circumvent safety guardrails, usage restrictions, or other protective measures implemented by AI-powered services" are prohibited | Chatbot jailbreaks, bypassing usage limits or quotas of AI services, automations that circumvent protections |
| **Regulated Goods and Services** | Predictive markets are prohibited: "Extensions that facilitate or enable real money transactions on predictive outcomes are not allowed" | Betting on outcomes with real money, including *prediction markets* |

Source: [Chrome Web Store policy update](https://developer.chrome.com/blog/cws-policy-updates-2026), July 1, 2026. The specialized press covered it as a tightening of privacy standards with a deadline of August 1, both in [Android Authority](https://www.androidauthority.com/chrome-web-store-extension-stricter-rules-3684115/) and [CyberInsider](https://cyberinsider.com/google-chrome-extensions-must-meet-new-privacy-standards-by-august-1/).

Two nuances that are often overlooked:

1. **"Prominent" does not mean "in the privacy policy"**. The disclosure must be seen by the user in the usage flow, not buried in a legal URL. The violation code covering this in the official catalog is *Purple Nickel*, "insufficient user consent for data collection".
2. **Subsequent changes also count**. If in version 1.0 everything was local and in 1.4 you send selected text to an API, that is a change in processing that must be disclosed proactively. It is not enough to silently update the policy.

## Written justification for permissions has been mandatory since June 2026

According to the regulatory change count from [CWS Kit](https://cwskit.khanakia.com/blog/chrome-web-store-policy-changes-2026), since **June 1, 2026**, any extension that requests *host permissions*, `storage`, or `identity` must present a **written justification** during review, and these justifications are read by a person, not an automatic system: an insufficient justification means rejection. It is advisable to take it as what it is —the count of a third party, not the official text— but it aligns with what Google's own documentation requests in the panel: explain why you need each permission.

The typical mistake is not writing anything, but writing a tautology. "I need `storage` to store data" does not justify anything. The justification that passes has three parts: **what user function**, **what specific data**, and **why it cannot be done with less**.

| Permission | Justification that often fails | Justification that works |
|---|---|---|
| `storage` | "To store user data" | "Stores the three preferences of the options panel (language, size, and theme) in `chrome.storage.sync`. No page content or identifiers are stored." |
| `identity` | "To log in" | "Obtains the user's OAuth token to read their own document list in the *Import* button. No scope other than reading that list is requested." |
| *host permissions* | "To work on any website" | "Injects the sidebar only on `https://docs.example.com/*`, the only site where the summary function makes sense; other domains are requested on the fly with `chrome.permissions.request()`." |
| `tabs` | "To manage tabs" | "Reads the title and URL of the active tab when the *Save bookmark* button is pressed. No history is traversed or background tabs are listed." |
| `scripting` | "To inject scripts" | "Injects `highlight.js` into the active tab when the user clicks the icon, with `activeTab` as the scope." |

## The three points that the human reviewer checks

The human reviewer installs the extension, uses it, and checks three things: **if it does what the listing says**, **if each permission is justified by a visible function**, and **if the data handling matches the privacy statement**. According to the breakdown of the [review process in 2026](https://cwskit.khanakia.com/blog/chrome-web-store-review-process-2026), the typical review takes between **1 and 3 days**, and extensions with sensitive permissions can exceed **ten days**.

![Three glass platforms representing the three points that the reviewer checks: actual function, permission linked to a visible function, and match with the privacy statement](https://cdn.aistohire.com/i/2460-wwtm-whfr-kicf-usqv.webp)

That same source places the rejection distribution as follows: **excessive permissions around one third**, followed by absent or inadequate privacy policy, misleading listings (*keyword stuffing*, false promises, undisclosed *upsells*), obfuscated code —minification is allowed— and extensions that simply do not work upon installation. It adds an uncomfortable fact: **approximately one in five first submissions is rejected**, although the rate drops significantly for publishers with a history.

The practical consequence is that the **visible function** is the king criterion. If your extension requests `history` but the user cannot find any screen where they see their history, that permission is not justified, no matter how much your code uses it internally. The rule to adopt: *one permission, one button*. If you cannot point to the screen where the user sees the effect of the permission, remove it or move it to `optional_permissions`.

## What literal warning will someone installing your extension see, permission by permission

Chrome translates each permission into a specific phrase in the installation dialog, and that phrase is what decides whether the user completes the installation or gets scared. Not all permissions show a warning: `storage`, `identity`, `scripting`, `notifications`, `alarms`, and `activeTab` do not generate any. These are the literal warnings according to the [permissions list of the extensions API](https://developer.chrome.com/docs/extensions/reference/permissions-list.md.txt):

| Permission | Literal warning on installation | Note |
|---|---|---|
| `tabs` | "Read your browsing history." | Suppressed if the extension already requests `<all_urls>` |
| `webNavigation` | "Read your browsing history." | Same warning as `tabs` |
| `history` | "Read and change your browsing history on all signed-in devices." | The most aggressive warning in the usual catalog |
| `bookmarks` | "Read and change your bookmarks." | — |
| `topSites` | "Read a list of your most frequently visited websites." | — |
| `downloads` | "Manage your downloads." | — |
| `geolocation` | "Detect your physical location." | — |
| `clipboardRead` | "Read data you copy and paste." | — |
| `clipboardWrite` | "Modify data you copy and paste." | — |
| `management` | "Manage your apps, extensions, and themes." | — |
| `nativeMessaging` | "Communicate with cooperating native applications." | — |
| `debugger` | "Access the page debugger backend." + "Read and change all your data on all websites." | Two warnings, one of them equivalent to full access |
| `declarativeNetRequest` | "Block content on any page." | — |
| `cookies` | No own warning | The warning comes from the associated host permissions |
| `storage`, `identity`, `scripting`, `notifications`, `alarms`, `activeTab` | No warning | `activeTab` is the silent way to act on the current tab |

Two useful readings. The first: `activeTab` is the most underestimated permission in the ecosystem, because it does 80% of what people ask for with *host permissions* **without generating any warning**. The second: when an extension accumulates several permissions with warnings, the user does not see one, they see a **list**, and the official documentation of [permission declarations](https://developer.chrome.com/docs/extensions/develop/concepts/declare-permissions) states this explicitly. Each extra line in that list is lost conversion.

## How to Trim Host Permissions from "all sites" to Specific Domains

Requesting `<all_urls>` in `host_permissions` is the request most likely to trigger a deep manual review, scare the user with the warning of "read and change all your data on all websites," and be blocked by company policy. The solution is not to give up on scope: it is **to declare the domains you actually use and move the rest to runtime**.

![Comparison between a wide funnel that absorbs dozens of sites and a narrow channel through which only three specific domains pass](https://cdn.aistohire.com/i/8324-lfqu-lxmk-ptuw-qden.webp)

The path, in four steps:

1. **Real inventory.** List the domains where your `content_script` does something observable. If there are five, there are five patterns, not `<all_urls>`.
2. **List specific patterns** in `host_permissions`, with a path when you can narrow it down: `https://www.example.com/app/*` is better than `https://*.example.com/*`.
3. **Move the wildcard to `optional_host_permissions`.** According to Chrome's documentation, optional permissions "are granted by the user at runtime, instead of at install time": the user adds a site when requested, with a dialog each time.
4. **Request on the fly with `chrome.permissions.request()`**, tied to a user gesture ("Activate on this site" button), not to the startup of the *service worker*.

```json
{
  "manifest_version": 3,
  "host_permissions": [
    "https://docs.example.com/*",
    "https://app.example.com/editor/*"
  ],
  "optional_host_permissions": ["<all_urls>"],
  "permissions": ["activeTab", "storage"]
}
```

This manifest installs **without the total access warning**, covers the two domains where the function exists, and leaves the door open to any other site under explicit consent. It is also the easiest configuration to justify in writing: the reviewer sees that you have narrowed it down and that the wildcard is opt-in.

> If your extension does need `<all_urls>` at installation — blockers, password managers, universal readers — the justification must explain **why it cannot work with narrower patterns**. It is not enough to state that it needs it: you must reason the technical impossibility.

## What Your Privacy Policy Should State Even if Everything is Processed Locally

That you do not collect anything, stated explicitly and verifiably, and why each declared permission does not imply collection. Processing locally **does not exempt you** from having a privacy policy accessible from the listing: the *Purple Lithium* violation code from Google's official catalog is precisely "lack of privacy policy disclosure," and a generic policy unrelated to the functionality of the extension counts as inadequate.

![Sealed glass dome over a laptop with data circulating in a closed loop inside, disconnected external servers, and a privacy policy document resting on the base](https://cdn.aistohire.com/i/1793-pndk-rubd-mhib-jayq.webp)

What a reviewer expects to find in a 100% local extension policy:

- **An unambiguous statement**: no user data is transmitted outside the device and there is no own server receiving anything.
- **What is stored and where**: "preferences are stored in `chrome.storage.local`, in the user's browser profile, and are deleted upon uninstalling the extension."  
- **Permission by permission, what it does not do**: if you request `tabs`, state that the URL of the active tab is read in memory and is neither persisted nor sent.
- **Absence of third parties**: no analytics, no SDKs, no CDNs that log requests. If there is a remote source — web fonts, a translation API — name it; silence there is what turns a correct policy into an inadequate one.
- **Remote code**: declare that all executable code travels in the package. Running code brought from outside is the *Blue Argon* violation from the official catalog.
- **How you will notify of a change**: the proactive disclosure policy as of August 2026 requires informing of subsequent changes, so write down the channel (release note, new features screen, email).
- **Contact and last updated date**, with the always-live URL: a broken link in the policy field is direct rejection.

And one operational detail: the policy you write must **match the data usage boxes** you check in the panel. Inconsistency between the two is one of the three crossing points for the reviewer.

## Google's rejection codes, translated

When Google rejects an extension, the email includes a code with a color name and chemical element. These are closed and public categories: identifying yours tells you exactly what to fix. These are the ones that most affect legitimate extensions, according to the [official compliance resolution guide](https://developer.chrome.com/docs/webstore/troubleshooting):

| Code | Meaning | Fix |
|---|---|---|
| **Purple Potassium** | Requested and unused permissions | Remove the permission or show the reviewer the function that uses it |
| **Purple Lithium** | Missing privacy policy | Live and specific link in the panel field |
| **Purple Nickel** | Insufficient consent to collect data | Prominent disclosure and affirmative consent *before* collecting |
| **Purple Magnesium** | Unnecessary data collection or dissemination | Do not log browsing activity unless a visible function requires it |
| **Purple Copper** | Insecure data transmission | HTTPS; do not put data in headers or in *query strings* |
| **Blue Argon** | Remote code | No external `<script>`s or `eval()`; everything inside the package |
| **Red Titanium** | Obfuscated code | Minify yes, obfuscate no |
| **Yellow Magnesium** | The extension does not work | Test the packaged ZIP, not just the unzipped folder |
| **Yellow Zinc** | Poor metadata (icon, title, screenshots) | Complete and descriptive assets |
| **Yellow Argon** | *Keyword stuffing* in the listing | No repeated words more than five times |
| **Red Magnesium** and family | Multiple unrelated purposes | One purpose per extension; split into two products |
| **Grey Copper** | Online gaming or predictive markets | Already explicitly banned since August 2026 |

## Checklist before hitting "Submit for review"

If you're just going to do a quick pass before submitting, do this. Each point corresponds to a real documented rejection reason above.

1. **Unique purpose in one sentence.** If you need an "and" to describe your extension, you probably have two products.
2. **One permission, one visible function.** Go through the manifest and point out the screen for each permission. What you can't point out, remove or move to `optional_permissions`.
3. **`activeTab` before `host_permissions`,** and specific patterns before `<all_urls>`.
4. **Written justification** for *host permissions*, `storage`, and `identity`: function + concrete data + why it can't be done with less.
5. **Listing = build.** Screenshots and description of the version you are uploading, not last year's or the roadmap's.
6. **Listing limits respected** and texts without keyword stuffing.
7. **Privacy policy** live, specific, consistent with data usage checkboxes, and explicit if everything is local.
8. **Prominent disclosure** in the usage flow for any collection, and a written plan to notify of future changes.
9. **Test the package.** Install the ZIP in a clean profile and check that it starts without console errors.
10. **No shortcuts to AI guardrails** or real money on results: that is no longer a rejection, it's a withdrawal.

It's worth remembering why it's worth the effort: the median for a Chrome Web Store extension is **18 users** and only **2.63%** exceed 10,000, with **14.10%** at zero users ([statistics 2026](https://konabayev.com/blog/chrome-extension-statistics-2026/)). The bottleneck is not the code, it's getting to the store well presented and staying in.

## Frequently Asked Questions

### How long does the review of an extension in the Chrome Web Store take in 2026?

Between **1 and 3 days** for most new submissions, according to the [analysis of the review process](https://cwskit.khanakia.com/blog/chrome-web-store-review-process-2026). Extensions with sensitive permissions may exceed **ten days**, as they move from the automatic phase —static analysis, manifest validation, asset and privacy policy checks— to a complete manual review.

### Do the new policies affect me if I haven't updated my extension since before August 2026?

Yes. The policies apply to all items in the store, not just new submissions, and the enforcement of the updated wording began on **August 1, 2026**. An intact listing from before that date may be flagged, and according to the official notice, non-compliant extensions are subject to removal.

### Do I need a privacy policy if my extension doesn't collect any data?

Yes, and it must be specific to your extension. The lack of privacy policy disclosure is a standalone rejection category (*Purple Lithium*) and a generic policy unrelated to functionality counts as inadequate. What changes when you don't collect anything is not the obligation, it's the content: you explicitly state that there is no transmission outside the device and explain, permission by permission, why.

### Can I request `<all_urls>` if my extension really needs it?

You can, but expect a deeper manual review and a more discouraging installation notice. The justification must explain why the extension **cannot function with narrower patterns**, not just claim that it needs it. It is advisable to declare specific domains in `host_permissions` and leave `<all_urls>` in `optional_host_permissions`, which the user grants at runtime.

### What permissions do not show any notice to the user upon installation?

According to the official list of permissions, `storage`, `identity`, `scripting`, `notifications`, `alarms`, and `activeTab` do not generate a notice; `cookies` also does not have its own notice. Additionally, the notice for `tabs` ("Read your browsing history.") is suppressed if the extension already requests `<all_urls>`, because that permission already covers a broader notice.

### Why was I rejected for "excessive permissions" if my code uses them?

Because the reviewer’s criterion is the **function visible to the user**, not the internal code usage. If the permission serves logic that the user never sees reflected on a screen, the reviewer reads it as unjustified. The solution is either to expose the function, remove the permission, or make it optional and request it when the user activates that function.

### What counts as "bypassing the guardrails" of an AI service?

The new policy prohibits extensions "designed to bypass security guardrails, usage restrictions, or other protective measures implemented by AI-powered services." In practice, it covers *jailbreaks* of chatbots, bypassing usage limits or quotas, and automations whose purpose is to evade the service's protections. Integrating with an AI API while respecting its terms does not fall under this prohibition.

### Do I have to notify my users if I change what I do with their data?

Yes, and proactively. That is exactly the second part of the change in disclosure requirements from July 2026: it is not enough to update the policy on the website; you must inform the user of the change in data handling. Write in your own policy through which channel you will do this.

## Where an AI tool fits into all this

The work you've just read —narrowing permissions, drafting a justification for each one, writing a privacy policy consistent with what the manifest declares, and preparing a listing that says exactly what the build does— is repetitive, and it is precisely what determines whether you pass the review on the first or third attempt. **aiChrome**, the app from **AiToolsForApps**, brings together [AI tools for those who create, sell, or compete in Chrome extensions](/chrome-extensions-manifest-v3-listing-dimensions-privacy-239) and is designed for that moment: the one just before hitting "Submit for review."

Policies will continue to evolve —2026 has brought changes on various dates— so the best practice is not to memorize the rule, but to leave your manifest and your listing in a defensible state: each permission with its function, each data point with its reason, and each claim in the listing verifiable in thirty seconds by someone who has never spoken to you.

> Prepare your next submission with aiChrome: narrow down permissions, draft justifications and the listing, and arrive at the Chrome Web Store review with everything coherent. Try it for free, no registration required.

- [Google Chrome — Listing assets, Manifest V3 and Chrome Web Store paperwork](https://aitoolsforapps.com/chrome-extensions-manifest-v3-listing-dimensions-privacy-239)

## About the platform

**Google Chrome — Listing assets, Manifest V3 and Chrome Web Store paperwork** — an app by AiToolsForApps. Available at: https://aitoolsforapps.com/chrome-extensions-manifest-v3-listing-dimensions-privacy-239/blog/why-your-extension-is-rejected-chrome-web-store-2026

### Other languages

- `es`: https://aitoolsforapps.com/es/extensiones-chrome-manifest-v3-medidas-ficha-privacidad-239/blog/por-que-rechazan-tu-extension-chrome-web-store-2026
- `fr`: https://aitoolsforapps.com/fr/extensions-chrome-manifest-v3-dimensions-fiche-confidentialite-239/blog/pourquoi-rejet-extension-chrome-web-store-2026
- `it`: https://aitoolsforapps.com/it/estensioni-chrome-manifest-v3-misure-scheda-privacy-239/blog/perche-la-tua-estensione-viene-rifiutata-chrome-web-store-2026
- `pt`: https://aitoolsforapps.com/pt/extensoes-chrome-manifest-v3-medidas-ficha-privacidade-239/blog/por-que-sua-extensao-e-rejeitada-chrome-web-store-2026
- `de`: https://aitoolsforapps.com/de/chrome-erweiterungen-manifest-v3-listing-masse-datenschutz-239/blog/warum-deine-erweiterung-im-chrome-web-store-2026-abgelehnt-wird
- `bg`: https://aitoolsforapps.com/bg/razshireniya-za-chrome-manifest-v3-razmeri-na-listinga-i-poveritelnost-239/blog/zashto-otharlyat-razshirenieto-ti-chrome-web-store-2026
- `ja`: https://aitoolsforapps.com/ja/chrome-extension-manifest-v3-store-assets-239/blog/chrome-web-store-kyakka-riyu-2026
- `nl`: https://aitoolsforapps.com/nl/chrome-extensies-manifest-v3-afmetingen-voor-de-vermelding-en-privacy-239/blog/waarom-chrome-web-store-extensie-afgewezen-2026
- `ko`: https://aitoolsforapps.com/ko/chrome-extension-manifest-v3-store-listing-239/blog/chrome-web-store-hwakjang-peurogeuraem-georbu-iyu-2026
- `sv`: https://aitoolsforapps.com/sv/chrome-tillagg-manifest-v3-sidans-matt-och-integritet-239/blog/varfor-avslas-ditt-tillagg-chrome-web-store-2026
- `da`: https://aitoolsforapps.com/da/chrome-udvidelser-manifest-v3-mal-til-oversigten-og-privatliv-239/blog/derfor-afvises-din-udvidelse-chrome-web-store-2026
- `zh`: https://aitoolsforapps.com/zh/chrome-extension-manifest-v3-store-assets-239/blog/chrome-web-store-extension-rejected-2026
- `pl`: https://aitoolsforapps.com/pl/rozszerzenia-chrome-manifest-v3-wymiary-wpisu-i-prywatnosc-239/blog/dlaczego-odrzucaja-twoje-rozszerzenie-chrome-web-store-2026
- `ar`: https://aitoolsforapps.com/ar/idafat-chrome-manifest-v3-wmqasat-albtaqa-walkhsusia-239/blog/rafd-idafat-chrome-web-store-2026
- `fi`: https://aitoolsforapps.com/fi/chrome-laajennukset-manifest-v3-listauksen-mitat-ja-tietosuoja-239/blog/miksi-laajennuksesi-hylataan-chrome-web-store-2026
- `cs`: https://aitoolsforapps.com/cs/rozsireni-pro-chrome-manifest-v3-rozmery-karty-a-soukromi-239/blog/proc-zamitaji-rozsireni-chrome-web-store-2026
- `no`: https://aitoolsforapps.com/no/chrome-utvidelser-manifest-v3-oppfoeringsmal-og-personvern-239/blog/hvorfor-avvises-chrome-utvidelsen-din-chrome-web-store-2026
- `id`: https://aitoolsforapps.com/id/ekstensi-chrome-manifest-v3-ukuran-listing-dan-privasi-239/blog/alasan-ekstensi-ditolak-chrome-web-store-2026
- `he`: https://aitoolsforapps.com/he/tospi-chrome-manifest-v3-midot-krtis-vprtiot-239/blog/why-chrome-web-store-rejects-your-extension-2026
