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