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