Privacy policy

Privacy policy generator

Tell us what your site collects and which tools you use. Termsquill writes a privacy policy from those answers and shows you which answer caused each paragraph.

Hand-painted illustration: a paper-document character holding a green umbrella over a small cottage on a floating island.

Free template page. Updated 20 November 2026.

What a privacy policy is for

A privacy policy tells people what personal information you collect, what you do with it and who you share it with. Many laws, app stores, ad networks and payment providers expect one wherever you collect even a contact form email.

Who needs one

Almost every site that has a contact form, newsletter sign-up, account, analytics tool, shop or embedded service needs one. If your site collects nothing at all and sets no cookies, you may not, but that is rarer than people think.

What your privacy policy covers

Who you areYour name or business, a contact route and, where the law needs it, a representative.
What you collectDetails people give you, details collected automatically and details that come from other sources.
Why and on what basisThe purposes of each use and, for EU and UK visitors, the legal basis.
Who receives itTypes of service providers, such as email, payment and hosting, and when data is shared.
How long you keep itA retention period or the rule you use to decide one.
Rights and how to use themAccess, correction, deletion and opt-out rights, and how to ask.

What the wizard asks you

These are the kinds of questions. Each one explains why we ask it, and you can skip what does not apply.

  1. Question 1What does your site do, and where are your visitors?
  2. Question 2Which details do you collect, and from whom?
  3. Question 3Which outside tools handle that data (email, analytics, payments, chat)?
  4. Question 4Do you use cookies or similar technologies?
  5. Question 5How can people contact you about their data?

A sample clause

Your real text is built from your answers. This is an example of the plain style we aim for, with the parts you fill in shown in brackets.

Sample: contact form data
When you send us a message through our contact form, we collect your name, your email address and the text of your message. We use them only to reply to you and to keep a record of our conversation. We keep messages for [12] months, then delete them. Our form is provided by [form provider], who handles the data for us.

Sample text for illustration. Your page is written from your own answers.

Mistakes we see most

  • Copying another company's policy. It describes their tools, not yours, and can promise things you do not do.
  • Listing tools you stopped using, or missing ones you added. Review the policy whenever your tools change.
  • Saying you never share data while using an analytics or email service. Those are sharing, and the policy should say so.

Questions

Do I need a privacy policy if I only have a contact form?
In most places, yes. A contact form collects personal data, and many laws require you to say what you do with it. Payment providers and ad platforms often ask for the link too.
Does Termsquill make my site GDPR or CCPA compliant?
No tool can promise that. Termsquill writes the privacy text those laws expect you to publish. Compliance also depends on what you actually do with data. We never say a page is compliant.
Can I use one policy for several sites?
Only if the sites collect the same data with the same tools. Otherwise each site should have its own, and the wizard lets you start from a copy.
How often should I update it?
Whenever you add or remove a tool, start collecting something new or change a retention period. Plus plans get an update inbox that tells you when our template changes.
Hand-painted illustration: a paper-document character at a round wooden door holding up a brass key.

Be first through the door.

Join the waitlist. One email when the free plan opens, and nothing else.