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