Transparency alternatives to saldia
Other Website builders vendors we measure, sorted by how much they publish that saldia does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 37 that differ from saldia on at least one criterion we measured for both. Public transparency score, not a product or security rating.
saldia 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, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and saldia does not” is the one that closes them.
| Vendor | Score | Publishes, and saldia does not | saldia publishes, and they do not | |
|---|---|---|---|---|
| Hostingerhostinger.com | 65/100 | 8 Data processing agreement, Data location stated, Status page with history, +5 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | Compare |
| Glideglideapps.com | 78/100 | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | 1 No third-party tracking before consent | Compare |
| Unbounceunbounce.com | 78/100 | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | 1 No third-party tracking before consent | Compare |
| Squarespacesquarespace.com | 57/100 | 6 Data processing agreement, Status page with history, Public pricing, +3 | 1 No third-party tracking before consent | Compare |
| Ghostghost.org | 57/100 | 5 Data processing agreement, Data location stated, Public pricing, +2 | 1 No third-party tracking before consent | Compare |
| Framerframer.com | 52/100 | 5 Data processing agreement, Data location stated, Public pricing, +2 | 1 No third-party tracking before consent | Compare |
| Umsoumso.com | 48/100 | 4 Data processing agreement, Data location stated, Notice before subprocessors change, +1 | 1 No third-party tracking before consent | Compare |
| Elementor Hostingelementor.com | 43/100 | 4 Subprocessor list, Status page with history, Public pricing, +1 | 1 No third-party tracking before consent | Compare |
| Tildatilda.cc | 41/100 | 4 Data processing agreement, Data location stated, Public pricing, +1 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | Compare |
| Sitejetsitejet.io | 39/100 | 4 Data location stated, Public pricing, security.txt (RFC 9116), +1 | 1 No third-party tracking before consent | Compare |
| Brizy Cloudbrizy.io | 35/100 | 3 Data location stated, Public pricing, Named privacy contact | 1 No third-party tracking before consent | Compare |
| WordPress.comwordpress.com | 35/100 | 3 Data location stated, Public pricing, security.txt (RFC 9116) | 1 No third-party tracking before consent | 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.