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