Do I need a privacy policy for my Chrome extension?

You need one whenever the extension handles user data, and the Chrome Web Store asks for the policy URL in the Privacy practices tab. Handling covers collection, use, storage and transfer, so local-only handling can still require disclosure.

Does this generator upload my answers?

No. The policy text is built in the page from what you tick, and nothing is sent anywhere.

Is the generated policy enough on its own?

It is a starting draft. What reviewers compare is whether the policy, the dashboard declaration and the code all say the same thing. Your jurisdiction or your users may require more, and this is not legal advice.

What if my extension stores data only on the device?

Say so explicitly. Local storage still gets described, and stating it plainly avoids a contradiction between a listing that claims nothing leaves the browser and code that sends something.

Chrome Extension Privacy Policy Generator

Extension name

Developer or company

Contact email

The one thing the extension does

Which categories does the code touch? Tick only what the code actually does — the declaration in the dashboard has to match this.

Where does it go?

Stored on the device only Sent to our own server Sent to a payment provider Sent to an analytics vendor

Third parties (comma separated, optional)

Retention

How to use it

Three things to do with the output

Host it at a public URL and put that URL in the dashboard. A policy behind a login or returning 404 is treated as missing.
Declare the same categories in the Privacy practices tab. The mismatch between policy, declaration and code is what gets flagged — not the wording of the policy itself.
Update it in the same release as any change to what the code handles. A policy that lags behind the code is the version you will be held to.

This generator produces a starting draft based on what you ticked. It is not legal advice, and your jurisdiction or your users may require more. Related: what reviewers check in privacy and Data Use · manifest pre-check.

The rest of the submission

The Chrome Web Store Submission Kit covers what this generator does not: permission justification lines, a Data Use worksheet that maps code paths to declared categories, listing copy rules, and a rejection decoder. 6-page PDF, one-time $19. It is ours — we wrote it and we are paid when you buy it. Everything on this site stays free either way.

Get the kit — $19

Not sure what to change?

Paste your manifest.json or the rejection email and we will tell you which parts are likely drawing scrutiny and what we would change. Free, no signup. It is our reading, not a ruling from Google.

Send it for a free triage The triage form is different from the tool above: what you paste there is sent to us.

Prefer to work through it yourself? The Chrome Web Store Submission Kit collects the permission justification lines, the Data Use worksheet, a privacy policy template and a rejection decoder into one document — one-time $19. It is ours; we are paid when you buy it. Everything on this site stays free either way.

Get the kit — $19