Alternatives to Okendo
Other Loyalty and rewards vendors we measure, sorted by how much they publish that Okendo does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 29 that differ from Okendo on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Okendo has 6 gaps in what we could measure: Subprocessor list, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “publishes and Okendo does not” is the one that closes them.
| Vendor | Score | Publishes, and Okendo does not | Okendo publishes, and they do not | |
|---|---|---|---|---|
| Yotpoyotpo.com | 61/100 | 4 Subprocessor list, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 2 Data processing agreement, Data location stated | Compare |
| Voucherifyvoucherify.io | 65/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 1 Certifications named | Compare |
| Talon.Onetalon.one | 52/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 2 Status page with history, Public pricing | Compare |
| Zinrelozinrelo.com | 52/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 2 Status page with history, Public pricing | Compare |
| Bazaarvoicebazaarvoice.com | 39/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 3 Data processing agreement, Public pricing, Notice before subprocessors change | Compare |
| Growavegrowave.io | 35/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Status page with history, Certifications named, +1 | Compare |
| Joyjoy.so | 35/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Status page with history, Certifications named, +1 | Compare |
| Piggypiggy.eu | 35/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 4 Data location stated, Status page with history, Certifications named, +1 | Compare |
| Annex Cloudannexcloud.com | 30/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Status page with history, Public pricing, +1 | Compare |
| Judge.mejudge.me | 26/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 5 Data processing agreement, Data location stated, Public pricing, +2 | Compare |
| Kangarookangaroorewards.com | 26/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 5 Data processing agreement, Status page with history, Public pricing, +2 | Compare |
| Perkvilleperkville.com | 26/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 5 Data processing agreement, Status page with history, Public pricing, +2 | 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.