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