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