Website basics · 17 Nov 2026 · 6 min read
Website privacy policy, terms and cookie notice: what each is for
These three legal pages answer different questions. This guide explains each in general terms, where to link them and when to get professional advice.
The short answer
A website privacy policy explains what personal data you collect and how it is used. Terms and conditions set the rules of using the site or buying from you. A cookie notice explains which trackers the site sets and what choices visitors have. Rules differ by country and change, so ask a qualified lawyer.
Three pages, three different jobs
A website privacy policy, a terms and conditions page and a cookie notice are often lumped together as "the legal pages". They answer different questions for different readers, and mixing them up leads to pages that say too little or the wrong thing.
| Page | Main question it answers | Mainly protects |
|---|---|---|
| Privacy policy | What personal data do you collect, why, and what happens to it? | The visitor's information, and your honesty about it |
| Terms and conditions | What are the rules of using this site or buying from you? | The relationship between you and the user |
| Cookie notice | What small files or trackers does the site use, and what can I choose? | The visitor's choice over tracking |
This guide explains what each is for, in general terms. It is not legal advice. Rules differ by country, they change, and the right wording depends on your business, so a qualified lawyer should check the final pages.
What a website privacy policy covers
A privacy policy describes how your business handles personal information gathered through the site. Personal information is anything that identifies a person, such as a name, an email address or an online identifier. The policy is a statement of fact about your practice, so it has to match what the site actually does.
In general terms, a useful policy says:
- who you are and how to contact you about privacy;
- what information you collect, and where it comes from, such as forms, accounts, orders and analytics;
- why you collect each kind, and what you do with it;
- who else receives it, such as payment, email or hosting providers;
- how long you keep it and how it is protected;
- what rights the visitor has and how to use them, which depends on the country.
The most common failure is a policy that no longer matches the site. A new analytics tool, a new email service or a new form changes what you collect. Review the policy whenever the site changes. It helps to keep a list of every form and tool that touches personal data. Our guide to getting more form submissions is a reminder that every added form is also a new data source to describe.
Do not copy another company's policy and change the name. It will describe their practices, not yours, and may promise things you cannot do.
What terms and conditions are for
Terms and conditions set the rules of use. For a brochure site that only displays information, they are short: who owns the content, what visitors may do with it, and a note about the limits of what the site says. For a site that sells, takes bookings or lets users post content, they do much more work.
Typical topics are the order and payment process, delivery or service timing, cancellations and refunds, intellectual property, user conduct, limits on responsibility and how disputes are handled. Each of these varies a great deal by country and by type of business, and consumer protection rules in many places limit what terms can say. Do not assume that a clause is enforceable because it appears on a page.
For work done by a developer or agency for you, terms of use for the public site are separate from the agreement between you and the supplier. If you are commissioning a site, our guide to the website development contract covers what to agree in that relationship.
Terms should be written in plain language that a customer can follow. If a customer cannot understand it, it is less useful to everyone, including you.
Cookie notices and consent
A cookie notice explains what small files and similar technologies the site stores on a visitor's device, and why. Some are needed for the site to work, such as keeping a basket. Others measure visits or support advertising. Many countries have rules on telling people about the second group and on asking for permission before using them. The rules differ, and they are updated, so take advice for the places where your visitors live.
In practice, a good approach has three steps. First, find out what your site actually sets, because plugins and embedded content add more than people expect. Second, describe each type honestly in the notice. Third, if consent is needed, set up a banner that does not load non-essential trackers until the visitor agrees, and that makes refusing as easy as accepting.
The notice should be reachable at any time, and not just on first visit, so that people can change their choice. Check the current documentation of any consent tool or analytics service you use, since they change their settings and wording.
Where should legal pages be linked?
Put links to all three in the footer of every page. People look there first, and so do automated checks by payment providers and advertising platforms. Use plain link text: "Privacy policy", "Terms and conditions", "Cookie notice".
Add direct links at the moments they matter:
- Next to any form that collects personal data, with a short line saying what the data is used for.
- At checkout or booking, beside the button, for terms and refund rules.
- In the cookie banner, linking to the full notice.
- In account sign-up screens and in the confirmation emails you send.
Make each page easy to read and printable. Give each its own address so it can be linked and cited. A "last updated" date at the top tells visitors whether the page is current.
If you later move the site or change addresses, keep the legal pages reachable; redirect the old addresses to the new ones, as described in the guide to redirect planning for a redesign or domain move.
Keeping the pages accurate
Assign an owner, someone who is responsible for checking the pages. Review them when you add a tool, change a supplier, open a new market or change how you take payment. Record the date and keep older versions, because you may need to show what was published at a given time.
Security is part of the privacy story. A policy that says data is protected means little if the site is neglected, so see our website security checklist for small business. And if the site goes down or data may be affected, you need a plan; the steps are in what to do when your website goes offline. Some countries require you to tell people or regulators if personal data is lost. Ask a qualified lawyer what applies to you.
When should I ask a lawyer?
Ask before launch if the site sells to consumers, takes payments, collects sensitive information such as health details, serves children, or targets customers in several countries. Ask again when you change what you do with data. Ask if you receive a complaint or a formal request from a person or a regulator.
Free templates and generators can be a starting point for a draft, but they do not know your business. Use them to prepare questions, not to replace advice. A short consultation with a lawyer who handles website and data matters is often enough to review pages you have written yourself.
A web team can handle the website side: placing the pages, linking them correctly, setting up forms and consent banners and keeping them working. Our website development service page describes that kind of work. The legal wording itself, and what the law requires in your country, should come from a lawyer.
Related guides
- Website development
- Website forms how to get more submissions
- Website development contract what to agree
- Website security checklist for small business
- What to Do When Your Website Goes Offline
- Website Redirect Planning for a Redesign or Domain Move
Questions and answers
What is the difference between a privacy policy and terms?
A privacy policy explains what personal data you collect and how it is used. Terms and conditions set the rules for using the site or buying from you. They answer different questions and are usually separate pages.
Where should legal pages be linked?
Link all of them in the footer of every page. Also link privacy information beside forms, terms beside checkout or booking buttons, and the cookie notice from the consent banner. Give each page its own address and a last updated date.
When should I ask a lawyer about my website legal pages?
Before launch if you sell to consumers, take payments, collect sensitive data, serve children or sell across countries, and again whenever your data practices change. Rules differ by country and change, so a qualified lawyer should review final wording.
Can I use a template or generator for my privacy policy?
A template can give you a draft structure, but it does not know what your site collects. Make sure the final text matches your real practice, and have a qualified lawyer review it if your business handles personal data in any serious way.
Do I need a cookie notice if I only use analytics?
It depends on the country and on the tool. Many places have rules for analytics cookies and similar trackers. Check what your site sets, describe it honestly, and ask a lawyer or the official regulator about consent where your visitors live.
How often should I update my legal pages?
Review them whenever you add a tool, change a supplier or form, enter a new market or change how you take payment. Put a last updated date on each page and keep older versions.
Tell us what you are building.
A short call, a written plan and a fixed quote. No obligation.