Transparency alternatives to Redo
Other Returns management vendors we measure, sorted by how much we found at them and not at Redo. This is a comparison of disclosure, not of features or fitness.
12 shown of 30 that differ from Redo on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Redo has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at Redo” is the one that closes them.
| Vendor | Score | Found there, not found at Redo | Found at Redo, not found there | |
|---|---|---|---|---|
| Narvarnarvar.comSee also Transparency alternatives to Narvar | 52/100 | 6 Subprocessor list, Data location stated, Certifications named, +3 | 3 Public pricing, security.txt (RFC 9116), Named privacy contact | Compare |
| WeSupplywesupplylabs.comSee also Transparency alternatives to WeSupply | 70/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | 1 security.txt (RFC 9116) | Compare |
| Sortedsorted.comSee also Transparency alternatives to Sorted | 35/100 | 4 Subprocessor list, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | 3 Public pricing, security.txt (RFC 9116), Named privacy contact | Compare |
| Loop Returnsloopreturns.comSee also Transparency alternatives to Loop Returns | 39/100 | 3 Data processing agreement, Certifications named, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Claimlaneclaimlane.comSee also Transparency alternatives to Claimlane | 30/100 | 2 Data processing agreement, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Swap Commerceswap-commerce.comSee also Transparency alternatives to Swap Commerce | 26/100 | 2 HTTPS enforced with HSTS, Notice before subprocessors change | 1 Public pricing | Compare |
| ClickPostclickpost.aiSee also Transparency alternatives to ClickPost | 22/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Refundidrefundid.comSee also Transparency alternatives to Refundid | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 3 Public pricing, security.txt (RFC 9116), Named privacy contact | Compare |
| FloorFoundfloorfound.comSee also Transparency alternatives to FloorFound | 17/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 3 Public pricing, security.txt (RFC 9116), Named privacy contact | Compare |
| Happy Returnshappyreturns.comSee also Transparency alternatives to Happy Returns | 13/100 | 2 Certifications named, HTTPS enforced with HSTS | 3 Public pricing, security.txt (RFC 9116), Named privacy contact | Compare |
| Corsocorso.comSee also Transparency alternatives to Corso | 22/100 | 1 Data location stated | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| yaylohyayloh.comSee also Transparency alternatives to yayloh | 22/100 | 1 HTTPS enforced with HSTS | 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.