Basics

What Is Proof of Consent, and What Should You Keep?

Proof of consent is a record of each visitor's cookie choice: when, what they chose and which banner they saw. What to keep, for how long, and what not to.

By the allowedit team · · 7 min read

The short answer

  • The GDPR says you must be able to demonstrate that a person consented. For cookies, that means a record of each choice, not just a banner on your site.
  • A useful record holds a random consent id, the time, the choices, the banner version and the region. It doesn't need the visitor's IP address or name.
  • Keep records for as long as you rely on the consent, plus a margin to answer complaints. Many sites keep them for a year.
  • Log choices when they're made, not on every page view, and make records easy to search by consent id and export.

Proof of consent is a record that shows a specific visitor made a specific cookie choice: when they made it, what they allowed or refused, and which version of your banner they saw. The GDPR requires you to be able to demonstrate consent, and a banner on its own doesn't do that. A consent log does, and a good one stores very little personal data.

This guide covers what to record, what to leave out, how long to keep it, and how to use it when someone asks.

Why isn't the banner itself proof?

Because a banner shows what you asked, not what anyone answered.

Article 7(1) of the GDPR says that where processing is based on consent, the controller must be able to demonstrate that the person consented. If a visitor complains that your site tracked them without agreement, or a regulator asks how you obtained consent, "we have a banner" isn't an answer. You need to show that this visitor, at this time, saw this banner and chose this.

Other laws point the same way. Quebec's Law 25 lets its regulator ask how consent was obtained. US state laws expect you to show you honoured opt-out requests, including Global Privacy Control signals.

Enough to answer three questions: who (without naming them), what they saw, and what they chose.

FieldWhy it matters
Consent idA random identifier, also stored in the visitor's consent cookie. It links the visitor to the record without identifying them.
TimestampWhen the choice was made.
ChoicesEach category: preferences, analytics, marketing, allowed or refused.
ActionHow they chose: accepted all, rejected all, customised, opted out, or an automatic Global Privacy Control opt-out.
Banner versionWhich wording, categories and cookie list they saw. Without this, you can't show what they agreed to.
RegionCountry, and state or province where it matters (the US, Quebec), because the rules differ.
Device typeDesktop, mobile or tablet, useful for spotting a banner that misbehaves on one kind of device.

The banner version is the field people forget. If you change your categories, add a new marketing tool or reword the banner, older consents were given to something different. A version number on each record, plus a history of what each version contained, lets you show exactly what was on screen.

What should you leave out?

The goal is proof, not surveillance. Data protection law asks you to collect only what you need (data minimisation, Article 5(1)(c) of the GDPR), and a consent log is no exception.

  • IP addresses. An IP address is personal data. It doesn't add much as proof, since IP addresses change and are shared. A random consent id does the linking job better.
  • Names and emails. Not needed for website visitors.
  • Full browser fingerprints. A hashed user agent can help separate records, but there's no need for more.
  • Every page view. Log the choice when it's made. Logging every page load creates huge logs full of personal data for no benefit.

There's no single legal period. The reasonable answer is: for as long as you rely on that consent, plus enough time to deal with questions or complaints about it.

In practice:

  • A choice is usually remembered for 6 to 12 months before the banner asks again. Keeping the record at least that long covers the consent's whole life.
  • Complaints can arrive after the fact, so many businesses keep records for a year or more.
  • If you're in a dispute, keep the relevant records until it's resolved.

Whatever you choose, write it down in your privacy policy and stick to it. Keeping records forever is its own data protection problem.

The log earns its keep in a few specific situations.

A visitor asks what they agreed to

They can give you their consent id (shown in the preferences panel, or stored in their consent cookie), and you look up the record: the time, the choices and the banner version.

You show the banner versions, your region rules, and a sample of records, including rejections. A log that has plenty of "Rejected all" entries is good evidence your reject button works.

You need to check a change didn't break anything

If your consent rate jumps or drops after a release, the log, split by region and device, shows where. A sudden jump to near 100% acceptance in the EU usually means the reject button disappeared.

A client asks for evidence

Agencies can export a client's records as CSV, or send a monthly report, instead of sharing a dashboard login.

These are different things, and you need both:

  • A cookie declaration tells visitors what cookies your site uses, by category, with their purpose and duration. It belongs on your privacy page. See cookie declarations.
  • A consent log records what each visitor chose. It's for you, to prove consent when asked.

The banner version ties them together: each version captures the categories and cookie list that the declaration showed at the time.

allowedit's proof of consent log is on every plan, including free. When a visitor makes a choice, the script records:

  • a random consent id (also saved in the allowedit_consent cookie on your site, and shown to the visitor in the preferences panel),
  • the timestamp,
  • the choices for preferences, analytics and marketing,
  • the action (accepted all, rejected all, customised, opted out, or a GPC opt-out),
  • the banner version,
  • the region (country, and state or province),
  • the device type, and
  • a hashed user agent.

No IP addresses are stored. Our hosting reads the visitor's IP address in passing to work out their region, and it's never written to the log. Records are created only when someone makes or changes a choice, never on page views.

You can search by consent id, filter by date, and export as CSV. Records are kept for 30 days on the free plan and 1 year on Pro and Agency. The same data feeds the consent analytics: consent rate, the accept, reject and customise split, by region and device, over time.

The consent log docs show how to look up a record and export it, and the consent cookie docs explain what's stored in the visitor's browser.

A quick checklist

  • Every choice is logged, including rejections and GPC opt-outs.
  • Each record has a consent id the visitor can find.
  • Each record has the banner version, and you can see what each version contained.
  • No IP addresses or names are stored.
  • You log choices, not page views.
  • Your retention period is written in your privacy policy.
  • You can export records when someone asks.

If your current tool can't tick these boxes, compare options on our comparison pages, or read the full GDPR banner requirements for the rest of the checklist.

This article is general information, not legal advice. How long to keep records and what counts as enough proof can depend on your country and your business.

Frequently asked questions

Is a consent log legally required?

The GDPR doesn't name a consent log, but Article 7(1) requires you to be able to demonstrate consent. A log of each choice is the practical way to do that. Quebec's Law 25 and US state laws also expect you to show you honoured choices.

Should the log store IP addresses?

It doesn't need to. An IP address is personal data, so storing it adds risk without making the record much stronger. A random consent id stored in the visitor's own consent cookie links the visitor to the record instead.

How does a visitor find their consent id?

With allowedit, the consent id is shown in the preferences panel and stored in the allowedit_consent cookie. If a visitor asks what they agreed to, they can give you the id and you can look up the record.

How long does allowedit keep consent records?

30 days on the free plan and 1 year on Pro and Agency. You can export them as CSV at any time to keep them longer in your own systems.