Transparency alternatives to Cookie Script
Other Privacy compliance vendors we measure, sorted by how much we found at them and not at Cookie Script. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 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 “Found there, not found at Cookie Script” is the one that closes them.
| Vendor | Score | Found there, not found at Cookie Script | Found at Cookie Script, not found there | |
|---|---|---|---|---|
| TrustArctrustarc.comSee also Transparency alternatives to TrustArc | 70/100 | 5 Subprocessor list, Data location stated, Status page with history, +2 | 1 Public pricing | Compare |
| Privacy Beeprivacybee.comSee also Transparency alternatives to Privacy Bee | 48/100 | 5 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +2 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| Transcendtranscend.ioSee also Transparency alternatives to Transcend | 43/100 | 5 Status page with history, Certifications named, Uptime SLA with a figure, +2 | 3 Public pricing, Notice before subprocessors change, Named privacy contact | Compare |
| Didomididomi.ioSee also Transparency alternatives to Didomi | 48/100 | 4 Subprocessor list, Status page with history, Certifications named, +1 | 2 Data processing agreement, Public pricing | Compare |
| Secure Privacysecureprivacy.aiSee also Transparency alternatives to Secure Privacy | 57/100 | 3 Subprocessor list, Status page with history, HTTPS enforced with HSTS | 1 Notice before subprocessors change | Compare |
| Securitisecuriti.aiSee also Transparency alternatives to Securiti | 48/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 1 Notice before subprocessors change | Compare |
| Ketchketch.comSee also Transparency alternatives to Ketch | 43/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Cookiebotcookiebot.comSee also Transparency alternatives to Cookiebot | 39/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| Privadoprivado.aiSee also Transparency alternatives to Privado | 39/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 2 Data processing agreement, Notice before subprocessors change | Compare |
| iDox.aiidox.aiSee also Transparency alternatives to iDox.ai | 35/100 | 3 Data location stated, HTTPS enforced with HSTS, No third-party tracking before consent | 3 Data processing agreement, Public pricing, Notice before subprocessors change | Compare |
| Relyancerelyance.aiSee also Transparency alternatives to Relyance | 22/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 4 Data processing agreement, Public pricing, Notice before subprocessors change, +1 | Compare |
| Cookiefirstcookiefirst.comSee also Transparency alternatives to Cookiefirst | 48/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 Public pricing | 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.