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