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