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