Alternatives to Real Cookie Banner
Other Privacy compliance vendors we measure, sorted by how much they publish that Real Cookie Banner does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 26 that differ from Real Cookie Banner on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Real Cookie Banner has 10 gaps in what we could measure: Subprocessor list, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Real Cookie Banner does not” is the one that closes them.
| Vendor | Score | Publishes, and Real Cookie Banner does not | Real Cookie Banner publishes, and they do not | |
|---|---|---|---|---|
| BigIDbigid.com | 61/100 | 6 Subprocessor list, Status page with history, Certifications named, +3 | 1 Data processing agreement | Compare |
| Didomididomi.io | 61/100 | 6 Subprocessor list, Status page with history, Certifications named, +3 | 1 Data processing agreement | Compare |
| Securitisecuriti.ai | 57/100 | 6 Status page with history, Public pricing, Certifications named, +3 | 1 Data location stated | Compare |
| CookieYescookieyes.com | 70/100 | 5 Subprocessor list, Public pricing, HTTPS enforced with HSTS, +2 | nothing | Compare |
| Cookiebotcookiebot.com | 48/100 | 4 Status page with history, Public pricing, HTTPS enforced with HSTS, +1 | 1 Data processing agreement | Compare |
| Ketchketch.com | 43/100 | 4 Status page with history, Public pricing, HTTPS enforced with HSTS, +1 | 1 Data processing agreement | Compare |
| Cookiefirstcookiefirst.com | 48/100 | 3 HTTPS enforced with HSTS, Notice before subprocessors change, Named privacy contact | nothing | Compare |
| Cookie Scriptcookie-script.com | 35/100 | 3 Public pricing, Notice before subprocessors change, Named privacy contact | 1 Data location stated | Compare |
| Enzuzoenzuzo.com | 35/100 | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Data location stated | Compare |
| Usercentricsusercentrics.com | 35/100 | 3 Public pricing, HTTPS enforced with HSTS, Named privacy contact | 1 Data processing agreement | Compare |
| OneTrustonetrust.com | 18/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | 2 Data processing agreement, Data location stated | Compare |
| Syrenissyrenis.com | 17/100 | 3 Uptime SLA with a figure, HTTPS enforced with HSTS, Named privacy contact | 2 Data processing agreement, Data location stated | 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.