Transparency alternatives to Super
Other Website builders vendors we measure, sorted by how much we found at them and not at Super. This is a comparison of disclosure, not of features or fitness.
12 shown of 38 that differ from Super on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Super has 9 gaps in what we could measure: Subprocessor list, Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Super” is the one that closes them.
| Vendor | Score | Found there, not found at Super | Found at Super, not found there | |
|---|---|---|---|---|
| Hostingerhostinger.comSee also Transparency alternatives to Hostinger | 65/100 | 6 Data location stated, Status page with history, Certifications named, +3 | 1 HTTPS enforced with HSTS | Compare |
| Glideglideapps.comSee also Transparency alternatives to Glide | 78/100 | 5 Subprocessor list, Data location stated, Status page with history, +2 | nothing | Compare |
| Unbounceunbounce.comSee also Transparency alternatives to Unbounce | 78/100 | 5 Subprocessor list, Data location stated, Status page with history, +2 | nothing | Compare |
| Squarespacesquarespace.comSee also Transparency alternatives to Squarespace | 70/100 | 5 Data location stated, Status page with history, security.txt (RFC 9116), +2 | nothing | Compare |
| Elementor Hostingelementor.comSee also Transparency alternatives to Elementor Hosting | 57/100 | 4 Subprocessor list, Data location stated, Status page with history, +1 | 1 Data processing agreement | Compare |
| Ghostghost.orgSee also Transparency alternatives to Ghost | 57/100 | 3 Data location stated, Uptime SLA with a figure, Notice before subprocessors change | nothing | Compare |
| Framerframer.comSee also Transparency alternatives to Framer | 52/100 | 3 Data location stated, Certifications named, security.txt (RFC 9116) | nothing | Compare |
| Umsoumso.comSee also Transparency alternatives to Umso | 48/100 | 3 Data location stated, Notice before subprocessors change, Named privacy contact | 1 Public pricing | Compare |
| Sitejetsitejet.ioSee also Transparency alternatives to Sitejet | 39/100 | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | 1 Data processing agreement | Compare |
| Tildatilda.ccSee also Transparency alternatives to Tilda | 41/100 | 2 Data location stated, Named privacy contact | 1 HTTPS enforced with HSTS | Compare |
| Brizy Cloudbrizy.ioSee also Transparency alternatives to Brizy Cloud | 35/100 | 2 Data location stated, Named privacy contact | 1 Data processing agreement | Compare |
| Typedreamtypedream.comSee also Transparency alternatives to Typedream | 35/100 | 2 Data location stated, Certifications named | 1 Data processing agreement | 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.