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