What is the cmplz_banner-status cookie?
cmplz_banner-status is an HTTP cookie set by Complianz, a widely used consent management platform (CMP) plugin, primarily on WordPress sites. It is created as soon as a visitor first loads a page where the Complianz plugin is active, even before any consent choice has been made.
Its role is purely technical: to record the state of the cookie consent banner (shown, dismissed, accepted/rejected), so the banner does not reappear unnecessarily on every page the same visitor loads.
What data it stores
The cookie stores a simple value indicating the status of the visitor's interaction with the consent banner (for example, whether it has been displayed and closed). The exact value format may vary depending on the installed Complianz version.
The data stays stored locally in the visitor's browser and is read by the Complianz script running on that site; the cookie is not sent to third-party servers operated by the provider.
What it is used for
For the site owner, this cookie enables the consent banner to work correctly: without it, the plugin could not know whether the banner has already been shown or dismissed, and visitors would see the consent request on every single page load.
It is not used for tracking behavior, profiling, or advertising — its purpose is strictly limited to the operation of the consent mechanism.
Does it require consent?
In CookieFix's classification, cmplz_banner-status falls under the strictly necessary category. Under the ePrivacy Directive 2002/58/EC (implemented in Romania via Law 506/2004) and ANSPDCP guidance, cookies strictly necessary for a service explicitly requested by the user (here, the consent mechanism itself) do not require prior consent.
- No visitor consent is required before it is set.
- The site owner must still list it in the cookie policy, along with its purpose and duration.
- It should not be placed in categories that are auto-blocked pending consent.
How to block or delete cmplz_banner-status
Visitors can delete or block this cookie at any time from their browser settings (Chrome, Firefox, Edge, Safari — under site data/cookie management). Blocking it does not seriously affect browsing, but it may cause the consent banner to reappear on every visit.
Because it is strictly necessary, a CMP like CookieFix does not block it automatically before consent — only cookies in the statistics, marketing, and preferences categories are held back until the user gives their consent.
Frequently asked questions
It's a technical cookie set by the Complianz plugin that records the status of a visitor's interaction with the cookie consent banner.
No, it is classified as strictly necessary because it supports the consent mechanism the visitor has explicitly requested.
Its typical duration is 1 year, after which the browser removes it automatically unless it is renewed.
Yes, even though it doesn't require consent, the site owner must disclose it, along with its purpose and duration, to meet GDPR transparency obligations.