Transparency alternatives to Dise
Other Digital signage vendors we measure, sorted by how much we found at them and not at Dise. This is a comparison of disclosure, not of features or fitness.
12 shown of 54 that differ from Dise on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Dise has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, 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 Dise” is the one that closes them.
| Vendor | Score | Found there, not found at Dise | Found at Dise, not found there | |
|---|---|---|---|---|
| Yodeckyodeck.comSee also Transparency alternatives to Yodeck | 65/100 | 5 Subprocessor list, Status page with history, Public pricing, +2 | 2 Certifications named, security.txt (RFC 9116) | Compare |
| ScreenCloudscreencloud.comSee also Transparency alternatives to ScreenCloud | 57/100 | 5 Data processing agreement, Status page with history, Public pricing, +2 | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Appspaceappspace.comSee also Transparency alternatives to Appspace | 52/100 | 5 Data processing agreement, Status page with history, Public pricing, +2 | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Pickcelpickcel.comSee also Transparency alternatives to Pickcel | 48/100 | 4 Subprocessor list, Public pricing, Notice before subprocessors change, +1 | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Poppulopoppulo.comSee also Transparency alternatives to Poppulo | 48/100 | 4 Subprocessor list, Status page with history, Notice before subprocessors change, +1 | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Broadsignbroadsign.comSee also Transparency alternatives to Broadsign | 43/100 | 4 Data processing agreement, Status page with history, Notice before subprocessors change, +1 | 3 Data location stated, Certifications named, security.txt (RFC 9116) | Compare |
| Onsignonsign.tvSee also Transparency alternatives to Onsign | 35/100 | 3 Status page with history, Public pricing, Uptime SLA with a figure | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Rocket Alumnirocketalumnisolutions.comSee also Transparency alternatives to Rocket Alumni | 48/100 | 2 Data processing agreement, Public pricing | 1 security.txt (RFC 9116) | Compare |
| Xiboxibo.org.ukSee also Transparency alternatives to Xibo | 48/100 | 2 Data processing agreement, Notice before subprocessors change | 1 Certifications named | Compare |
| Play Digital Signageplaysignage.comSee also Transparency alternatives to Play Digital Signage | 43/100 | 2 Public pricing, No third-party tracking before consent | 1 Certifications named | Compare |
| Carouselcarouselsignage.comSee also Transparency alternatives to Carousel | 39/100 | 2 Data processing agreement, Named privacy contact | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Navorinavori.comSee also Transparency alternatives to Navori | 39/100 | 2 Public pricing, Named privacy contact | 1 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.