Transparency alternatives to Jumpseller
Other Ecommerce platforms vendors we measure, sorted by how much they publish that Jumpseller does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from Jumpseller on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Jumpseller 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 “publishes and Jumpseller does not” is the one that closes them.
| Vendor | Score | Publishes, and Jumpseller does not | Jumpseller publishes, and they do not | |
|---|---|---|---|---|
| Saleorsaleor.io | 74/100 | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | 1 security.txt (RFC 9116) | Compare |
| Lightspeedlightspeedhq.com | 70/100 | 7 Data processing agreement, Subprocessor list, Status page with history, +4 | 1 security.txt (RFC 9116) | Compare |
| Shopifyshopify.com | 70/100 | 7 Data processing agreement, Status page with history, Public pricing, +4 | nothing | Compare |
| commercetoolscommercetools.com | 52/100 | 5 Data processing agreement, Subprocessor list, Certifications named, +2 | 1 security.txt (RFC 9116) | Compare |
| Gumroadgumroad.com | 52/100 | 4 Data processing agreement, Data location stated, Public pricing, +1 | 1 security.txt (RFC 9116) | Compare |
| Swellswell.is | 52/100 | 4 Data processing agreement, Status page with history, Public pricing, +1 | nothing | Compare |
| Ecwidecwid.com | 36/100 | 4 Status page with history, Public pricing, Certifications named, +1 | nothing | Compare |
| BigCommercebigcommerce.com | 35/100 | 4 Status page with history, Public pricing, Certifications named, +1 | 1 security.txt (RFC 9116) | Compare |
| Volusionvolusion.com | 35/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Shoplazzashoplazza.com | 38/100 | 3 Data location stated, Public pricing, Certifications named | 1 security.txt (RFC 9116) | Compare |
| ChannelEnginechannelengine.com | 30/100 | 3 Status page with history, Public pricing, Certifications named | 1 security.txt (RFC 9116) | Compare |
| WooCommercewoocommerce.com | 33/100 | 2 Data location stated, Public pricing | 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.