Transparency alternatives to Sovrn
Other Affiliate and partner marketing vendors we measure, sorted by how much we found at them and not at Sovrn. 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 “Found there, not found at Sovrn” is the one that closes them.
| Vendor | Score | Found there, not found at Sovrn | Found at Sovrn, not found there | |
|---|---|---|---|---|
| Reditusgetreditus.comSee also Transparency alternatives to Reditus | 74/100 | 6 Data processing agreement, Data location stated, Public pricing, +3 | 1 security.txt (RFC 9116) | Compare |
| Everfloweverflow.ioSee also Transparency alternatives to Everflow | 57/100 | 5 Data processing agreement, Data location stated, Status page with history, +2 | 2 Subprocessor list, security.txt (RFC 9116) | Compare |
| PartnerStackpartnerstack.comSee also Transparency alternatives to PartnerStack | 52/100 | 4 Data processing agreement, Data location stated, Certifications named, +1 | 1 security.txt (RFC 9116) | Compare |
| UpPromoteuppromote.comSee also Transparency alternatives to UpPromote | 45/100 | 4 Data processing agreement, Data location stated, Public pricing, +1 | 2 Subprocessor list, Named privacy contact | Compare |
| LeadDynoleaddyno.comSee also Transparency alternatives to LeadDyno | 43/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 2 Subprocessor list, security.txt (RFC 9116) | Compare |
| Partneropartnero.comSee also Transparency alternatives to Partnero | 43/100 | 4 Data processing agreement, Data location stated, Public pricing, +1 | 3 Subprocessor list, security.txt (RFC 9116), Named privacy contact | Compare |
| Refersionrefersion.comSee also Transparency alternatives to Refersion | 41/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 2 Subprocessor list, Named privacy contact | Compare |
| Channelscalerchannelscaler.comSee also Transparency alternatives to Channelscaler | 39/100 | 4 Data location stated, Public pricing, Certifications named, +1 | 2 Subprocessor list, security.txt (RFC 9116) | Compare |
| Referral Rockreferralrock.comSee also Transparency alternatives to Referral Rock | 43/100 | 3 Data processing agreement, Data location stated, Public pricing | 1 Subprocessor list | Compare |
| Affiseaffise.comSee also Transparency alternatives to Affise | 39/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 1 Subprocessor list | Compare |
| Affonsoaffonso.ioSee also Transparency alternatives to Affonso | 39/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 3 Subprocessor list, security.txt (RFC 9116), Named privacy contact | Compare |
| ingeniousingenioustechnologies.comSee also Transparency alternatives to ingenious | 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.