Alternatives to Termly
Other Privacy compliance vendors we measure, sorted by how much they publish that Termly does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 34 that differ from Termly on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Termly has 6 gaps in what we could measure: Subprocessor list, Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116). The column “publishes and Termly does not” is the one that closes them.
| Vendor | Score | Publishes, and Termly does not | Termly publishes, and they do not | |
|---|---|---|---|---|
| BigIDbigid.com | 61/100 | 4 Subprocessor list, Status page with history, HTTPS enforced with HSTS, +1 | 3 Data processing agreement, Public pricing, Named privacy contact | Compare |
| Privacy Beeprivacybee.com | 48/100 | 4 Subprocessor list, HTTPS enforced with HSTS, No third-party tracking before consent, +1 | 4 Data processing agreement, Data location stated, Notice before subprocessors change, +1 | Compare |
| Transcendtranscend.io | 43/100 | 4 Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | 4 Data location stated, Public pricing, Notice before subprocessors change, +1 | Compare |
| CookieYescookieyes.com | 70/100 | 3 Subprocessor list, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Certifications named, Named privacy contact | Compare |
| Didomididomi.io | 61/100 | 3 Subprocessor list, Status page with history, HTTPS enforced with HSTS | 2 Data processing agreement, Public pricing | Compare |
| Securitisecuriti.ai | 57/100 | 3 Status page with history, HTTPS enforced with HSTS, No third-party tracking before consent | 2 Data location stated, Notice before subprocessors change | Compare |
| Secure Privacysecureprivacy.ai | 52/100 | 3 Subprocessor list, Status page with history, HTTPS enforced with HSTS | 4 Data location stated, Certifications named, Notice before subprocessors change, +1 | Compare |
| Cookiebotcookiebot.com | 48/100 | 3 Status page with history, HTTPS enforced with HSTS, No third-party tracking before consent | 4 Data processing agreement, Certifications named, Notice before subprocessors change, +1 | Compare |
| Ketchketch.com | 43/100 | 2 Status page with history, HTTPS enforced with HSTS | 3 Data processing agreement, Certifications named, Notice before subprocessors change | Compare |
| Enzuzoenzuzo.com | 35/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 4 Data location stated, Certifications named, Notice before subprocessors change, +1 | Compare |
| DataGraildatagrail.io | 17/100 | 2 Status page with history, HTTPS enforced with HSTS | 6 Data processing agreement, Data location stated, Public pricing, +3 | Compare |
| Syrenissyrenis.com | 17/100 | 2 Uptime SLA with a figure, HTTPS enforced with HSTS | 5 Data processing agreement, Data location stated, Public pricing, +2 | 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.