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