Transparency alternatives to Real Cookie Banner
Other Privacy compliance vendors we measure, sorted by how much we found at them and not at Real Cookie Banner. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 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 11 gaps in what we could measure: Subprocessor list, Data location stated, 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 “Found there, not found at Real Cookie Banner” is the one that closes them.
| Vendor | Score | Found there, not found at Real Cookie Banner | Found at Real Cookie Banner, not found there | |
|---|---|---|---|---|
| TrustArctrustarc.comSee also Transparency alternatives to TrustArc | 70/100 | 7 Subprocessor list, Data location stated, Status page with history, +4 | nothing | Compare |
| Didomididomi.ioSee also Transparency alternatives to Didomi | 61/100 | 7 Subprocessor list, Data location stated, Status page with history, +4 | 1 Data processing agreement | Compare |
| Secure Privacysecureprivacy.aiSee also Transparency alternatives to Secure Privacy | 70/100 | 6 Subprocessor list, Data location stated, Status page with history, +3 | nothing | Compare |
| Privacy Beeprivacybee.comSee also Transparency alternatives to Privacy Bee | 48/100 | 6 Subprocessor list, Public pricing, Certifications named, +3 | 1 Data processing agreement | Compare |
| Securitisecuriti.aiSee also Transparency alternatives to Securiti | 48/100 | 5 Status page with history, Public pricing, Certifications named, +2 | nothing | Compare |
| Ketchketch.comSee also Transparency alternatives to Ketch | 43/100 | 5 Data location stated, Status page with history, Public pricing, +2 | 1 Data processing agreement | Compare |
| Transcendtranscend.ioSee also Transparency alternatives to Transcend | 43/100 | 5 Status page with history, Certifications named, Uptime SLA with a figure, +2 | nothing | Compare |
| Privadoprivado.aiSee also Transparency alternatives to Privado | 39/100 | 5 Data location stated, Public pricing, Certifications named, +2 | 1 Data processing agreement | Compare |
| Cookiefirstcookiefirst.comSee also Transparency alternatives to Cookiefirst | 48/100 | 4 Data location stated, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | nothing | Compare |
| Termlytermly.ioSee also Transparency alternatives to Termly | 48/100 | 4 Data location stated, Public pricing, Certifications named, +1 | nothing | Compare |
| CookieYescookieyes.comSee also Transparency alternatives to CookieYes | 43/100 | 4 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | nothing | Compare |
| Cookiebotcookiebot.comSee also Transparency alternatives to Cookiebot | 39/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 1 Data processing agreement | 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.