Transparency alternatives to Sovrn
Other Affiliate and partner marketing vendors we measure, sorted by how much they publish that Sovrn does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 39 that differ from Sovrn on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Sovrn has 9 gaps in what we could measure: Data processing agreement, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change. The column “publishes and Sovrn does not” is the one that closes them.
| Vendor | Score | Publishes, and Sovrn does not | Sovrn publishes, and they do not | |
|---|---|---|---|---|
| Reditusgetreditus.com | 74/100 | 6 Data processing agreement, Data location stated, Public pricing, +3 | 1 security.txt (RFC 9116) | Compare |
| PartnerStackpartnerstack.com | 61/100 | 5 Data processing agreement, Data location stated, Public pricing, +2 | 1 security.txt (RFC 9116) | Compare |
| Everfloweverflow.io | 57/100 | 5 Data processing agreement, Data location stated, Status page with history, +2 | 2 Subprocessor list, security.txt (RFC 9116) | Compare |
| UpPromoteuppromote.com | 45/100 | 4 Data processing agreement, Data location stated, Public pricing, +1 | 2 Subprocessor list, Named privacy contact | Compare |
| LeadDynoleaddyno.com | 43/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 2 Subprocessor list, security.txt (RFC 9116) | Compare |
| Partneropartnero.com | 43/100 | 4 Data processing agreement, Data location stated, Public pricing, +1 | 3 Subprocessor list, security.txt (RFC 9116), Named privacy contact | Compare |
| Channelscalerchannelscaler.com | 39/100 | 4 Data location stated, Public pricing, Certifications named, +1 | 2 Subprocessor list, security.txt (RFC 9116) | Compare |
| Affiseaffise.com | 39/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 1 Subprocessor list | Compare |
| Affonsoaffonso.io | 39/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 3 Subprocessor list, security.txt (RFC 9116), Named privacy contact | Compare |
| ingeniousingenioustechnologies.com | 39/100 | 3 Data processing agreement, Data location stated, HTTPS enforced with HSTS | 2 Subprocessor list, security.txt (RFC 9116) | Compare |
| Referral Rockreferralrock.com | 39/100 | 3 Data processing agreement, Data location stated, Public pricing | 2 Subprocessor list, security.txt (RFC 9116) | Compare |
| Webgainswebgains.com | 39/100 | 3 Data processing agreement, Data location stated, HTTPS enforced with HSTS | 2 Subprocessor list, security.txt (RFC 9116) | 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.