Alternatives to ScreenCloud
Other Digital signage vendors we measure, sorted by how much they publish that ScreenCloud does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 25 that differ from ScreenCloud on at least one criterion we measured for both. Public transparency score, not a product or security rating.
ScreenCloud has 6 gaps in what we could measure: Subprocessor list, Data location stated, Status page with history, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “publishes and ScreenCloud does not” is the one that closes them.
| Vendor | Score | Publishes, and ScreenCloud does not | ScreenCloud publishes, and they do not | |
|---|---|---|---|---|
| Poppulopoppulo.com | 61/100 | 4 Subprocessor list, Data location stated, Status page with history, +1 | 3 Data processing agreement, Public pricing, Uptime SLA with a figure | Compare |
| Appspaceappspace.com | 65/100 | 3 Data location stated, Status page with history, Named privacy contact | 1 Notice before subprocessors change | Compare |
| Broadsignbroadsign.com | 57/100 | 3 Data location stated, Status page with history, Named privacy contact | 3 Public pricing, Certifications named, Uptime SLA with a figure | Compare |
| Disedise.com | 39/100 | 3 Data location stated, Status page with history, security.txt (RFC 9116) | 4 Data processing agreement, Public pricing, Uptime SLA with a figure, +1 | Compare |
| Carouselcarouselsignage.com | 39/100 | 2 Data location stated, Named privacy contact | 4 Public pricing, Certifications named, Uptime SLA with a figure, +1 | Compare |
| Navorinavori.com | 39/100 | 2 Data location stated, Named privacy contact | 3 Data processing agreement, Uptime SLA with a figure, Notice before subprocessors change | Compare |
| NoviSignnovisign.com | 35/100 | 2 Data location stated, Named privacy contact | 4 Data processing agreement, Certifications named, Uptime SLA with a figure, +1 | Compare |
| Play Digital Signageplaysignage.com | 26/100 | 2 Data location stated, security.txt (RFC 9116) | 5 Data processing agreement, Certifications named, Uptime SLA with a figure, +2 | Compare |
| Screenlyscreenly.io | 26/100 | 2 Status page with history, security.txt (RFC 9116) | 4 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | Compare |
| viewneoviewneo.com | 26/100 | 2 Data location stated, Named privacy contact | 5 Data processing agreement, Certifications named, Uptime SLA with a figure, +2 | Compare |
| Onsignonsign.tv | 30/100 | 1 Status page with history | 3 Data processing agreement, Certifications named, Notice before subprocessors change | Compare |
| TelemetryTVtelemetrytv.com | 30/100 | 1 Data location stated | 3 Data processing agreement, Public pricing, Notice before subprocessors change | 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.