Transparency alternatives to TecAlliance
Other Automotive retail software vendors we measure, sorted by how much we found at them and not at TecAlliance. This is a comparison of disclosure, not of features or fitness.
12 shown of 45 that differ from TecAlliance on at least one criterion we measured for both. Public transparency score, not a product or security rating.
TecAlliance has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at TecAlliance” is the one that closes them.
| Vendor | Score | Found there, not found at TecAlliance | Found at TecAlliance, not found there | |
|---|---|---|---|---|
| Tekiontekion.comSee also Transparency alternatives to Tekion | 39/100 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Autovoltautovolt.ukSee also Transparency alternatives to Autovolt | 36/100 | 3 Data processing agreement, Public pricing, Notice before subprocessors change | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | Compare |
| Infomediainfomedia.com.auSee also Transparency alternatives to Infomedia | 36/100 | 2 Data processing agreement, Notice before subprocessors change | 2 Data location stated, Status page with history | Compare |
| Navigator DMSdmsnavigator.comSee also Transparency alternatives to Navigator DMS | 30/100 | 2 Data processing agreement, Public pricing | 4 Data location stated, Status page with history, security.txt (RFC 9116), +1 | Compare |
| DealersClouddealerscloud.comSee also Transparency alternatives to DealersCloud | 26/100 | 1 Certifications named | 3 Status page with history, security.txt (RFC 9116), Named privacy contact | Compare |
| GDV Dienstleistunggdv-dl.deSee also Transparency alternatives to GDV Dienstleistung | 22/100 | 1 No third-party tracking before consent | 3 Data location stated, Status page with history, security.txt (RFC 9116) | Compare |
| DealerCenterdealercenter.comSee also Transparency alternatives to DealerCenter | 18/100 | 1 Public pricing | 3 Data location stated, Status page with history, Named privacy contact | Compare |
| Alldataalldata.comSee also Transparency alternatives to Alldata | 13/100 | 1 Public pricing | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | Compare |
| Autodataautodata-group.comSee also Transparency alternatives to Autodata | 13/100 | 1 Notice before subprocessors change | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | Compare |
| Frazerfrazer.comSee also Transparency alternatives to Frazer | 13/100 | 1 Public pricing | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | Compare |
| Cars Commercecarscommerce.incSee also Transparency alternatives to Cars Commerce | 9/100 | 1 Certifications named | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | Compare |
| Teknnova AutoViewteknnova.comSee also Transparency alternatives to Teknnova AutoView | 9/100 | 1 No third-party tracking before consent | 5 Data location stated, Status page with history, HTTPS enforced with HSTS, +2 | 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.