Cookie policy: what it must contain, how to write it and a ready-to-use outline

calendar_today September 13, 2026
Cookie policy: what it must contain, how to write it and a ready-to-use outline

The banner is the visible part, but the duty to inform users is fulfilled by the cookie policy: the document the banner must link to, describing in detail which cookies the site uses and why. Regulators call it the second layer of information, as opposed to the short first layer shown in the banner. Many sites have one copied from another site or generated years ago, listing cookies that no longer exist and ignoring those added since. A notice that does not match the actual cookies is not a notice, and in an inspection it is challenged together with the banner.

What the law says

The information to provide comes from Articles 12 and 13 of the GDPR, from Article 5(3) of the ePrivacy Directive as transposed in each country and from the guidelines of national authorities such as the Italian Garante, the French CNIL and the Spanish AEPD. The policy must be written in plain language, reachable from every page of the site and specific to that site. It must also explain how users can give, refuse and withdraw consent, and withdrawing must be as easy as consenting.

The eight sections of a complete cookie policy

This is the outline we use in Konsento to generate policies. You can follow it even if you write yours by hand.

  • Data controller: name, address, contact email and, if appointed, the contact details of the data protection officer.
  • What cookies and similar technologies are: a short explanation that also covers local storage, pixels and identifiers used by apps.
  • Strictly necessary cookies: the list of essential cookies, with name, purpose and duration, and a note that they do not require consent.
  • Cookies subject to consent, divided by category: functional, statistics, marketing. For each cookie the name, who sets it, purpose, duration and whether it is first or third party.
  • Third parties: for each provider, its name, the link to its privacy notice and, if it transfers data outside the European Union, the legal basis for the transfer.
  • How to manage consent: how to change it on the site, how to delete cookies in the most common browsers, what happens if you refuse.
  • User rights: access, rectification, erasure, restriction, objection, portability and the right to lodge a complaint with the supervisory authority, with instructions to exercise them.
  • Last update date: the policy must state when it was last modified.

The mistakes that make it useless

The first mistake is the generic policy: a text that mentions "possible third-party cookies" without saying which ones. The second is the policy frozen in time: the site added a pixel, a chat, an embedded video, and nobody updated the list. The third is the policy in one language on a multilingual site: the foreign user is not informed in an understandable way. The fourth is the missing link: the policy exists but the banner does not point to it, or the link is hidden at the bottom of a page that cannot be reached from the banner. The fifth, more subtle, is the missing duration: for each cookie you must state how long it stays in the browser, and "persistent" is not a duration.

Cookie policy and privacy policy are not the same thing

The privacy policy describes all the controller's processing: contact forms, the newsletter, orders, customer data. The cookie policy deals only with cookies and similar technologies. They can live in the same document, but it is clearer to keep them separate and link them to each other, with the banner pointing to the cookie policy and the footer pointing to both.

When to update it

The cookie policy must be updated every time the site's cookies change: a new plugin, a different theme, a campaign with a new pixel, the removal of a service. The easiest way not to forget is to run a periodic cookie scan and compare the result with the published list. If you added cookies subject to consent, the banner must be updated too, and the consent already collected may not cover the new cookies.

How Konsento handles it

Konsento generates the cookie policy from the cookies its scanner actually finds on your site: every recognised cookie is placed in the right category, with provider, purpose and duration. The policy is available in six languages, is updated after every scan you run and is linked to the banner automatically. Together with the privacy policy and the terms and conditions it is part of the one-time licence: 86 euros per domain, forever, no subscription. You can try everything free for 15 days: konsento.cloud/en/register.

arrow_back Torna alle News