Download websites that use CookieYes

About CookieYes

A consent banner is not a feature anyone asked for. A regulator required a record of permission, and a small industry appeared to produce that record on demand. CookieYes belongs to that industry. The product scans a site for cookies, shows a banner, holds tags back until a visitor agrees and keeps a log that can be produced if someone asks for it. Presence on a domain is a legal posture rendered in JavaScript rather than a technical decision.

What the posture implies about the operator is specific. Someone concluded that the site falls in scope for European data protection law, for one of the American state privacy statutes, or for a client contract that demanded it. Consent tooling marks the boundary of where privacy regulation is actually being obeyed rather than where it nominally applies, which is a more interesting boundary than a map of jurisdictions. As of September 2026 the file holds 872,624 sites running it, and United States contributes 221,106 of them, which says less about European law than about how quickly American operators decided that European visitors were worth keeping.

The version data is where the picture gains texture. We have recorded 537 distinct versions in the wild, with 3.5.5 the one we encounter most. A spread that wide is not noise. Hosted customers receive the current script from a content network and move together, while installs that ship inside a plugin or a copied snippet freeze at whatever release was current on the day someone pasted the code. A stale consent script is a real problem rather than a cosmetic one, because consent records collected by an old version may not match what the current banner claims to be doing.

Version spread also functions as a rough maintenance index for the site as a whole. An operator who left a consent script untouched for several release cycles is unlikely to be diligent about the rest of the front end, which makes this column useful well beyond the privacy question that put it there.

Detection recognises the script and the banner, not whether either is configured correctly, and a banner is not compliance. Two further limits matter for anyone planning to lean on the numbers. Some deployments serve the consent layer only to visitors from certain regions, so a crawl from one vantage point will miss them, and a site can carry a consent tool while still firing trackers before anyone has agreed to anything, which our detection does not attempt to judge.

The commercial use is straightforward and does not work one domain at a time. Consent platforms compete for the same installed base, privacy consultancies need to find the sites with no consent layer at all, and adtech vendors care about which sites will hand them a usable signal. All of that requires a population. Every domain in a country or a domain-ending segment with its consent tool named, joined against your own prospect file, and compared across snapshots so that churn between vendors becomes visible instead of assumed. Launched in 2018 and sold on a Freemium model, the product competes in a market where switching costs are low, which is exactly why movement between snapshots is the part worth watching.