Privacy finding
The cookie list gives a purpose that the tracker list contradicts
Privacy Warning Severity: High
Part of the audit The cookie list says one thing, the browser shows another. Finding id: privacy.declaredPurposeVsDatabase.
What it costs you
A cookie filed under the wrong purpose is asked for under the wrong heading, or not asked for at all.
What to do
Correct the purpose in the cookie list and in the consent tool, so the cookie waits for the right consent.
What it checks
- Declared purpose differs from cookie database
How to fix it
File the cookie under its real purpose
- Read the vendor's own documentation for this cookie.
- Change the purpose in the published list and the category in the consent tool.
- Check that the cookie is no longer set before that category is accepted.
How to check: Crawl the site again. The cookie no longer appears in this rule.
A real case
A Belgian legal information website argued that its analytics cookies were strictly necessary and so needed no consent. The Belgian data protection authority rejected that and fined the company 15,000 euros in December 2019.
How to verify by hand
The consent platform's own scan report; a person for cookies set only in rare flows.
What this relies on
The scan is right and the published list is out of date.