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