Privacy Policy Builder

Answer a few questions and get a draft privacy policy.

Your business

Where most of your visitors or customers are.

Data you collect

Cookieless analytics, such as OpenRevenue, measure visits without storing anything on the visitor’s device.

Meta Pixel, Google Ads tags, LinkedIn Insight and similar.

Videos, maps or social posts loaded from other services.

Sharing and retention
0/1000

One per line or comma-separated, e.g. your help desk or CRM.

Under 13 in the US, or under 16 in much of the EU.

Your draft policy

A starting draft, not legal advice. Check that it matches what your site really does, and have it reviewed by a qualified professional before you publish it.

Privacy Policy for [Business name]

Effective date: [Effective date]

About this policy

[Business name] ("we", "us" or "our") runs the website [Website address] (the "site"). This policy describes the personal information we handle when you visit the site or use our services, what we do with it, who we share it with, and the choices you have.

For the purposes of the EU and UK General Data Protection Regulation (GDPR), [Business name] is the controller of the personal data described here.

Information we collect

Depending on how you use the site, we collect:

  • Technical data sent by your browser when you load a page, such as your IP address, browser type, device type, the page requested and the time of the request. Our hosting provider records this in server logs.
  • What you send us through a contact or enquiry form: usually your name, email address and your message.
  • Usage statistics, such as pages viewed, referring websites, approximate location (country or city) and device type, measured without cookies and reported to us in aggregate.

We do not ask for sensitive information, such as health data or political or religious views. Please do not send it to us.

How we use your information

  • To run, secure and fix the site, and to prevent abuse.
  • To answer your questions and messages.
  • To understand how the site is used and improve it.
  • To comply with legal obligations and to establish or defend legal claims.

Legal bases for processing (EU and UK)

Under the GDPR we rely on these legal bases:

  • Legitimate interests: to keep the site secure and working, to reply to messages you send us and to measure site use without identifying you. You can object to processing based on legitimate interests.
  • Legal obligation: where a law requires us to keep or disclose information.

Cookies

We do not use cookies or similar technologies to track you. If that changes, we will update this policy first.

Analytics

We measure visits with privacy-focused analytics that do not use cookies and do not follow you across other websites. We see totals, such as the number of visitors and the most popular pages, not profiles of individual people.

Who we share information with

We share personal information only with service providers that help us run the site and our business, and only as far as they need it. They may only use it on our instructions. These include:

  • Hosting and infrastructure providers that run the site.
  • Analytics.

We may also disclose information if the law requires it, to protect our rights or the safety of others, or as part of a merger or sale of our business. We do not sell your personal information.

International transfers

Some of our service providers may process data outside the EU or UK. When that happens we rely on an adequacy decision or on safeguards such as the European Commission's Standard Contractual Clauses (and the UK addendum). Contact us for more information about these safeguards.

How long we keep information

We keep personal information only as long as we need it for the purposes above.

  • Server logs are kept for a short period for security and then deleted.

Security

We use reasonable technical and organisational measures to protect personal information, such as encrypted connections and limited access. No system is completely secure, so we cannot guarantee absolute security.

Your choices

You can ask us what personal information we hold about you, and ask us to correct or delete it, by emailing [Contact email]. We may need to confirm your identity before acting on a request.

Your rights in the EU and UK

If the GDPR applies to you, you have the right to:

  • Access the personal data we hold about you and get a copy.
  • Have inaccurate data corrected.
  • Have your data deleted in certain circumstances.
  • Restrict or object to our processing, including for direct marketing.
  • Receive your data in a portable format.
  • Withdraw consent at any time where we rely on consent.

You also have the right to complain to a data protection authority, for example the authority where you live or work. We would appreciate the chance to address your concern first.

Children

The site is not intended for children under 16, and we do not knowingly collect their personal information. If you believe a child has given us personal information, contact us and we will delete it.

Changes to this policy

We may update this policy when our practices or the law change. We will post the new version on this page with a new effective date, and tell you directly about significant changes where appropriate.

Contact us

Questions about this policy or your personal information? Email [Contact email], or write to [Business name].

What a privacy policy should cover

A privacy policy tells visitors what personal information you collect, why, who else receives it, how long you keep it and what rights they have. Regulators read it as a promise: if the policy says you do not use tracking cookies, your site must not set them.

That is why this builder only adds sections for what you switch on. A policy that lists every possible practice is less accurate, and an inaccurate policy is a risk of its own.

Before you publish

  • Check the policy against what the site actually loads: forms, scripts, pixels and embeds.
  • List every service provider that receives personal data, including hosting, email and support tools.
  • Make sure the contact address is monitored, so you can answer requests on time.
  • Link the policy from every page, usually in the footer, and from forms that collect data.
  • Have it reviewed by a lawyer or privacy professional, especially if you handle payments, health data or children’s data.

Collect less, write less

The simplest privacy policy belongs to a site that collects little. Cookieless analytics such as OpenRevenue measure visits, sources and conversions without storing anything on the visitor’s device, which removes a whole category of disclosures and consent prompts.

Frequently asked questions

Is this privacy policy legally binding or compliant?

It is a starting draft, not legal advice. It covers the topics privacy laws usually expect, based on your answers, but only you know exactly what your site does with data. Check every section and have a qualified professional review it before you rely on it.

Does my website need a privacy policy?

Almost certainly. Laws such as the GDPR and California’s CCPA require one when you collect personal information, and even a contact form or server logs count. App stores, ad networks and payment providers also ask for one.

Is my information sent anywhere?

No. The policy is assembled in your browser from fixed templates. Nothing you type is sent to a server or to an AI model.

What changes if I use cookieless analytics?

Cookieless analytics do not store identifiers on the visitor’s device, so the policy can say you do not use tracking cookies, and in many cases you do not need a cookie banner for analytics. You still describe the analytics in the policy.

How often should I update my privacy policy?

Whenever you add a new way of collecting data or a new service provider, such as a chat widget, an ad pixel or a new payment provider, and at least once a year. Change the effective date when you do.

Related tools

All tools