How to add a Privacy Policy URL for a Chrome Extension
By Paul Cranmer, Founder · Last verified August 2026 · Chrome Web Store · Extensions
You are ready to publish a Chrome extension, then the Web Store asks for a privacy policy URL. If your product handles user data, Google requires an accurate, up-to-date policy linked from the Developer Dashboard. This page shows where to paste the URL, what the policy must cover, and how our free Browser Extension path fits.
Who this is for
- Extension developers publishing or updating a Chrome Web Store listing
- Solo builders stuck on the Privacy policy field before review
- Teams aligning manifest permissions with plain-language disclosures
Not for
- Meta, Google Ads, or LinkedIn lead form campaigns (those use the paid hosted path)
- A full Chrome extension architecture course
What the platform requires
- Chrome Web Store Program Policies say if your product handles any user data, you must post an accurate, up-to-date privacy policy.
- The policy must disclose how you collect, use, and share user data, and which parties you share it with, alongside any in-product disclosures.
- You must make the policy accessible by providing a link in the designated Chrome Web Store Developer Dashboard field.
- Privacy practices disclosures in the dashboard should stay consistent with the privacy policy URL on your developer account.
Get a live URL first
Browser Extension is on our free path. Choose Browser extension in the wizard, get a live HTTPS privacy policy URL, and paste it into the Chrome Web Store. Ads, lead forms, and stores stay on the $9.99/yr hosted plan. Do not use this free extension link as a substitute when you are blocked on Meta or Google lead forms.
Get free extension URLStep-by-step: paste your privacy policy URL
- Open the Developer Dashboard. Go to the Chrome Web Store Developer Dashboard and sign in with the publisher account that owns the extension.
- Set the account Privacy policy URL. Open Account (publisher settings). Find the Privacy policy field, paste your live HTTPS URL, and click Save. Confirm it still shows after a refresh so the save stuck.
- Complete Privacy practices for the item. Open your extension item and fill Privacy practices / data use disclosures so they match what the policy page says and what your manifest permissions allow.
- Align permissions and policy text. If you request broad host or data permissions, the policy should explain what you access, why, retention, and how users can request deletion or contact you.
- Preview and submit. Preview the listing, open the policy link in a private window, then submit or update the package for review. If Google rejects the item, fix mismatches between permissions, Privacy practices, and the policy page before resubmitting.
Field labels to look for
- Privacy policy (Account)
- Publisher-level field in the Developer Dashboard Account section. Paste a public https:// page URL and Save.
- Privacy practices (item)
- Per-extension disclosures about data collection and limited use. Keep them consistent with the policy URL.
- Permissions / manifest
- Requested permissions must be explainable in the policy. Vague “we may collect data” language is a common review failure.
Common reasons the form fails
- Empty Privacy policy URL when the extension handles user data
- Dashboard field edited but not Saved
- Policy that never names the extension or explains permissions
- Privacy practices answers that contradict the policy page
- Broken link, login wall, or page that only works with heavy client scripts
- Using an ads/lead-form paid URL story when you only needed the free extension path, or the reverse
Free path vs ads path
This how-to is for Chrome extensions (free Browser Extension path). If you came here from a Facebook, Google Ads, or LinkedIn lead form blocker, use those how-tos and the $9.99/yr hosted plan instead. Homepage SEO stays on Privacy Policy URL for the general head term; this page is only the extension job.
FAQ
Do I need a privacy policy URL for a Chrome extension?
If your extension handles user data, Chrome Web Store policies require an accurate privacy policy linked from the designated Developer Dashboard field.
Where do I paste the Privacy policy URL?
In the Chrome Web Store Developer Dashboard, open Account and fill the Privacy policy field, then Save. Also complete Privacy practices on the extension item so disclosures match.
Is Privacy Policy URL free for Chrome extensions?
Yes. Browser Extension is on our free path. Ads, lead forms, and stores use $9.99/yr. Choose Browser extension in the wizard for the free link.
Do permissions need to match the policy?
Yes. If the manifest requests broad access, the policy should explain purpose, use, sharing, and contact or deletion paths in plain language.
Is telemetry allowed?
With disclosure. Describe what you collect, why, how it is shared, and how users can opt out or request deletion when applicable.
Can I use the same URL for Play and the Web Store?
Yes if the page names each product and covers their data practices. One stable HTTPS URL is easier to maintain than separate broken links.
What if review rejects the listing?
Compare Privacy practices, permissions, and the policy page. Fix contradictions, confirm the URL loads publicly, Save again, and resubmit the package.
I need a URL for Facebook lead ads. Is this the right page?
No. Use the Facebook Lead Ads how-to and the paid hosted plan. This page is only for Chrome extension listings.