Transparency alternatives to Volusion
Other Ecommerce platforms vendors we measure, sorted by how much we found at them and not at Volusion. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from Volusion on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Volusion has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Certifications named, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Volusion” is the one that closes them.
| Vendor | Score | Found there, not found at Volusion | Found at Volusion, not found there | |
|---|---|---|---|---|
| Shopifyshopify.comSee also Transparency alternatives to Shopify | 70/100 | 7 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +4 | 2 Data location stated, Uptime SLA with a figure | Compare |
| Lightspeedlightspeedhq.comSee also Transparency alternatives to Lightspeed | 70/100 | 6 Data processing agreement, Subprocessor list, Certifications named, +3 | 2 Data location stated, Uptime SLA with a figure | Compare |
| commercetoolscommercetools.comSee also Transparency alternatives to commercetools | 52/100 | 6 Data processing agreement, Subprocessor list, Certifications named, +3 | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| Saleorsaleor.ioSee also Transparency alternatives to Saleor | 74/100 | 5 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +2 | 1 Status page with history | Compare |
| Gumroadgumroad.comSee also Transparency alternatives to Gumroad | 52/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Status page with history, Uptime SLA with a figure | Compare |
| Swellswell.isSee also Transparency alternatives to Swell | 52/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 1 Data location stated | Compare |
| Ecwidecwid.comSee also Transparency alternatives to Ecwid | 36/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | 2 Data location stated, Uptime SLA with a figure | Compare |
| BigCommercebigcommerce.comSee also Transparency alternatives to BigCommerce | 35/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | 2 Data location stated, Uptime SLA with a figure | Compare |
| OXID eSalesoxid-esales.comSee also Transparency alternatives to OXID eSales | 26/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 3 Data location stated, Status page with history, Uptime SLA with a figure | Compare |
| VTEXvtex.comSee also Transparency alternatives to VTEX | 17/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| Shoplazzashoplazza.comSee also Transparency alternatives to Shoplazza | 35/100 | 2 Certifications named, HTTPS enforced with HSTS | 2 Status page with history, Uptime SLA with a figure | Compare |
| Vendurevendure.ioSee also Transparency alternatives to Vendure | 35/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 2 Status page with history, Uptime SLA with a figure | 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.