Cookie consent log: what it is, what it must contain and how long consent lasts
Article 7 of the GDPR is short and clear: where processing is based on consent, the controller must be able to demonstrate that the data subject has consented. For cookies this means that showing a correct banner is not enough. You need a record of every choice made by users, kept in a way that can be produced if a supervisory authority asks for it, if a user complains or in litigation. This is the consent log, and in our experience it is the part most often missing, especially in free banners and in those developed in-house.
Why the banner alone is not enough
A banner collects the choice and saves it in a cookie in the user's browser. That cookie serves not to show the banner again, but it is not evidence: it lives on the user's device, can be deleted at any time and the controller cannot consult it. If the authority asks you to prove that the visitor of 12 March accepted marketing cookies, you need an archive of your own, with the data of that choice. The burden of proof is on the controller, not on the user.
What the log must contain
For every consent collected the log should keep:
- A consent identifier, generated by the banner and also saved in the user's browser, to link the choice to whoever challenges it.
- The exact date and time of the choice.
- The type of action: accept all, reject all or custom choice.
- The categories accepted and refused: necessary, functional, statistics, marketing.
- The version of the banner and of the text shown, to prove what information the user saw.
- The version of the cookie policy in force at that moment.
- The language the banner was shown in and the page where the choice was made.
- Later withdrawals and changes, linked to the original consent.
You need a way to link the log to the individual user without identifying them more than necessary: a pseudonymous identifier saved in the choice cookie is enough.
What not to record
The log is itself a processing of personal data and must respect data minimisation. There is no need to keep the full IP address: if you want to keep track of it, truncate it or hash it. No need to record name and email, unless consent is given by a logged-in user. No need to keep the full browser string, the device type is enough. Every extra piece of data you keep is one more to protect and to justify.
How long to keep it
The log must be kept for the whole duration of the consent and for the time needed to defend against possible claims. The most common practice is to keep it at least for the validity period of the consent plus the limitation period, and most controllers choose between two and five years. The chosen period must be stated in the privacy policy.
How often to renew consent
The question always comes up: how long does cookie consent last? The Italian Garante's guidelines say that, if the user refused, the banner must not reappear for six months, unless the processing changes significantly or the user deletes the cookies. For consent given they set no expiry, but other European authorities do: the French CNIL recommends keeping the choice for six months, the Spanish AEPD sets twenty-four months as the maximum before asking again; in Germany there is no statutory term, but authorities expect consent not to last indefinitely. A prudent rule that works across Europe: a choice cookie lasting six months, after which the banner reappears. If you add cookies of a new category, the previous consent does not cover them and the banner must be shown again immediately.
How to use the log in an inspection
The log matters at the moment someone asks for it. That is why it must be searchable by date and by identifier, exportable in a readable format such as CSV and stored on a system other than the user's browser. If a user exercises the right of access, the log lets you tell them which choice they made and when. If the authority opens an inspection, the typical request is to produce the records of a given period.
How Konsento handles it
Konsento records every consent automatically: identifier, date and time, type of choice, categories accepted and refused, language, page, country and later withdrawals or changes. The log can be consulted from the dashboard, filtered and exported to CSV, and is included in the one-time licence of 86 euros per domain, no subscription. In the free plans of most services it is the first feature to be missing, as we explained in another article. You can try it free for 15 days: konsento.cloud/en/register.