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