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