Transparency alternatives to PartnerStack
Other Affiliate and partner marketing vendors we measure, sorted by how much we found at them and not at PartnerStack. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from PartnerStack on at least one criterion we measured for both. Public transparency score, not a product or security rating.
PartnerStack has 5 gaps in what we could measure: Status page with history, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at PartnerStack” is the one that closes them.
| Vendor | Score | Found there, not found at PartnerStack | Found at PartnerStack, not found there | |
|---|---|---|---|---|
| Awinawin.comSee also Transparency alternatives to Awin | 26/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | Compare |
| Reditusgetreditus.comSee also Transparency alternatives to Reditus | 74/100 | 2 HTTPS enforced with HSTS, Notice before subprocessors change | 1 Uptime SLA with a figure | Compare |
| Everfloweverflow.ioSee also Transparency alternatives to Everflow | 57/100 | 2 Status page with history, HTTPS enforced with HSTS | 3 Subprocessor list, Certifications named, Uptime SLA with a figure | Compare |
| LeadDynoleaddyno.comSee also Transparency alternatives to LeadDyno | 43/100 | 2 Status page with history, HTTPS enforced with HSTS | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | Compare |
| Affiseaffise.comSee also Transparency alternatives to Affise | 39/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | Compare |
| belboonbelboon.comSee also Transparency alternatives to belboon | 35/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 5 Data processing agreement, Subprocessor list, Public pricing, +2 | Compare |
| Post Affiliate Propostaffiliatepro.comSee also Transparency alternatives to Post Affiliate Pro | 30/100 | 2 Status page with history, HTTPS enforced with HSTS | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | Compare |
| Refersionrefersion.comSee also Transparency alternatives to Refersion | 27/100 | 2 Status page with history, HTTPS enforced with HSTS | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | Compare |
| Daisycondaisycon.comSee also Transparency alternatives to Daisycon | 26/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 6 Data processing agreement, Subprocessor list, Public pricing, +3 | Compare |
| Tapfiliatetapfiliate.comSee also Transparency alternatives to Tapfiliate | 26/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | Compare |
| ReferralCandyreferralcandy.comSee also Transparency alternatives to ReferralCandy | 22/100 | 2 Status page with history, security.txt (RFC 9116) | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | Compare |
| UpPromoteuppromote.comSee also Transparency alternatives to UpPromote | 45/100 | 1 HTTPS enforced with HSTS | 4 Subprocessor list, Certifications named, Uptime SLA with a figure, +1 | 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.