Privacy Policy Generator
Generate a privacy policy for your website or app covering the data you collect, cookies, analytics and user rights.
What the generated policy says on your behalf
The output has eight short sections: information collected, how it is used, cookies, third-party services, your rights, retention and security, changes, and contact. Your company name, website, contact email and effective date are filled in. The form also asks for a governing law, but the privacy policy text doesn't use it.
Several sentences are statements of fact about your site, and you must make sure each one is true before you publish:
- "We do not sell your personal data."
- That you collect names and emails directly, and IP address, browser type and pages visited through cookies and analytics.
- That you use analytics and advertising partners.
- That you keep data "only as long as necessary", which says nothing about how long that is.
If you run no ads, delete the advertising mention. If you sell products, the template says nothing about payment or delivery data, so you need to add it.
List your data before you edit the text
A privacy policy describes what you actually do, so start with an inventory, not the wording. One row for every place data enters your site:
| Data | Collected by | Who else handles it | Why | Kept for |
|---|---|---|---|---|
| Name, email, message | Contact form | Your email provider | To reply | [e.g. 12 months] |
| Email address | Newsletter sign-up | Newsletter service | To send the newsletter | Until unsubscribe |
| IP address, pages viewed | Analytics script | Analytics provider | Traffic statistics | [provider setting] |
| Name, address, order | Checkout | Payment processor, courier | To fulfil the order | [as your tax records require] |
| IP address, request log | Web server | Hosting company | Security, debugging | [host setting] |
Every row should appear somewhere in the finished policy. Plugins, embedded videos, chat widgets and form builders are the rows people most often forget.
Where the template is thinner than GDPR or CCPA expect
GDPR can apply to you even if you are outside the EU, when you offer goods or services to people who are in the EU or monitor their behaviour there. The test is where the person is, not their nationality. If it applies, the template is missing the legal basis for each use of data, actual retention periods, a list of who receives data, and any transfers outside the EU.
CCPA applies to a for-profit business doing business in California that meets any one of these: annual gross revenue over $26,625,000 (the adjusted figure in force from 1 January 2025), buying, selling or sharing personal information of 100,000 or more consumers or households, or earning 50% or more of revenue from selling or sharing personal information. Note the word "sharing". If your advertising partners use visitor data, ask a lawyer whether "We do not sell your personal data" is the full answer for you.
The generated policy is a template, not legal advice. Have a qualified lawyer review it if either law applies to you, or if you handle health, financial or children's data.
Sample: privacy policy for a small newsletter site
A compact policy organised around the inventory above, with retention periods and named recipients that the template leaves vague. Replace everything in [BRACKETS].
How to use this tool
- 1Fill in the fields in the form.
- 2Watch the document preview update live.
- 3Click Print / Save as PDF, or copy the text.
Frequently asked questions
Is the generated privacy policy GDPR compliant?+
No generator can promise that, because compliance depends on what your site really does with data, not on the wording. Use the text as a starting draft, correct it against your own data list, and have a lawyer review it if GDPR applies to you.
Do I need a separate cookie policy as well?+
The template has a short cookies section, which may be enough for a site with very few cookies. If you use several analytics or advertising tools, a separate cookie policy with a list of each cookie is clearer, and you may also need a consent banner.
How often should I update my privacy policy?+
Whenever you add or remove something that collects data: a new form, a newsletter service, an analytics tool, an ad network or a checkout. Change the effective date each time, and keep old versions so you can show what the policy said on a given date.
Where should I link to the privacy policy?+
In the site footer on every page, and next to every place people hand over data: sign-up forms, contact forms and checkout. In an app, put it in the settings menu and on the sign-up screen.
Guides & deep dives
Does Your Website Need a Privacy Policy? (GDPR, CCPA)
Find out if your website legally needs a privacy policy under GDPR, CCPA, and other laws — plus what to include, penalties for non-compliance, and how to get one fast.
NDAs Explained: Mutual vs One-Way and Key Clauses
Learn when to use a mutual vs one-way NDA, what confidentiality terms are standard, which carve-outs matter, and the red flags that make agreements unenforceable.
Embed this tool on your website
Free to use on blogs, school sites and intranets. Paste this code into your page's HTML; please keep the credit line.
<iframe src="https://utilityapp.lat/embed/legal/privacy-policy-generator" title="Privacy Policy Generator" width="100%" height="780" style="border:0;max-width:760px" loading="lazy"></iframe> <p style="font-size:13px"><a href="https://utilityapp.lat/legal/privacy-policy-generator">Privacy Policy Generator</a> by UtilityApp</p>