Alternatives to Cookiebot
Other Privacy compliance vendors we measure, sorted by how much they publish that Cookiebot does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 26 that differ from Cookiebot on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Cookiebot has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Certifications named, Uptime SLA with a figure, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Cookiebot does not” is the one that closes them.
| Vendor | Score | Publishes, and Cookiebot does not | Cookiebot publishes, and they do not | |
|---|---|---|---|---|
| CookieYescookieyes.com | 70/100 | 4 Data processing agreement, Subprocessor list, security.txt (RFC 9116), +1 | 2 Status page with history, No third-party tracking before consent | Compare |
| BigIDbigid.com | 61/100 | 4 Subprocessor list, Certifications named, security.txt (RFC 9116), +1 | 2 Public pricing, No third-party tracking before consent | Compare |
| Didomididomi.io | 61/100 | 4 Subprocessor list, Certifications named, Notice before subprocessors change, +1 | 2 Public pricing, No third-party tracking before consent | Compare |
| Securitisecuriti.ai | 57/100 | 3 Data processing agreement, Certifications named, Named privacy contact | 1 Data location stated | Compare |
| Cookiefirstcookiefirst.com | 48/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 3 Status page with history, Public pricing, No third-party tracking before consent | Compare |
| Cookie Scriptcookie-script.com | 35/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | Compare |
| Ethycaethyca.com | 43/100 | 2 Data processing agreement, Notice before subprocessors change | 3 Status page with history, Public pricing, No third-party tracking before consent | Compare |
| Enzuzoenzuzo.com | 35/100 | 2 Data processing agreement, security.txt (RFC 9116) | 3 Data location stated, Status page with history, No third-party tracking before consent | Compare |
| OneTrustonetrust.com | 18/100 | 2 Certifications named, Named privacy contact | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| Syrenissyrenis.com | 17/100 | 2 Uptime SLA with a figure, Named privacy contact | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| Ketchketch.com | 43/100 | 1 Named privacy contact | 1 No third-party tracking before consent | Compare |
| Usercentricsusercentrics.com | 35/100 | 1 Named privacy contact | 2 Status page with history, No third-party tracking before consent | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.