Transparency alternatives to Track-POD
Other Route planning and delivery vendors we measure, sorted by how much we found at them and not at Track-POD. This is a comparison of disclosure, not of features or fitness.
12 shown of 64 that differ from Track-POD on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Track-POD has 11 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, 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 Track-POD” is the one that closes them.
| Vendor | Score | Found there, not found at Track-POD | Found at Track-POD, not found there | |
|---|---|---|---|---|
| NextBillion.ainextbillion.aiSee also Transparency alternatives to NextBillion.ai | 48/100 | 6 Data processing agreement, Public pricing, Certifications named, +3 | 1 Data location stated | Compare |
| RideCorideco.comSee also Transparency alternatives to RideCo | 52/100 | 5 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +2 | nothing | Compare |
| One Step GPSonestepgps.comSee also Transparency alternatives to One Step GPS | 35/100 | 5 Status page with history, Public pricing, Certifications named, +2 | 1 Data location stated | Compare |
| Lytxlytx.comSee also Transparency alternatives to Lytx | 48/100 | 4 Subprocessor list, Status page with history, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Tookanjungleworks.comSee also Transparency alternatives to Tookan | 48/100 | 4 Data processing agreement, Public pricing, Certifications named, +1 | nothing | Compare |
| Netradynenetradyne.comSee also Transparency alternatives to Netradyne | 43/100 | 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Routalroutal.comSee also Transparency alternatives to Routal | 43/100 | 4 Public pricing, HTTPS enforced with HSTS, No third-party tracking before consent, +1 | nothing | Compare |
| Navixynavixy.comSee also Transparency alternatives to Navixy | 39/100 | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | 1 Data location stated | Compare |
| Badger Mapsbadgermapping.comSee also Transparency alternatives to Badger Maps | 30/100 | 4 Status page with history, Public pricing, HTTPS enforced with HSTS, +1 | 1 Data location stated | Compare |
| Nautonauto.comSee also Transparency alternatives to Nauto | 30/100 | 4 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | 1 Data location stated | Compare |
| Routificroutific.comSee also Transparency alternatives to Routific | 39/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | nothing | Compare |
| Avriosavrios.comSee also Transparency alternatives to Avrios | 30/100 | 3 Subprocessor list, Public pricing, HTTPS enforced with HSTS | 1 Data location stated | 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.