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