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