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