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