Transparency alternatives to Okendo
Other Loyalty and rewards vendors we measure, sorted by how much we found at them and not at Okendo. This is a comparison of disclosure, not of features or fitness.
12 shown of 37 that differ from Okendo on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Okendo has 7 gaps in what we could measure: Subprocessor list, Data location stated, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “Found there, not found at Okendo” is the one that closes them.
| Vendor | Score | Found there, not found at Okendo | Found at Okendo, not found there | |
|---|---|---|---|---|
| Yotpoyotpo.comSee also Transparency alternatives to Yotpo | 61/100 | 4 Subprocessor list, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 Data processing agreement | Compare |
| Voucherifyvoucherify.ioSee also Transparency alternatives to Voucherify | 65/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 Certifications named | Compare |
| Joyjoy.soSee also Transparency alternatives to Joy | 57/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 2 Status page with history, Certifications named | Compare |
| Talon.Onetalon.oneSee also Transparency alternatives to Talon.One | 52/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 2 Status page with history, Public pricing | Compare |
| TrueLoyaltrueloyal.comSee also Transparency alternatives to TrueLoyal | 52/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 2 Status page with history, Public pricing | Compare |
| Stamp Mestampme.comSee also Transparency alternatives to Stamp Me | 39/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 3 Data processing agreement, Status page with history, Notice before subprocessors change | Compare |
| Growavegrowave.ioSee also Transparency alternatives to Growave | 35/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Status page with history, Certifications named, +1 | Compare |
| Smile.iosmile.ioSee also Transparency alternatives to Smile.io | 35/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Status page with history, Certifications named, +1 | Compare |
| ProvenExpertprovenexpert.comSee also Transparency alternatives to ProvenExpert | 27/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 5 Data processing agreement, Status page with history, Public pricing, +2 | Compare |
| Kognitivkognitiv.comSee also Transparency alternatives to Kognitiv | 26/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Named privacy contact | 5 Data processing agreement, Status page with history, Public pricing, +2 | Compare |
| Perkvilleperkville.comSee also Transparency alternatives to Perkville | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 5 Data processing agreement, Status page with history, Public pricing, +2 | Compare |
| LoyaltyLionloyaltylion.comSee also Transparency alternatives to LoyaltyLion | 43/100 | 2 Subprocessor list, HTTPS enforced with HSTS | 2 Data processing agreement, Notice before subprocessors change | 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.