Developer

Chrome Web Store Privacy Requirements: Privacy Policy, Data Disclosures and Limited Use

What the Chrome Web Store requires for user data in late 2026: the Privacy practices tab, privacy policies, Limited Use, prominent disclosure and July's changes.

Privacy is one of the most common reasons Chrome Web Store submissions get rejected or taken down, and the rules got stricter in 2026. The good news is that the requirements are concrete. If you know what data your extension touches, you can fill in the forms correctly in about half an hour.

This guide summarizes the Chrome Web Store’s privacy requirements as of November 2026, with links to the official policy pages. It’s a practical overview, not legal advice. Your extension also has to follow the privacy laws that apply to you and your users.

What counts as “user data”?

Google’s definition is broad. The dashboard asks about these categories:

  • Personally identifiable information: name, address, email, age, ID numbers.
  • Health information and financial and payment information.
  • Authentication information: passwords, credentials, PINs, security questions.
  • Personal communications: emails, texts, chat messages.
  • Location: region, IP address, GPS coordinates.
  • Web history: the list of pages visited, with titles and times.
  • User activity: clicks, mouse position, scrolling, keystrokes.
  • Website content: text, images, sounds, videos or links on pages.

Notice the last three. An extension that sends page text to an AI service handles website content. A “productivity tracker” that logs visited domains handles web history. Many developers who think they collect “nothing” actually do.

The key question is whether data leaves the user’s device or is otherwise collected by you or a third party. Processing that happens entirely locally, like counting words on a page, generally isn’t collection, but describe it accurately anyway.

The July 2026 policy update

On July 1, 2026, Google announced policy changes, enforced from August 1, 2026:

  • Limited Use: user data must be strictly necessary for the extension’s disclosed single purpose. Collecting it for anything else is prohibited.
  • Disclosure: all data collection must be prominently disclosed to the user, even when it’s closely related to the single purpose. If your data practices change after installation, you must tell users proactively.
  • AI guardrails: extensions built to get around safety measures or usage restrictions of AI services are now explicitly prohibited.
  • Prediction markets: extensions enabling real-money transactions on predictive outcomes are prohibited.

Requirement 1: the Privacy practices tab

Every item has a Privacy practices tab in the Developer Dashboard (docs). It contains:

  1. Single purpose description. One narrow, clear purpose. “Shows reading time for articles” is good. “Productivity suite” isn’t.
  2. Permission justifications. A sentence for each permission and host permission, explaining what feature uses it.
  3. Remote code declaration. MV3 doesn’t allow remotely hosted code; you must state that you don’t use it.
  4. Data usage. Checkboxes for each data category you collect, plus certifications that you don’t sell data, don’t use it for unrelated purposes, and don’t use it for creditworthiness or lending.
  5. Privacy policy URL, if you handle user data.

These disclosures appear on your listing. Reviewers compare them with your code and network traffic. If the form says “no data collected” but the extension calls an analytics endpoint, expect a rejection, often under the violation code “Purple Lithium” for user data policy issues.

Requirement 2: a real privacy policy

If your extension handles any user data, the privacy policy requirement applies. Your policy, together with any in-product disclosures, must explain:

  • What data the extension collects.
  • How it’s used.
  • Who it’s shared with: every party, including processors such as an AI API provider or an analytics service.

Practical tips:

  • Host it on a stable public URL you control, not a Google Doc that needs a login.
  • Write it for this extension, not for your company in general. Generic website policies that don’t mention the extension are a frequent rejection reason.
  • Include retention and deletion: how long you keep data and how users can delete it.
  • Keep it in sync. Update the policy before shipping a version that collects something new.

Requirement 3: the Limited Use statement

The Limited Use policy restricts what you can do with collected data:

  • Use it only to provide or improve the single purpose.
  • Transfer it only when necessary for that purpose, for legal compliance, for security, or in a merger or acquisition (with prior consent).
  • Never use or transfer it for personalized advertising, and never sell it to data brokers.
  • Don’t let humans read it, except with the user’s consent for specific data, for security, for legal reasons, or in aggregated and anonymized form for internal operations.

You also need an affirmative statement on your extension’s website, for example in the privacy policy. Google’s suggested wording is: “The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.” Adapt it to your extension.

The User Data FAQ explains that a privacy policy alone isn’t always enough. When data collection isn’t obvious from the extension’s interface, you need an in-product disclosure, shown before collection starts, that:

  • Is displayed inside the extension’s UI, not only in the store listing or a policy.
  • Says plainly what data is collected and how it’s used.
  • Asks for affirmative consent: a click on “Agree” or similar, not consent assumed from continued use.

A first-run page from runtime.onInstalled is the usual place for this.

A worked example

Imagine an extension that summarizes the current page with a cloud AI API.

Item What to declare
Single purpose “Summarizes the current web page when you click the toolbar button.”
Permissions activeTab (read the page only when clicked), storage (save settings)
Data categories Website content (page text sent for summarizing)
Third parties The AI API provider, named in the privacy policy, with a link to its terms
In-product disclosure First-run screen: “When you click Summarize, the page text is sent to [provider] to create the summary. Nothing is sent otherwise.” Plus Agree button
Retention “We don’t store page text. [Provider] retention: see their policy.”

Using on-device AI instead, such as Chrome’s built-in Summarizer API, can remove the cloud transfer entirely. See Chrome’s built-in AI APIs.

Checklist before you submit

  1. List every network request your extension makes (DevTools → Network on the service worker and pages).
  2. Map each one to a data category and a feature.
  3. Remove anything not strictly necessary, such as unused analytics.
  4. Fill in the Privacy practices tab to match.
  5. Publish an extension-specific privacy policy with a Limited Use statement.
  6. Add a first-run disclosure and consent if collection isn’t obvious.
  7. Re-check all of this whenever you add a feature.

For the rest of the submission process, see publishing to the Chrome Web Store, and for how users evaluate this information, how to check if a Chrome extension is safe.

Keep reading