Alternatives to heyData
Other Privacy compliance vendors we measure, sorted by how much they publish that heyData does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 24 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 “publishes and heyData does not” is the one that closes them.
| Vendor | Score | Publishes, and heyData does not | heyData publishes, and they do not | |
|---|---|---|---|---|
| CookieYescookieyes.com | 70/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 1 Named privacy contact | Compare |
| BigIDbigid.com | 61/100 | 6 Subprocessor list, Data location stated, Status page with history, +3 | 1 Named privacy contact | Compare |
| Didomididomi.io | 61/100 | 5 Subprocessor list, Data location stated, Status page with history, +2 | nothing | Compare |
| Securitisecuriti.ai | 57/100 | 5 Data processing agreement, Status page with history, Public pricing, +2 | nothing | Compare |
| Cookiebotcookiebot.com | 48/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 1 Named privacy contact | Compare |
| Cookiefirstcookiefirst.com | 48/100 | 3 Data processing agreement, Data location stated, Notice before subprocessors change | nothing | Compare |
| Ethycaethyca.com | 43/100 | 3 Data processing agreement, Data location stated, Notice before subprocessors change | 1 Named privacy contact | Compare |
| Ketchketch.com | 43/100 | 3 Data location stated, Status page with history, Public pricing | nothing | Compare |
| Cookie Scriptcookie-script.com | 35/100 | 3 Data processing agreement, Public pricing, Notice before subprocessors change | 1 HTTPS enforced with HSTS | Compare |
| Enzuzoenzuzo.com | 35/100 | 3 Data processing agreement, Public pricing, security.txt (RFC 9116) | 1 Named privacy contact | Compare |
| Usercentricsusercentrics.com | 35/100 | 2 Data location stated, Public pricing | nothing | Compare |
| iubendaiubenda.com | 30/100 | 2 Data location stated, 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.