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