Transparency alternatives to Wireframe.cc
Other Creative review and approval vendors we measure, sorted by how much they publish that Wireframe.cc does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 41 that differ from Wireframe.cc on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Wireframe.cc has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Wireframe.cc does not” is the one that closes them.
| Vendor | Score | Publishes, and Wireframe.cc does not | Wireframe.cc publishes, and they do not | |
|---|---|---|---|---|
| Balsamiqbalsamiq.com | 77/100 | 8 Data processing agreement, Subprocessor list, Status page with history, +5 | 2 Data location stated, No third-party tracking before consent | Compare |
| Marker.iomarker.io | 74/100 | 6 Data processing agreement, Subprocessor list, Certifications named, +3 | 1 No third-party tracking before consent | Compare |
| Sketchsketch.com | 61/100 | 6 Data processing agreement, Subprocessor list, Certifications named, +3 | 2 Data location stated, No third-party tracking before consent | Compare |
| Atarimatarim.io | 48/100 | 5 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +2 | 2 Data location stated, No third-party tracking before consent | Compare |
| Userbackuserback.io | 57/100 | 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| Marvelmarvelapp.com | 48/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| Frame.ioframe.io | 35/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | 2 Data location stated, No third-party tracking before consent | Compare |
| Ziflowziflow.com | 35/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | 2 Data location stated, No third-party tracking before consent | Compare |
| Bugherdbugherd.com | 48/100 | 3 Subprocessor list, Certifications named, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Approval Studioapproval.studio | 39/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | 1 No third-party tracking before consent | Compare |
| Wipsterwipster.io | 30/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 2 Data location stated, No third-party tracking before consent | Compare |
| GoProofgoproof.net | 26/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | 2 Data location stated, 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.