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