Privacy Policy Generator

What this page builds

The generator produces a complete privacy policy page in HTML. You provide the identifying details, choose which optional sections apply and press the generate button. The server inserts your values into a prepared template and returns the result; there is no language model and no AI drafting involved.

That distinction matters. The output is predictable and repeatable, but it is also generic. It gives you a structured starting point that covers the sections most websites are expected to publish, and it leaves the legal review, the data inventory and the jurisdiction-specific wording to you.

The form, field by field

• Last updated: the date shown at the top of the policy. Use the date you actually publish or revise it.
• Response time: a number from 1 to 365 and a unit of days, weeks or months. It is inserted into the rights section where the policy says how quickly you answer requests.
• Site name: the brand or company name that appears throughout the document.
• Site URL: the address the policy refers to. If you leave out the scheme, the generator adds https://.
• Contact info text: a short phrase such as "visit our contact us page" or an email address. It is inserted as text, not as a clickable link.
• Terms page URL: optional. If blank, the generator uses your site URL followed by /terms-and-condition.
• Cookies, ads and AdSense: three independent switches that add optional clauses and a partner table.

What the generated policy covers

The template includes a title block, a consent paragraph, an information-we-collect section, how the information is used, log files, CCPA rights, GDPR rights, children's information and a revisions clause. It also includes a third-party section when advertising is enabled.

The CCPA and GDPR sections are part of the base template, not optional switches. If your business does not fall under those laws, the clauses may still be harmless, but they can also promise rights you do not intend to honour. Read them and remove or adapt what does not apply.

What the cookies and ads switches change

Turning on cookies adds a Cookies and Web Beacons section that explains preference cookies and how visitors can manage them in the browser. Turning on general advertising adds a third-party advertising section and a partner table with a placeholder row you must replace.

Turning on Google AdSense adds the same advertising section but fills the table with a Google row and a link to Google's advertising technologies policy. If both ad switches are on, the AdSense row is the one that appears. If neither is on, the advertising section and table are omitted entirely.

What it cannot do for you

It does not know what data your site actually collects. A contact form, analytics script, payment processor, newsletter tool, chat widget or embedded video can each change the policy. List the tools you use before you publish, then add the missing categories and third-party names.

It does not select a jurisdiction, generate a cookie consent banner, create a data processing agreement, register you with a supervisory authority or check your compliance with the GDPR, CCPA, PIPEDA, LGPD or any other law. It also does not verify that the URLs you enter resolve. The output is a template, not legal advice, and a lawyer should review it for a business that handles sensitive data.

Contact details and response time

The contact field is plain text. If you want a mailto link, edit the generated HTML and add the anchor yourself. The response time is inserted where the policy describes how requests are handled; keep it realistic. Promising a reply within seven days and then taking a month is worse than stating a longer period you can meet.

The terms URL is only a link target. The generator does not fetch that page or confirm that a terms page exists.

Output, editing and publishing

After generation, the result appears in a preview tab and in an editor tab. The editor is a rich-text surface, so you can fix wording, add a company address, remove a clause or insert a link without writing HTML by hand. The copy button copies the current HTML, and the download button saves a file named privacy-policy.html.

Publish the page at a stable URL, link it in your footer and make sure the contact method in the policy actually works. If you change the policy later, update the last-updated date and keep a copy of the previous version for your records.

Step by step

1. Enter the last-updated date and the response time.
2. Fill in the site name, site URL and contact text.
3. Add the terms URL if you already have a terms page.
4. Enable cookies, advertising or AdSense only if they apply.
5. Press Generate Privacy Policy HTML.
6. Read the preview from top to bottom and edit the clauses that do not match your business.
7. Copy the HTML or download privacy-policy.html, then publish and link it.

Review checklist before publishing

Check the company name, the domain, the contact method and the date. Confirm that every data category in the policy matches a real form, script or integration. Confirm that the third-party table names your actual advertising partners. Check that the rights sections match the laws that apply to your visitors, and that the retention wording is something you can follow in practice. Finally, open the published page on a phone and make sure the table and headings are readable.

Limits and privacy

The form requires a date, site name, URL and contact text. The site name is capped at 120 characters, the URLs at 255 and the contact text at 255. The response time must be between 1 and 365. The generator does not create an account, store the policy or host it for you.

Your inputs are sent to the server so the template can be rendered and are returned in the response. The tool does not keep them after the request. Do not enter confidential information that is not already intended for a public policy page.

Frequently Asked Questions