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