Cookie banner plugins

Your cookie banner can load from outside before anyone clicks Accept

A consent tool can serve its banner from your WordPress site, or load the banner from a vendor CDN in the visitor browser before Accept. That banner request can reach the vendor before anyone chooses. Consent logs are a different step. A banner served from a CDN does not by itself show consent records left your site. The cookie-banner checker tool measures a live site; this page documents plugin setups.

Based on plugin documentation, not tests of your site. Your settings can change what loads. This is not legal advice or a compliance rating.

Scan your site for third-party requests

This scan checks requests made by a visitor’s browser. It cannot inspect consent logs stored on your server or in a vendor dashboard.

How we group cookie banner plugins

We separate where the banner script is served from where consent logs are stored. A plugin that serves the banner from your WordPress site is different from a plugin that loads the banner from a vendor CDN in the visitor browser before Accept. A banner served from a CDN does not by itself show consent records left your site. Consent timing for other trackers and vendor retention length have not been tested.

Banner on your site vs banner from a vendor CDN

Banner served from your WordPress site

Some consent tools serve the banner assets from your WordPress site. The visitor browser talks to your site for that banner. Consent records can still stay local or sync elsewhere depending on the product — check the Consent records column.

Banner script from a vendor CDN

Other consent tools load the banner from a vendor CDN in the visitor browser before Accept. That request can include the visitor IP at page load. A banner served from a CDN does not by itself show consent records left your site. Consent logs may stay on your site, go to a vendor dashboard, or both when that product is connected.

Before consent

A vendor CDN banner script loads before Accept by design. That column marks the banner request itself. It is not a scan of other trackers on your site. Consent timing for advertising or analytics vendors is not tested here.

Cookie banner plugins

No paid placement. Banners served from your WordPress site first, then vendor CDN banners, then plugins not yet reviewed. Names are alphabetical within each group.

PluginBanner served fromConsent recordsDocumented banner hostsHow long data is keptBefore consentLinksSource
Complianz

This row covers Complianz with the banner served from your WordPress site. Docs describe a native, self-hosted banner. Individual consent records stay on your WordPress server when Records of Consent is enabled (Premium). Optional cookiedatabase.org sync for cookie descriptions is a separate admin path and is not a visitor banner host. Consent timing for other trackers is not tested here.

Banner served from your WordPress siteOn your WordPress server when Records of Consent is enabled (Premium)No outside banner-script host documented for this setup. Other page requests are not covered.Not assessedNot tested
Cookiebot

This row covers Cookiebot with the banner script loaded from consent.cookiebot.com in the visitor browser before Accept. Docs place uc.js early in the page head for auto-blocking. Consent logs are available from the Cookiebot Manager. A first-party CookieConsent cookie can also store the choice on your site. A banner served from a CDN does not by itself show consent records left your site. Consent timing for other trackers is not tested here.

Banner script from a vendor CDNConsent logs in the vendor dashboardconsent.cookiebot.comNot assessedBanner script loads before Accept
CookieYes

This row covers CookieYes (cookie-law-info) when the site is connected to the CookieYes web app and the banner script loads from cdn-cookieyes.com in the visitor browser before Accept. Consent logs stay in CookieYes when connected and logging is enabled. Plugin-only operation without that web-app connection is a different setup and is not this row. A banner served from a CDN does not by itself show consent records left your site. Consent timing for other trackers is not tested here.

Banner script from a vendor CDNConsent logs in CookieYes when connected and logging is enabledcdn-cookieyes.comNot assessedBanner script loads before Accept
iubenda

This row covers iubenda Cookie Solution with the banner script loaded from cdn.iubenda.com in the visitor browser before Accept. Banner preferences can stay in a cookie or local storage on your site domain. Consent Database records can be sent to iubenda when that product is connected. A banner served from a CDN does not by itself show consent records left your site. Consent timing for other trackers is not tested here.

Banner script from a vendor CDNBanner choice on-site; proof or logs can go to the vendor when connectedcdn.iubenda.comNot assessedBanner script loads before Accept
  • None
Termly

This row covers Termly with the banner script loaded from app.termly.io in the visitor browser before Accept. Consent logs are managed from the Termly dashboard. Consent storage API hosts are a separate step from the banner script host listed here. A banner served from a CDN does not by itself show consent records left your site. Consent timing for other trackers is not tested here.

Banner script from a vendor CDNConsent logs in the vendor dashboardapp.termly.ioNot assessedBanner script loads before Accept
  • None
Usercentrics

This row covers Usercentrics with the banner script loaded from web.cmp.usercentrics.eu in the visitor browser before Accept. Consent history is available from the Usercentrics admin interface. Current WordPress install guidance may route through Cookiebot by Usercentrics; this row covers the Usercentrics script hosts named in the docs. A banner served from a CDN does not by itself show consent records left your site. Consent timing for other trackers is not tested here.

Banner script from a vendor CDNConsent logs in the vendor dashboardweb.cmp.usercentrics.euNot assessedBanner script loads before Accept
  • None

What this table does and does not prove

This table describes the named cookie-banner setups. It does not show what loads on your site. Banner serving and consent-record storage are separate columns. A banner served from a CDN does not by itself show consent records left your site. Where no outside banner-script host is documented, that applies only to the banner path described. Other page requests are not covered. The cookie-banner checker tool measures a live site and is a different page. Plugins marked Not reviewed have not been assessed. We have not tested consent timing for other trackers, and we have not assessed how long vendor logs are kept. The site scan linked below checks requests made by a visitor’s browser. It cannot inspect consent logs stored on your server or in a vendor dashboard.

Documentation snapshot: Oct 7, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-cookie-banner-plugin-privacy