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