Transparency alternatives to Cytric
Other Business travel management vendors we measure, sorted by how much we found at them and not at Cytric. This is a comparison of disclosure, not of features or fitness.
12 shown of 28 that differ from Cytric on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Cytric has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Cytric” is the one that closes them.
| Vendor | Score | Found there, not found at Cytric | Found at Cytric, not found there | |
|---|---|---|---|---|
| TravelPerktravelperk.comSee also Transparency alternatives to TravelPerk | 35/100 | 4 Data location stated, Public pricing, Certifications named, +1 | 1 HTTPS enforced with HSTS | Compare |
| BizAwaybizaway.comSee also Transparency alternatives to BizAway | 35/100 | 3 Data processing agreement, Public pricing, Certifications named | 1 security.txt (RFC 9116) | Compare |
| Serkoserko.comSee also Transparency alternatives to Serko | 35/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Zauizaui.comSee also Transparency alternatives to Zaui | 35/100 | 3 Data processing agreement, Public pricing, Uptime SLA with a figure | 1 security.txt (RFC 9116) | Compare |
| Spotnanaspotnana.comSee also Transparency alternatives to Spotnana | 30/100 | 3 Data processing agreement, Data location stated, Named privacy contact | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| BCD Travelbcdtravel.comSee also Transparency alternatives to BCD Travel | 26/100 | 2 Data location stated, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| CWTmycwt.comSee also Transparency alternatives to CWT | 26/100 | 2 Data location stated, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Fairjunglefairjungle.comSee also Transparency alternatives to Fairjungle | 26/100 | 2 Data location stated, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Supertrippersupertripper.comSee also Transparency alternatives to Supertripper | 26/100 | 2 Data location stated, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Itiliteitilite.comSee also Transparency alternatives to Itilite | 22/100 | 2 Public pricing, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Lemaxlemax.netSee also Transparency alternatives to Lemax | 22/100 | 2 Data processing agreement, Notice before subprocessors change | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| TravelBanktravelbank.comSee also Transparency alternatives to TravelBank | 22/100 | 2 Status page with history, Named privacy contact | 1 security.txt (RFC 9116) | 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.