CookieYes alternatives
For a site running the CookieYes banner that has hit a plan limit or a missing feature and wants to know whether to upgrade or move. CookieYes and 6 platforms its users switch to, measured on the consent rules of the GDPR and the ePrivacy Directive and on California’s opt-out rules, from each vendor’s own pages. read 2026-10-22
Best free plan for US visitors
Cookiebot
Its free plan honors Global Privacy Control and shows Californians the opt-out link, which CookieYes keeps for Pro.
Best if pageview caps are why you are leaving
Complianz
A WordPress plugin on your own server with no pageview or session limits, sold by number of sites.
Best if privacy requests come next
Osano
Says yes on every row, and its request handling sits on the same platform; confirm which plan carries what.
CookieYes against the alternatives, rule by rule
The rows are the same requirements as our consent management platforms compare, with CookieYes in the first column so you can read each alternative against what you run today. A note under a word names the plan or the limit that applies.
| Requirement | CookieYes | Cookiebot | Complianz | Osano | CookieHub | iubenda | Termly |
|---|---|---|---|---|---|---|---|
| Blocks non-essential cookies until consentePrivacy Art. 5(3); GDPR Art. 6(1)(a) | yesauto-blocking on Free | yesmanual on the free plan | yesknown services | yes | yes | yes | yes |
| Keeps a consent record you can exportGDPR Art. 7(1) | yesCSV; 1 year back on Free, 5 on paid | paid planCSV; kept up to 12 months | paid planrecords; export not stated | yes | not statedkept 1 month on Free, 12 on paid | not statedlog on every plan; export not stated | paid plan |
| Honors Global Privacy Control signalsCCPA regs § 7025(b) | paid planPro and Ultimate | yesfree plan included | paid plan | yes | yesfree plan included | yes | yesper its release notes |
| Shows a “Do Not Sell or Share” linkCal. Civ. Code § 1798.135(a)(1) | yesfooter link code | yesfor California visitors | yesopt-out page | yes | yes | yes“Your Privacy Choices” link | yes |
| Offers a data processing agreementGDPR Art. 28(3) | yes | yesunsigned template | not stateddata stays on your server | yes | yes | yes | yes |
| Serves a different banner by regionopt-in (ePrivacy Art. 5(3)) vs opt-out (§ 1798.135) | paid planPro and Ultimate | paid plan | paid plan | yes | paid planBasic and up | paid planAdvanced and Ultimate | paid plan |
| Supports the IAB Transparency and Consent FrameworkIAB Europe TCF (ad-funded sites) | paid planPro and Ultimate | paid plan | paid plan | yes | paid planBusiness and up | paid planevery paid plan | paid plan |
| Finds and blocks scripts automatically (scanner)what ePrivacy Art. 5(3) covers on your site | yes5 scans a month on Free | paid planfree: one initial scan | yesfull site scan premium | yes | yesone-time scan on Free | partialauto-blocking labelled experimental | yesquarterly scans on Free |
| On Google’s certified CMP listGoogle ads in the EEA, UK and Switzerland | yes | yes | yes | yes | yes | yes | yes |
Source: vendor documentation, read 2026-10-22. “not stated” means the vendor’s own documentation does not say. | |||||||
Why sites leave CookieYes, and where each reason points
Each reason below is a row of the table above seen from the CookieYes side. The right-hand column is worked out from the same cells, so it moves when they do.
| The reason | What it touches | Where the alternatives stand |
|---|---|---|
| Global Privacy Control starts at Pro | CCPA regs § 7025(b) | Cookiebot, Osano, CookieHub, iubenda and Termly honor it with no plan qualifier on their own pages; Cookiebot and CookieHub list it on their free plans. |
| A banner per region starts at Pro | ePrivacy Art. 5(3) vs § 1798.135 | Only Osano lists it without a plan qualifier. Everywhere else it is a paid feature too, so this alone is rarely worth a move. |
| Traffic outgrows the pageview cap | the plan meter, not a rule | Complianz says its plans carry no pageview or session limits. CookieHub counts sessions, Osano monthly visitors, and Cookiebot the number of subpages on the site. |
| Free log exports reach back one year | GDPR Art. 7(1) | iubenda calls its log permanent; Cookiebot and CookieHub keep records up to 12 months. CookieYes's paid plans export five years, so on this row upgrading beats switching. |
| Google ads in the EEA need the IAB framework | Google certified CMP list | It is a paid feature on every alternative except Osano, whose pages do not tie it to a plan. All seven platforms are on Google's list. |
Source: vendor plan pages, read 2026-10-22. Rows are rules or plan meters, never prices. | ||
The two comparisons CookieYes users ask about
CookieYes vs Cookiebot
They meter differently. CookieYes plans count pageviews per domain; Cookiebot plans count subpages, meaning every unique URL on the domain, and its free plan covers one domain of up to 50 of them. On the meters alone, a small site with heavy traffic fits Cookiebot’s free plan; a large site with light traffic fits CookieYes’s.
The free plans split on the two rules that matter most. Cookiebot’s free plan honors Global Privacy Control and shows California visitors the opt-out link, but blocking is manual, it scans once, and a visitor’s consent lasts at most a month before the banner asks again. CookieYes Free blocks automatically and keeps an exportable log, but has no GPC until Pro. Pick by the gap you cannot live with: a California site that sells or shares data needs the signal handled; an EU site needs scripts held back before consent without hand-tagging each one.
Higher up they converge: CookieYes Pro and every Cookiebot Premium tier add region-based banners, the IAB framework and scheduled scans. Cookiebot keeps consent records up to 12 months on every plan; CookieYes’s paid plans export five years.
Complianz vs CookieYes
This is a choice of where the banner lives. Complianz is a WordPress plugin: its site says it runs entirely on your own server and sends no visitor data elsewhere, and it sets no pageview or session limits. CookieYes is a hosted service that plugs into WordPress and other site builders and counts pageviews.
The free Complianz plugin blocks known third-party services, scans the site and adds an opt-out page for California. Records of consent, GPC, banners chosen by visitor location and the IAB framework are premium. Its paid editions are sold by number of sites (one, five or 25) and billed yearly, and the 25-site Agency edition adds a multisite plugin. For an agency with a stack of WordPress clients that is usually the deciding line. Outside WordPress, its pricing page names only a Shopify app.
Both sit on the same rows of the table above. If the choice is still close, the consent management platforms compare sets them against each other for a new site rather than a switch.
Moving off CookieYes without a gap
The banner is the easy part. What goes wrong in a switch is the record you leave behind and the opt-out that quietly stops working for a day. In this order:
- Export the CookieYes consent log. Under Consent Log, choose Export as CSV and pick the widest date range your plan allows (one year back on Free, five on paid plans).
- File it with your other records. The new platform’s log starts empty on the day it goes live; the export is your only proof of consent collected before then (GDPR Art. 7(1)).
- Swap the scripts in one release. Remove the CookieYes code in the same change that adds the new one, so the site never runs two banners deciding which tags fire.
- Scan again and check the categories. Make sure every cookie sits in the category your cookie policy names, and add the new platform’s own cookie.
- Rebuild the US opt-out. The link must be titled “Do Not Sell or Share My Personal Information” (§ 1798.135(a)(1)); CookieYes’s guide calls its footer link a “Do not sell” link, so do not carry the old label over. Our guide to the “Do Not Sell or Share” link has the wording, and the GPC checker shows whether your browser is sending the signal while you test.
- Expect returning visitors to be asked again. CookieYes keeps each choice in its own “cookieyes-consent” cookie. Unless the new vendor’s documentation says it can carry those choices over, plan for everyone to see the new banner once.
- Cancel last. CookieYes says you keep the service until the end of the plan period, so cancel once the new banner is live and the export is saved.
“It shall be as easy to withdraw as to give consent.”
CookieYes meets that with its revisit consent button on every plan. Before you cancel, find the same thing on the new platform (a floating button, a footer link or a preference center) and put it where the old one was.
Run the new banner through the cookie banner checklist the day it goes live, and keep the CookieYes export beside the result.
Each platform in short
CookieYes first, as the baseline, then each alternative. If you are weighing the other common free banner instead, our Cookiebot alternatives page runs the same rows from Cookiebot’s side, and Termly vs iubenda sets the two banner-plus-policy bundles head to head.
CookieYes
What it is
The platform you are on: a hosted banner with auto-blocking, a scanner and a consent log, sold per domain as Free, Basic, Pro and Ultimate.
Who it fits
A site that wants scripts blocked before consent on a free plan, and is ready for Pro once it needs the US signal or a banner per region.
What the rule requires and whether it meets it
Auto-blocking, the opt-in and opt-out templates, the revisit consent button and the consent log are on every plan. GPC, geo-targeting, the combined GDPR-and-US banner and the IAB framework start at Pro.
Check with the vendor
Its guide labels the footer link “Do not sell”. California’s statute titles it “Do Not Sell or Share My Personal Information”, so check the text on your site.
Cookiebot
What it is
The consent platform of Usercentrics: a free plan and five Premium tiers chosen by the number of subpages on the domain.
Who it fits
A small, busy, US-facing site: the free plan honors GPC and covers one domain of up to 50 subpages.
What the rule requires and whether it meets it
GPC and the California opt-out link are on the free plan. Automatic blocking, scheduled scans, region-based banners, the IAB framework and CSV export of consents are Premium. Consent records are kept up to 12 months on every plan.
Check with the vendor
On the free plan a visitor’s consent expires after at most a month. Its data processing agreement is published as an unsigned template; ask how it is executed for your account.
Complianz
What it is
A WordPress plugin, free and premium, that runs on your own server and generates the legal documents beside the banner.
Who it fits
WordPress sites that outgrew a pageview cap, and agencies: editions cover one, five or 25 sites, the last with a multisite plugin.
What the rule requires and whether it meets it
The free plugin blocks known third-party services and adds a California opt-out page. GPC, records of consent, location-based banners and the IAB framework are premium.
Check with the vendor
Exporting consent records is not described. Its site says no processing agreement is needed for the plugin itself; ask for terms on any Complianz service that handles visitor data off your server.
Osano
What it is
A privacy platform whose consent product sits beside request handling and data mapping. Its free plan covers one user, one domain and 5,000 monthly visitors.
Who it fits
A firm leaving CookieYes because it now has privacy requests to answer as well as a banner to run.
What the rule requires and whether it meets it
Its feature list says yes to every row here: blocking, exportable logs, GPC, “Do Not Sell/Share” management, localized banners, IAB strings and scheduled tracker discovery. Its processing addendum is on its trust hub.
Check with the vendor
The pages we read do not say which plan carries which feature. Get that in writing before you choose one.
CookieHub
What it is
A hosted consent platform priced by sessions rather than pageviews, from a free tier through Starter, Basic, Business and Enterprise.
Who it fits
A small site that wants GPC and automatic blocking without moving up a tier.
What the rule requires and whether it meets it
Every plan, free included, blocks scripts, keeps proof of consent and honours GPC; the processing agreement it offers follows GDPR Art. 28. Consent by visitor location needs Basic, and the IAB framework needs Business.
Check with the vendor
The free tier is for fewer than 1,000 sessions a month, and CookieHub says the banner stops showing past that until you upgrade. Free keeps consent records one month and export is not described.
iubenda
What it is
A consent banner sold with privacy and cookie policy generators, on a free plan and three paid plans.
Who it fits
A site that wants its banner and its policies from one vendor, and a consent log it calls permanent.
What the rule requires and whether it meets it
It blocks before consent, detects GPC automatically and offers a “Your Privacy Choices” link for the US laws. Its consent log is on every plan, the free one included, and its paid plans call it permanent; the IAB framework is on every paid plan and geo-targeting starts at Advanced.
Check with the vendor
Its help article calls auto-blocking experimental and points to other prior-blocking methods. Exporting the log is not described.
Termly
What it is
Policy generators and a consent platform under one account: Free, Starter, Pro+ and Agency.
Who it fits
A small site that counts banner views rather than pageviews, or an agency wanting one account for client sites.
What the rule requires and whether it meets it
Its script auto blocker and a consent preference center are on every plan, with scans quarterly on Free. Exportable consent logs, regional consent rules and the IAB framework are on Pro+ and Agency.
Check with the vendor
Its release notes (1 January 2026) add a notice that confirms an honored GPC signal, but name no plan. Confirm it runs on yours before you rely on it for California visitors.
How we compared them
We started from CookieYes and added the hosted banners and the WordPress plugin a small site on CookieYes is most likely to move to, plus one broader privacy platform for firms that now handle requests too. Each is on Google’s certified CMP list. Plan allowances (pageviews, sessions, subpages) come from the same pages; prices do not appear here.
Each row is a requirement the rule itself sets, with the article or section cited beside it. Every cell comes from the vendor’s own public documentation, read on 2026-10-22; we did not run trials, take demos or accept vendor answers that are not published.
“not stated” means the vendor’s documentation does not say either way. It is not a “no”: ask the vendor and get the answer in writing. “paid plan” means the feature exists but not on the free or entry tier. There are no scores, ratings or prices on this page.
Verdicts are editorial: no vendor can buy a verdict position or displace another vendor.
This page is information, not legal advice. A tool that meets a row does not make a site compliant; how it is set up does.
Questions
How is CookieYes priced, and what changes from plan to plan?
Per domain, per month, on four plans: Free, Basic, Pro and Ultimate. Each plan carries a monthly pageview allowance (5,000 on Free, unlimited on Ultimate) and paid plans bill extra pageviews above it. Only one free plan is allowed per account. The features that change between plans are in the plan-by-plan table on this page; the price figures are on CookieYes’s own pricing page, and we do not repeat them.
Is CookieYes Free enough for a California site?
If the business sells or shares personal information, § 7025(b) of the CCPA regulations says it must process a valid opt-out preference signal, such as Global Privacy Control, as an opt-out request. CookieYes lists GPC on Pro and Ultimate only. Free does offer the opt-out banner and a “Do not sell” link; check the link’s wording against the statute’s title.
Do I have to keep my old CookieYes consent records after I switch?
GDPR Art. 7(1) asks a controller relying on consent to be able to demonstrate it. The article names no number of years, so the usual approach is to keep the export for as long as you rely on that consent; your counsel can set the period. The new platform cannot prove consent it did not collect.
Will visitors see the banner again after the switch?
Usually, yes. CookieYes stores each visitor’s choice in its own cookie, and the new platform reads its own. Unless the new vendor documents a way to carry choices over, every returning visitor is asked once more, and the new log starts from that answer.
Should I upgrade CookieYes instead of switching?
Often. If the gap is GPC, a banner per region or a longer log, CookieYes Pro closes it, and most alternatives keep those features on paid plans too. Switching pays off when the reason is structural: you want the banner on your own WordPress server, a platform that also handles requests, or a meter that suits your traffic. Run your current banner through the cookie banner checklist first to see which gaps are real.