
Many sites have both pages, and many owners are not sure why. In short, one explains what you do with personal data in general and the other explains one particular tool, cookies, in more detail.
This guide helps you decide how to split the information and what each page should say.
The privacy policy
Covers all personal data: what you collect, why, who receives it, how long you keep it and people's rights.
The cookie policy
Zooms in on cookies and similar technologies: which you set, what each does, how long it lasts and how to control it.
Do you need both?
If you use analytics, ads or embeds, yes. A single page can cover both, but a separate cookie policy is easier to keep current.
Consent
In the EU and UK, a banner usually collects consent for non-essential cookies. The policy explains what people are agreeing to.
Link them
Each should link to the other.
A way to remember the difference
The privacy policy answers the question: what do you know about me, and what do you do with it? The cookie policy answers: what small files do you put on my device, and can I say no? They overlap, so each page should link to the other.
What a cookie policy lists
Each cookie or similar tool, its purpose, how long it lasts and who sets it. Group them as strictly necessary, preferences, analytics and advertising. Say how a visitor can change their choice.
Do small sites need both?
If you set only the cookies your site needs to work, a few sentences in your privacy policy may be enough. If you use analytics, ads, embedded videos or social buttons, a separate cookie page is easier to keep accurate.
Banners and choices
Where the law asks for consent, a banner has to let people say no as easily as yes, and the tools should stay off until they choose. Check the rules in the countries your visitors come from.
A quick checklist
- Both pages link to each other.
- The cookie list matches what your site really sets.
- Visitors can change their choice later.
- Tools stay off until consent where it is required.
