How to document and test cookie consent
A useful record lets someone else answer two questions months later. What choice did visitors see, and what did the website do when they made it?
Sources checkedKeep evidence suited to the decision
GDPR Article 5(2) requires controllers to demonstrate compliance with the processing principles. When consent is the basis for processing personal data, Article 7(1) requires the controller to be able to show that the person consented. The right evidence depends on the processing.
Keep the notice and purpose text that was live, its published version, the user actions available and a dated account of how you tested them. A count of accepted choices can show a trend. It cannot establish that a named person agreed to a particular use. For an email newsletter, for example, retain the relevant subscription record and the wording used at sign-up in the mailing system.
A requirement to demonstrate consent does not create a general duty to identify every visitor. Before storing IP addresses or persistent identifiers, consider whether you need them for the stated purpose, their legal basis and retention, and whether less identifying evidence will do.
A sample test record
This example shows what a studio owner could write after testing a new booking template. Substitute the actual revision, date and observations from your own installation.
- Scope
- Booking landing page and confirmation page. Record the browser, region, date and published banner revision used in the test.
- Fresh visit and refusal
- List the cookie and storage key names and relevant requests observed before a choice and after refusal. Record whether the booking can still be completed.
- Acceptance and withdrawal
- Choose just the analytics purpose. Record when its script first runs. Reopen settings, withdraw it, reload the page and check subsequent requests and storage.
- Follow-up
- Identify any unclassified item, its owner and the change needed. Record the result of a new test after that change.
Keep personal information and live cookie values out of screenshots or reports wherever possible. A request to a provider is an observation. Inspect its purpose and behaviour before classifying it.
What a browser scan can establish
A scan observes a particular browser visiting a bounded set of pages. Nodkeeper’s hosted scanner requires domain verification and compares the initial, refused and accepted states when it can operate the banner. Its report distinguishes observations from requests the scanner held back. Read the coverage and incomplete phases alongside the findings.
A service may appear only after signing in, submitting a booking, playing a video or visiting from another region. A public crawl may miss those paths. Test important journeys separately, including withdrawal. Rerun checks when a CMS extension, tag manager or embedded provider changes.
What Nodkeeper keeps
With hosted reporting, Nodkeeper groups received actions by site, date and policy revision. A person can act more than once. These figures count choices. The standalone installation keeps choices in the visitor’s browser and sends no activity to Nodkeeper. Historical notice versions, configuration and your own test notes can be retained alongside any evidence required for a particular processing activity.
Open website scans. Read about reporting data and retention.