Transparency alternatives to Demio
Other Video conferencing vendors we measure, sorted by how much we found at them and not at Demio. This is a comparison of disclosure, not of features or fitness.
12 shown of 23 that differ from Demio on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Demio has 7 gaps in what we could measure: Data processing agreement, Data location stated, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at Demio” is the one that closes them.
| Vendor | Score | Found there, not found at Demio | Found at Demio, not found there | |
|---|---|---|---|---|
| Dialpaddialpad.comSee also Transparency alternatives to Dialpad | 57/100 | 4 Data location stated, Certifications named, security.txt (RFC 9116), +1 | 2 Subprocessor list, Named privacy contact | Compare |
| Pexippexip.comSee also Transparency alternatives to Pexip | 52/100 | 4 Data processing agreement, Certifications named, security.txt (RFC 9116), +1 | 2 Subprocessor list, Public pricing | Compare |
| TeamViewer Meetingteamviewer.comSee also Transparency alternatives to TeamViewer Meeting | 43/100 | 3 Data location stated, Certifications named, security.txt (RFC 9116) | 2 Subprocessor list, Public pricing | Compare |
| Dailydaily.coSee also Transparency alternatives to Daily | 48/100 | 2 Data processing agreement, Certifications named | 2 Public pricing, Named privacy contact | Compare |
| Livestormlivestorm.coSee also Transparency alternatives to Livestorm | 48/100 | 2 Data location stated, security.txt (RFC 9116) | 1 Subprocessor list | Compare |
| Wirewire.comSee also Transparency alternatives to Wire | 39/100 | 2 Data location stated, security.txt (RFC 9116) | 2 Subprocessor list, Status page with history | Compare |
| Alfaviewalfaview.comSee also Transparency alternatives to Alfaview | 35/100 | 2 No third-party tracking before consent, security.txt (RFC 9116) | 2 Subprocessor list, HTTPS enforced with HSTS | Compare |
| Elementelement.ioSee also Transparency alternatives to Element | 35/100 | 2 Data location stated, security.txt (RFC 9116) | 3 Subprocessor list, Public pricing, Named privacy contact | Compare |
| Wherebywhereby.comSee also Transparency alternatives to Whereby | 32/100 | 2 Data location stated, Certifications named | 3 Subprocessor list, Status page with history, Public pricing | Compare |
| Sherpanysherpany.comSee also Transparency alternatives to Sherpany | 30/100 | 2 Data location stated, security.txt (RFC 9116) | 3 Subprocessor list, Public pricing, HTTPS enforced with HSTS | Compare |
| Zoomzoom.comSee also Transparency alternatives to Zoom | 43/100 | 1 Certifications named | 1 Named privacy contact | Compare |
| eyesoneyeson.comSee also Transparency alternatives to eyeson | 22/100 | 1 Data location stated | 4 Subprocessor list, Status page with history, Public pricing, +1 | 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.