What is the cmplz_consented_services cookie?
The cmplz_consented_services cookie is set by Complianz, a popular consent management platform (CMP) plugin mostly used on WordPress sites, to implement GDPR- and ePrivacy-compliant cookie banners.
It appears as soon as a visitor interacts with the site's cookie banner (accepts all, rejects, or customizes choices), created by the Complianz script loaded on the page.
What data it stores
The cookie stores the list of services or cookie categories (e.g. statistics, marketing, preferences) for which the visitor has given consent. The exact value varies depending on the site's configuration and the services detected by Complianz's scanner.
The data is stored locally in the visitor's browser and read by the Complianz script on the site to decide which third-party scripts are allowed to load. It is not sent to any Complianz external servers.
What it is used for
The purpose of this cookie is purely functional: it lets the site remember the visitor's consent choices so they are not asked again on every page or visit.
For the site owner, this cookie is essential for proving and correctly enforcing consent — for example, to automatically keep marketing scripts blocked until the user has explicitly accepted them.
Does it require consent?
Since it is strictly necessary for the consent mechanism itself to function, cmplz_consented_services does not require the visitor's own consent, under Article 5 of Romania's Law 506/2004 (transposing the ePrivacy Directive) and ANSPDCP's guidance, as well as similar strictly-necessary exemptions under most EU implementations.
The site owner should still list it in the cookie policy, under the “strictly necessary” category, with its real purpose and duration.
How to block or delete cmplz_consented_services
A visitor can delete or block this cookie at any time from browser settings (Chrome, Firefox, Edge, Safari — the per-site cookie management section), though doing so resets consent preferences and the banner will reappear on the next visit.
- Manual deletion: from the browser's privacy settings, by searching for the site's domain
- Full blocking: privacy-focused extensions or private browsing mode
For site owners, strictly necessary cookies like this one should not be blocked before consent, but all other scripts (analytics, marketing) should be blocked automatically until consent is given. A CMP like CookieFix handles this automatically, stopping third-party scripts until the visitor gives their consent.
Frequently asked questions
No. It's a technical, strictly necessary cookie that only stores the visitor's consent choices and does not track their behavior.
No, since it is strictly necessary for the consent banner to function, but it must be listed in the site's cookie policy.
Your consent preferences are reset, and the cookie banner will appear again on your next visit to the site.
Typically around 1 year, though the exact duration can vary depending on the site's Complianz configuration.