Proof of Cookie Consent: Which Fields Should a Record Hold?
Having a cookie banner is one thing; proving what a visitor agreed to, when, and which text they were shown is another. When a complaint or a request for explanation arrives, that is the first question. This article lists the fields a consent record should hold and how to check yours.
This article is for information only and is not legal advice. Check the primary text, or ask a lawyer about your specific case.
Why keep proof at all?
Article 9 of Personal Data Protection Law No. 91/2025/QH15 governs the data subject's consent: voluntary, clear and specific, and silence is not consent. A banner that displays correctly is not enough; you should be able to show how that consent happened. Without a record, you only have your word.
Five minimum fields
- Time. The moment of recording, set by your server, not by the visitor's browser clock.
- Action. Accept all, reject, or customise; if customised, which categories were on or off (necessary, measurement, advertising...).
- Banner version. The exact words the visitor read: title, description, category names. This is the field most often missing. Edit the banner later and older records point at text nobody can reconstruct.
- Source. A choice the visitor actively made, or a browser privacy signal (such as GPC or DNT) that the banner recorded as a rejection.
- Minimal technical trace. IP address and user agent help when there is a dispute, but they are personal data: keep them only as long as needed, truncate them when the period ends, and never publish them.
Why the banner version matters
Suppose next month you rename "Measurement" to "Improve your experience". Last month's record says only "accepted measurement"; without a stored version you cannot show which wording the visitor saw. A clean approach is to compute a fingerprint (a hash) of the full banner content currently displayed, store it with the record, and keep a copy of the content that matches the hash. Two records with the same hash mean two visitors saw the same notice.
Check your setup in 3 minutes
- Try to answer from the data you have: "On the 1st of this month a visitor clicked Reject. Which exact text did they see?"
- Export your records to a spreadsheet: which column shows the action and the categories chosen?
- Is there a column for the banner version? If you edited the wording yesterday, can you still read the day-before record?
- Who can see the records? Do IP addresses sit anywhere public, or in emails?
- When a visitor asks you to erase their data, can you anonymise their records while keeping your statistics?
How Widget.vn helps
Widget.vn's free cookie banner records each choice with its time, the action, the categories chosen, the source, and a server-computed banner version code (older records may leave that code blank); a copy of the text behind each code is archived so it can be read later. Site owners can view the records in the dashboard and export them to CSV, scoped to their own account. It helps you keep evidence; it does not make a site compliant on its own — you still need a privacy policy and sound data-handling processes.
Source: Personal Data Protection Law No. 91/2025/QH15 (Article 9).