Chrome extension privacy policy template

This page lists what the Chrome Web Store asks of a privacy policy and gives a free excerpt of template wording for an extension.

What the Chrome Web Store asks for

Source: Chrome Web Store User Data FAQ (Chrome Web Store program policies), read 2026-10-12 as a summary from a page-reading tool, not verbatim.

Post a privacy policy in the Developer Dashboard for products that handle user data, even if data is only stored locally.
Show a Limited Use disclosure on your homepage or one click away, describing compliance with the User Data Policy.
Show a prominent disclosure in the product interface before the user agrees. A privacy policy alone does not satisfy it.
Send user data over a secure connection (HTTPS or WSS) and store it with strong encryption.

Where a policy commonly falls short

Going only by the source above: having no policy posted when the product handles user data, putting the Limited Use disclosure nowhere a user can find it, relying on the policy instead of an in-product disclosure, and sending data over an insecure connection. The source does not list rejection statistics, and this page does not promise store approval.

Free excerpt from the template

Four complete clauses, copyable as plain text. Replace every [[FIELD]].

1. Data we collect

The extension handles the following data: [[DATA_COLLECTED_LIST]]

2. Browser permissions the extension requests

The extension requests these permissions and uses them only for the reason given: [[PERMISSIONS_AND_WHY]]

3. How we use the data

We use the data only for these purposes: [[PURPOSES_LIST]]

We do not sell your data. We do not use or transfer it for any purpose unrelated to the extension's single purpose described in its store listing.

4. Limited Use disclosure

The use of information received from Google APIs and from browser data by [[EXTENSION_NAME]] adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

- We do not use or transfer user data to serve ads, including retargeting or interest-based ads.
- We do not allow humans to read user data unless you give consent for specific items, it is needed for security or to follow the law, or the data is aggregated and anonymized.
- We do not transfer or sell user data to data brokers or information resellers.

Keep clause 4 only if your extension handles user data covered by that policy, and confirm its wording against the current official policy.

Fill-in checklist

List every data type the extension really reads, stores or sends, including data that stays local.
List every permission in your manifest and the single reason for each.
Match the policy to the single purpose in your store listing.
Name each third party that receives data, or write that there are none.
Add the in-product disclosure; the policy does not replace it.
Confirm all data in transit uses HTTPS or WSS.
Set a retention period and a deletion method you can actually carry out.

The full editable pack (7 templates in Markdown, PDF and HTML) is being prepared.