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