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