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