Does my extension need a privacy policy if it collects nothing?

The Chrome Web Store rule is triggered when the extension handles any user data. Many extensions do (page content, browsing activity, email), so check your permissions honestly.

Is there a Chrome-extension-specific template?

No. PrivacyPage generates a general app policy; you describe your extension’s permissions and data in the wizard.

Chrome Web Store · Platform guide

Privacy policy for Chrome extensions

If a Chrome extension handles any user data, the Chrome Web Store requires an accurate, up-to-date privacy policy that discloses how data is collected, used and shared, and with whom. You link it in the developer dashboard, and your Privacy-tab data disclosures must be consistent with it.

§ 1

What Chrome Web Store requires

Program Policies — Privacy Policies

“If your Product handles any user data, then you must post an accurate and up to date privacy policy.”

Source: developer.chrome.com verified 2026-10-29

1.1Privacy tab disclosures must match the policy. In the dashboard’s Privacy tab you state a single purpose, justify each permission, and certify which data types you collect. Google notes the disclosures are shown to users and “should be consistent with the existing privacy policy URL that you provided”. Source: developer.chrome.com

1.2Limited Use. You certify that data use is limited to the extension’s disclosed purpose, under the Chrome Web Store Limited Use policy. Source: developer.chrome.com

§ 2

What common SDKs collect

SDK / API	Data it collects	Source
chrome.identity (getProfileUserInfo)	Email address of the signed-in Chrome profile (requires identity.email permission) Obfuscated Gaia ID	Source: developer.chrome.com

Everything in this table must appear in your policy if the SDK ships in your build.

§ 3

Where to put the URL

3.1Chrome Web Store developer dashboard → your item → Privacy tab → privacy policy link.
3.2Complete the single-purpose, permission justification and data-usage certifications on the same tab.

§ 4

Sample clause

§ 4.1 · Account email

If you choose to sign in, the extension reads the email address of your signed-in Chrome profile through Chrome’s identity API. We use it only to identify your account for sync, do not sell it, and do not use it for advertising.

Illustrative wording. Your generated policy is written from your own answers.

§ 5

Questions

Does my extension need a privacy policy if it collects nothing?: The Chrome Web Store rule is triggered when the extension handles any user data. Many extensions do (page content, browsing activity, email), so check your permissions honestly.
Is there a Chrome-extension-specific template?: No. PrivacyPage generates a general app policy; you describe your extension’s permissions and data in the wizard.