Transparency alternatives to Wireframe.cc
Other Creative review and approval vendors we measure, sorted by how much we found at them and not at Wireframe.cc. 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 “Found there, not found at Wireframe.cc” is the one that closes them.
| Vendor | Score | Found there, not found at Wireframe.cc | Found at Wireframe.cc, not found there | |
|---|---|---|---|---|
| Balsamiqbalsamiq.comSee also Transparency alternatives to Balsamiq | 91/100 | 8 Data processing agreement, Subprocessor list, Status page with history, +5 | 1 No third-party tracking before consent | Compare |
| Marker.iomarker.ioSee also Transparency alternatives to Marker.io | 74/100 | 6 Data processing agreement, Subprocessor list, Certifications named, +3 | 1 No third-party tracking before consent | Compare |
| Sketchsketch.comSee also Transparency alternatives to Sketch | 74/100 | 6 Data processing agreement, Subprocessor list, Certifications named, +3 | 1 No third-party tracking before consent | Compare |
| Atarimatarim.ioSee also Transparency alternatives to Atarim | 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.ioSee also Transparency alternatives to Userback | 57/100 | 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| Pastelusepastel.comSee also Transparency alternatives to Pastel | 52/100 | 4 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +1 | 2 Data location stated, No third-party tracking before consent | Compare |
| Marvelmarvelapp.comSee also Transparency alternatives to Marvel | 48/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| Ziflowziflow.comSee also Transparency alternatives to Ziflow | 48/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| Frame.ioframe.ioSee also Transparency alternatives to Frame.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 |
| Bugherdbugherd.comSee also Transparency alternatives to Bugherd | 48/100 | 3 Subprocessor list, Certifications named, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Approval Studioapproval.studioSee also Transparency alternatives to Approval Studio | 39/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | 1 No third-party tracking before consent | Compare |
| Wipsterwipster.ioSee also Transparency alternatives to Wipster | 30/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 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.