Chrome Web Store's data policy got a lot stricter on 1 August 2026 — here's what actually changed

Most "Chrome extension got rejected" threads still blame permissions. Since 1 August 2026, that's only half the story — Google has been enforcing a tightened Limited Use Policy, and it's the reason otherwise-finished extensions are getting flagged.

What changed, verbatim

From Google's own Chrome Web Store policy update (published 1 July 2026, enforcement began 1 August 2026):

"Any user data collected by an extension must now be strictly necessary to the extension's disclosed [single purpose]."

"...require that all data collection be prominently disclosed to the user — regardless of whether..."

"developers must proactively disclose to users if their data handling practices change."

Translation: it's no longer enough to have a privacy policy. The data your extension actually collects has to match the single purpose you declared, and if that changes later, you have to tell users — not just quietly update a policy page nobody reads.

Two other changes landed in the same update: predictive-market transaction extensions are now explicitly prohibited, and so are extensions built to bypass AI safety guardrails.

Why this matters more than it sounds

We build and publish Chrome extensions for clients, and the two things that trip people up now are:

1. Scope creep in permissions. An extension that started as "highlight text on this page" and grew a "sync your bookmarks" feature without updating its disclosed purpose is now a compliance problem, not just an over-broad-permissions warning.
2. Analytics bolted on after the fact. Adding a usage-tracking SDK later, without disclosing it as part of the purpose, is exactly the pattern the new policy targets.

If you're publishing a new extension, disclosure has to be written to match the code from day one. If you already have one live, that same disclosure now needs re-checking against what the code actually does — not what you meant it to do when you first shipped.

We do both at ZoopCoder (disclosed affiliation, honest pricing, no invented guarantees on Google's review outcome):

• Chrome Extension Development — ₹9,999, Manifest V3, built and submitted in 7-10 working days, scoped and disclosed against this policy from the start.
• Chrome Web Store Publishing — ₹999, for an extension you've already built: we check it against the current policy, write the permissions justification and privacy disclosure, and handle submission in 2-3 working days.

Neither service can promise Google approves anything — that call is Google's alone. What we can fix is the paperwork side, which is where most rejections actually happen now.

Source: developer.chrome.com/blog/cws-policy-updates-2026

Disclosure: I'm with ZoopCoder, a small dev shop in India. Sharing this because we hit real client extensions bouncing on this exact policy and couldn't find a plain-English writeup of it.