Transparency alternatives to Didomi
Other Privacy compliance vendors we measure, sorted by how much we found at them and not at Didomi. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from Didomi on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Didomi has 6 gaps in what we could measure: Data processing agreement, Data location stated, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at Didomi” is the one that closes them.
| Vendor | Score | Found there, not found at Didomi | Found at Didomi, not found there | |
|---|---|---|---|---|
| TrustArctrustarc.comSee also Transparency alternatives to TrustArc | 70/100 | 3 Data processing agreement, Data location stated, Uptime SLA with a figure | 1 HTTPS enforced with HSTS | Compare |
| Privacy Beeprivacybee.comSee also Transparency alternatives to Privacy Bee | 48/100 | 3 Public pricing, No third-party tracking before consent, security.txt (RFC 9116) | 3 Status page with history, Notice before subprocessors change, Named privacy contact | Compare |
| Termlytermly.ioSee also Transparency alternatives to Termly | 48/100 | 3 Data processing agreement, Data location stated, Public pricing | 4 Subprocessor list, Status page with history, HTTPS enforced with HSTS, +1 | Compare |
| CookieYescookieyes.comSee also Transparency alternatives to CookieYes | 43/100 | 3 Data processing agreement, Public pricing, security.txt (RFC 9116) | 4 Subprocessor list, Status page with history, Certifications named, +1 | Compare |
| Transcendtranscend.ioSee also Transparency alternatives to Transcend | 43/100 | 3 Data processing agreement, Uptime SLA with a figure, security.txt (RFC 9116) | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | Compare |
| Enzuzoenzuzo.comSee also Transparency alternatives to Enzuzo | 35/100 | 3 Data processing agreement, Public pricing, security.txt (RFC 9116) | 5 Subprocessor list, Status page with history, Certifications named, +2 | Compare |
| Secure Privacysecureprivacy.aiSee also Transparency alternatives to Secure Privacy | 57/100 | 2 Data processing agreement, Public pricing | 2 Certifications named, Notice before subprocessors change | Compare |
| Cookiefirstcookiefirst.comSee also Transparency alternatives to Cookiefirst | 48/100 | 2 Data processing agreement, Data location stated | 3 Subprocessor list, Status page with history, Certifications named | Compare |
| Securitisecuriti.aiSee also Transparency alternatives to Securiti | 48/100 | 2 Data processing agreement, Public pricing | 2 Subprocessor list, Notice before subprocessors change | Compare |
| Ethycaethyca.comSee also Transparency alternatives to Ethyca | 43/100 | 2 Data processing agreement, Data location stated | 4 Subprocessor list, Status page with history, Certifications named, +1 | Compare |
| Ketchketch.comSee also Transparency alternatives to Ketch | 43/100 | 2 Data location stated, Public pricing | 3 Subprocessor list, Certifications named, Notice before subprocessors change | Compare |
| Cookiebotcookiebot.comSee also Transparency alternatives to Cookiebot | 39/100 | 2 Data location stated, Public pricing | 4 Subprocessor list, Certifications named, Notice before subprocessors change, +1 | 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.