Free privacy policy generator for GDPR and CCPA.
Tick what your site collects (contact form, newsletter, purchases, Google Analytics, ad pixels) and get a complete privacy policy with legal bases, cookies, data sharing and user rights under GDPR and CCPA. Copy it as HTML or text. Free, no sign-up.
Template generated automatically from your answers. It is not a substitute for legal advice: review it before publishing and update it when your site changes.
How to create a website privacy policy
- Fill in your company details. Legal name, site name, registration number, website address and the email for privacy requests.
- Tick what the site collects. Be accurate: forms, newsletter, purchases, accounts, chat, Google Analytics and ad pixels.
- Say who you share data with. Hosting, payments, email marketing and CRM, and whether any service stores data in another country.
- Review and publish. Copy the HTML into a /privacy-policy page, link it in the footer and next to your forms, and have a lawyer review it.
Does every website need a privacy policy?
If your site collects any personal data (name, email, phone in a form, or analytics and advertising cookies), laws such as the EU GDPR and California’s CCPA require you to tell people clearly what you collect, why, who you share it with and how they can exercise their rights. Google Ads and Meta also require a privacy policy on sites that advertise and use their pixels.
What a GDPR-ready policy should include
Who the controller is and how to contact them, what data is processed, the purposes and legal bases (consent, contract, legal obligation or legitimate interests), sharing, international transfers, retention, security and user rights: access, rectification, erasure, restriction, portability, objection, withdrawing consent and complaining to a supervisory authority. For California residents, the CCPA adds the rights to know, delete, correct and opt out of the sale or sharing of personal information. The generator builds all of these sections.
Cookies, Google Analytics and ad pixels
Analytics and advertising tools store cookies and identifiers in the browser. Your policy must mention them and explain how to opt out. Ideally you also have a cookie banner that only turns on advertising cookies after consent. If your site uses the Meta Pixel or Google Ads conversions, tick the ad pixels option.
Privacy policy vs terms of service
The privacy policy explains how personal data is handled. The terms of service set the rules for using the site and buying from you. They are separate documents and most sites need both.
Frequently asked questions
Is the generated policy legally binding?
It is a complete template with the structure GDPR and CCPA expect, but it is not legal advice. Every business has its own details: review it before publishing.
Do I need a data protection officer (DPO)?
Under GDPR, only some organizations must appoint one (for example, public bodies or large-scale processing of sensitive data). If you do not need one, list a privacy contact email instead.
Where should I put the privacy policy?
On its own page, such as /privacy-policy, linked in the footer of every page and near your forms and checkout.
Does the CCPA apply to my business?
The CCPA applies to for-profit businesses that meet certain thresholds and handle personal information of California residents. Including the CCPA section does no harm if you are not covered.
Is the data I enter stored?
No. The policy is built in your browser and nothing is sent to One Analytic.