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