Transparency alternatives to Chauffeur Drive Systems
Other Route planning and delivery vendors we measure, sorted by how much they publish that Chauffeur Drive Systems does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 65 that differ from Chauffeur Drive Systems on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Chauffeur Drive Systems has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, 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 “publishes and Chauffeur Drive Systems does not” is the one that closes them.
| Vendor | Score | Publishes, and Chauffeur Drive Systems does not | Chauffeur Drive Systems publishes, and they do not | |
|---|---|---|---|---|
| RideCorideco.com | 52/100 | 5 Subprocessor list, Data location stated, HTTPS enforced with HSTS, +2 | 1 Public pricing | Compare |
| Lytxlytx.com | 48/100 | 5 Subprocessor list, Data location stated, Status page with history, +2 | 2 Public pricing, Certifications named | Compare |
| NextBillion.ainextbillion.ai | 48/100 | 4 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Badger Mapsbadgermapping.com | 43/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | 1 Certifications named | Compare |
| Netradynenetradyne.com | 43/100 | 4 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +1 | 1 Public pricing | Compare |
| Routalroutal.com | 43/100 | 4 Data location stated, HTTPS enforced with HSTS, No third-party tracking before consent, +1 | 1 Certifications named | Compare |
| Nautonauto.com | 30/100 | 4 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | 2 Public pricing, Certifications named | Compare |
| Tookanjungleworks.com | 48/100 | 3 Data processing agreement, Data location stated, HTTPS enforced with HSTS | nothing | Compare |
| Navixynavixy.com | 39/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 1 Public pricing | Compare |
| Routificroutific.com | 39/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 1 Certifications named | Compare |
| One Step GPSonestepgps.com | 35/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| FTS GPSftsgps.com | 30/100 | 3 Data processing agreement, Status page with history, Notice before subprocessors change | 2 Public pricing, Certifications named | 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.