Cookie consent present but CMP vendor is unrecognised
A consent management platform (CMP) is the underlying system that runs a cookie banner, logs consent choices, and handles vendor agreements. This check identifies which CMP vendor a site is using, if any of the well-known ones, OneTrust, Cookiebot, CookieYes, Iubenda, can be recognised. On this site, a cookie consent banner is present, but the CMP vendor behind it isn't one this check recognises. Custom or unrecognised consent banners may lack the things tier-1 CMPs provide by default: proper GDPR-compliant consent logging, audit trails, and Data Processing Agreements (DPAs) with the vendors involved. Custom banners often fail an audit when a regulator asks for proof of exactly what a specific visitor consented to and when, because that record-keeping wasn't built in from the start. Your developer and privacy lawyer should evaluate switching to a recognised CMP, such as CookieYes, roughly $10 a month, or Cookiebot, which has a free tier, both of which come with a DPA, audit logs, and IAB TCF (Interactive Advertising Bureau Transparency and Consent Framework) compliance built in. This is a bigger project, typically around a week including migration and testing.
Why this matters
Custom or unrecognised consent banners may lack the things tier-1 CMPs provide by default: proper GDPR-compliant consent logging, audit trails, and Data Processing Agreements (DPAs) with the vendors involved. Custom banners often fail an audit when a regulator asks for proof of exactly what a specific visitor consented to and when, because that record-keeping wasn't built in from the start.
How to fix it
Your developer and privacy lawyer should evaluate switching to a recognised CMP, such as CookieYes, roughly $10 a month, or Cookiebot, which has a free tier, both of which come with a DPA, audit logs, and IAB TCF (Interactive Advertising Bureau Transparency and Consent Framework) compliance built in. This is a bigger project, typically around a week including migration and testing.