Legal & Compliance
Privacy Policy Generator (GDPR, UK GDPR & CCPA)
Create a privacy policy for your website or app — what you collect, why, who you share it with, cookies, retention, and the rights sections GDPR, UK GDPR and California (CCPA/CPRA) require. Download as Word or PDF.
For general information only — not legal advice. Laws vary by location; consult a qualified lawyer.
How to use
- 1Enter your business details and what data you collect.
- 2Tick the services you use (analytics, ads, payments, newsletters).
- 3Download the policy and publish it on your site, linked from every page footer.
Frequently asked questions
Is this privacy policy legally binding?
A document like this is binding when the parties agree to it (and sign where required). Whether each clause is enforceable depends on your local law, so have important agreements reviewed by a lawyer.
Do I need a privacy policy?
Almost certainly, if you collect any personal data (even an email address or analytics cookies). GDPR, UK GDPR, CCPA/CPRA, CalOPPA and app stores all require one.
What's the legal basis under GDPR?
Each purpose needs one: consent, contract, legal obligation, vital interests, public task or legitimate interests. The generator maps common purposes to typical bases — check they fit your case.
Is my information stored?
No. The document is generated in your browser and nothing you type is sent to our servers.
Why the sections change based on what you toggle on
The generator doesn't print one fixed template — it assembles sections conditionally, because a privacy policy that lists a legal basis for processing you don't actually do is itself misleading. Turning off 'Shows personalised ads' removes the advertising purpose and its consent basis entirely rather than leaving a placeholder; turning on GDPR adds a numbered legal-basis to every purpose and a California toggle appends the CCPA/CPRA rights section only when it's relevant to who's reading the policy.
Worked example: Privacy Policy Generator
Say a UK-based SaaS tool enters its company and site details, leaves GDPR on, CCPA on, but switches 'Shows personalised ads' off. The generated policy lists purposes with their legal basis — 'To send newsletters and offers you've asked for — legal basis: Consent', 'To understand how our site is used and improve it — legal basis: Consent for non-essential cookies / legitimate interests' — and the California section states plainly 'We do not sell or share personal information,' since the ads toggle controls that exact sentence. Switch ads on instead, and the same section changes to describe opting out via a 'Do Not Sell or Share' link or a Global Privacy Control signal.
What generating the document doesn't verify
The policy only describes what you tell it you do — ticking 'analytics' and 'payments' doesn't confirm your actual Google Analytics or Stripe configuration matches what's printed, and listing data types in the textarea is only accurate if you've actually audited what you collect. A privacy policy that doesn't match real practice is arguably worse than none, since it's evidence you represented something false. Treat this as a structured starting draft to fact-check against your actual data flows, not a finished compliance document.
The date, the child's age, and the retention line are filled in for you
The line under the title is the day you generate the policy, not a date you type. The children section uses the minimum-age box, which starts at 16 and stays between 0 and 21. The how-long-we-keep-it sentence uses the retention box, which starts as 2 years after the account closes. Financial records are always described as kept as long as tax law requires, and there is no box for that. Hosting and IT providers are listed as a recipient even when analytics, ads, payments, and marketing are all off. Turn GDPR off and later sections renumber: how long we keep data becomes section 6 instead of 7, and the rights paragraph shrinks to a short request to see, correct, or delete.
Related tools
- Cookie Policy Generator
Create a cookie policy listing the cookies your site uses — necessary, preferences, analytics and marketing — with how to manage consent, as required by the GDPR, UK PECR and the EU ePrivacy Directive.
- Right to Erasure Request Letter (GDPR Article 17)
Ask a company to delete your personal data under the right to erasure ('right to be forgotten') — Article 17 GDPR / UK GDPR, or a CCPA deletion request for California — citing the right grounds.
- GDPR Fine Calculator (Maximum Fines under Article 83)
Work out the maximum GDPR or UK GDPR fine for a company — €10 million / 2% or €20 million / 4% of worldwide annual turnover, whichever is higher — and see how regulators weigh the factors that set the actual amount.
- GDPR Compliance Checklist (Self-Assessment)
Check your business against the core GDPR / UK GDPR requirements — lawful basis, privacy notice, records, consent, rights handling, security, breaches, processors, transfers, DPIAs and DPO — and get a score with a prioritised to-do list.
- Cookie & Tracker Scanner (GDPR)
See which cookies a website sets, whether they're Secure/HttpOnly/SameSite, which trackers and ad pixels it loads, and whether a consent banner tool is installed.
- HTTP Security Headers Checker
Paste a site's HTTP response headers to grade its security headers — HSTS, CSP, X-Content-Type-Options, clickjacking protection, Referrer-Policy and Permissions-Policy.