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