Alternatives to Alfaview
Other Video conferencing vendors we measure, sorted by how much they publish that Alfaview does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 20 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 “publishes and Alfaview does not” is the one that closes them.
| Vendor | Score | Publishes, and Alfaview does not | Alfaview publishes, and they do not | |
|---|---|---|---|---|
| Pexippexip.com | 65/100 | 5 Data processing agreement, Data location stated, Certifications named, +2 | 2 Public pricing, No third-party tracking before consent | Compare |
| Dailydaily.co | 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 |
| Dialpaddialpad.com | 55/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Restreamrestream.io | 43/100 | 3 Subprocessor list, Data location stated, HTTPS enforced with HSTS | 4 Status page with history, No third-party tracking before consent, security.txt (RFC 9116), +1 | Compare |
| TeamViewer Meetingteamviewer.com | 43/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 2 Public pricing, No third-party tracking before consent | Compare |
| Zoomzoom.com | 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.com | 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.co | 50/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Demiodemio.com | 43/100 | 2 Subprocessor list, HTTPS enforced with HSTS | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Wirewire.com | 39/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 Status page with history, No third-party tracking before consent | Compare |
| Elementelement.io | 35/100 | 2 Data location stated, HTTPS enforced with HSTS | 3 Public pricing, No third-party tracking before consent, Named privacy contact | Compare |
| Enghouse Videoenghousevideo.com | 26/100 | 2 Data location stated, HTTPS enforced with HSTS | 4 Status page with history, Public pricing, No third-party tracking before consent, +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.