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