Transparency alternatives to Cargoson
Other Shipping and logistics vendors we measure, sorted by how much we found at them and not at Cargoson. This is a comparison of disclosure, not of features or fitness.
12 shown of 82 that differ from Cargoson on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Cargoson 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, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Cargoson” is the one that closes them.
| Vendor | Score | Found there, not found at Cargoson | Found at Cargoson, not found there | |
|---|---|---|---|---|
| AfterShipaftership.comSee also Transparency alternatives to AfterShip | 83/100 | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | 1 security.txt (RFC 9116) | Compare |
| Sendcloudsendcloud.comSee also Transparency alternatives to Sendcloud | 70/100 | 6 Data processing agreement, Data location stated, Status page with history, +3 | 1 security.txt (RFC 9116) | Compare |
| FourKitesfourkites.comSee also Transparency alternatives to FourKites | 48/100 | 5 Data processing agreement, Data location stated, Status page with history, +2 | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Bringgbringg.comSee also Transparency alternatives to Bringg | 43/100 | 4 Data processing agreement, Status page with history, Notice before subprocessors change, +1 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| EasyPosteasypost.comSee also Transparency alternatives to EasyPost | 43/100 | 3 Data location stated, Status page with history, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Easyshipeasyship.comSee also Transparency alternatives to Easyship | 43/100 | 3 Data processing agreement, Status page with history, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Metapackmetapack.comSee also Transparency alternatives to Metapack | 43/100 | 3 Data processing agreement, Uptime SLA with a figure, Notice before subprocessors change | 1 security.txt (RFC 9116) | Compare |
| ShipStationshipstation.comSee also Transparency alternatives to ShipStation | 43/100 | 3 Data location stated, Status page with history, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| parcelLabparcellab.comSee also Transparency alternatives to parcelLab | 35/100 | 3 Status page with history, Notice before subprocessors change, Named privacy contact | 1 Public pricing | Compare |
| Quivoquivo.coSee also Transparency alternatives to Quivo | 35/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Seven Senderssevensenders.comSee also Transparency alternatives to Seven Senders | 35/100 | 3 Data location stated, Status page with history, Named privacy contact | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Locuslocus.shSee also Transparency alternatives to Locus | 30/100 | 3 Data location stated, Certifications named, Named privacy contact | 2 HTTPS enforced with HSTS, 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.