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