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