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