Transparency alternatives to Winshuttle
Other Product information management vendors we measure, sorted by how much we found at them and not at Winshuttle. This is a comparison of disclosure, not of features or fitness.
12 shown of 37 that differ from Winshuttle on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Winshuttle has 11 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, HTTPS enforced with HSTS, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Winshuttle” is the one that closes them.
| Vendor | Score | Found there, not found at Winshuttle | Found at Winshuttle, not found there | |
|---|---|---|---|---|
| Sodasoda.ioSee also Transparency alternatives to Soda | 65/100 | 7 Data processing agreement, Data location stated, Status page with history, +4 | nothing | Compare |
| Siffletsiffletdata.comSee also Transparency alternatives to Sifflet | 52/100 | 6 Data processing agreement, Data location stated, Public pricing, +3 | nothing | Compare |
| Alationalation.comSee also Transparency alternatives to Alation | 39/100 | 5 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +2 | nothing | Compare |
| data.worlddata.worldSee also Transparency alternatives to data.world | 39/100 | 5 Data location stated, Status page with history, Certifications named, +2 | nothing | Compare |
| Reltioreltio.comSee also Transparency alternatives to Reltio | 39/100 | 5 Data location stated, Status page with history, Certifications named, +2 | nothing | Compare |
| Ataccamaataccama.comSee also Transparency alternatives to Ataccama | 30/100 | 5 Public pricing, Certifications named, HTTPS enforced with HSTS, +2 | nothing | Compare |
| Plytixplytix.comSee also Transparency alternatives to Plytix | 30/100 | 4 Data location stated, Public pricing, Certifications named, +1 | nothing | Compare |
| Profiseeprofisee.comSee also Transparency alternatives to Profisee | 30/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Tamrtamr.comSee also Transparency alternatives to Tamr | 30/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Fozzelsfozzels.comSee also Transparency alternatives to Fozzels | 26/100 | 4 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | nothing | Compare |
| Akeneoakeneo.comSee also Transparency alternatives to Akeneo | 22/100 | 4 Status page with history, Certifications named, security.txt (RFC 9116), +1 | nothing | Compare |
| Castorcastordoc.comSee also Transparency alternatives to Castor | 30/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | nothing | 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.