Transparency alternatives to MegaMeeting
Other Video conferencing vendors we measure, sorted by how much they publish that MegaMeeting does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 23 that differ from MegaMeeting on at least one criterion we measured for both. Public transparency score, not a product or security rating.
MegaMeeting has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and MegaMeeting does not” is the one that closes them.
| Vendor | Score | Publishes, and MegaMeeting does not | MegaMeeting publishes, and they do not | |
|---|---|---|---|---|
| Pexippexip.com | 52/100 | 6 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +3 | 1 Public pricing | Compare |
| Dialpaddialpad.com | 48/100 | 5 Data location stated, Status page with history, HTTPS enforced with HSTS, +2 | 1 Public pricing | Compare |
| Livestormlivestorm.co | 48/100 | 5 Data location stated, Status page with history, HTTPS enforced with HSTS, +2 | 1 Certifications named | Compare |
| TeamViewer Meetingteamviewer.com | 43/100 | 5 Data location stated, Status page with history, HTTPS enforced with HSTS, +2 | 1 Public pricing | Compare |
| Dailydaily.co | 48/100 | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | 1 Public pricing | Compare |
| Demiodemio.com | 43/100 | 4 Subprocessor list, Status page with history, HTTPS enforced with HSTS, +1 | 1 Certifications named | Compare |
| Wirewire.com | 39/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 Certifications named | Compare |
| Alfaviewalfaview.com | 35/100 | 4 Status page with history, No third-party tracking before consent, security.txt (RFC 9116), +1 | 1 Certifications named | Compare |
| Elementelement.io | 35/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | 2 Public pricing, Certifications named | Compare |
| Sherpanysherpany.com | 30/100 | 4 Data location stated, Status page with history, security.txt (RFC 9116), +1 | 2 Public pricing, Certifications named | Compare |
| Zoomzoom.com | 43/100 | 3 Subprocessor list, Status page with history, HTTPS enforced with HSTS | nothing | Compare |
| Wherebywhereby.com | 32/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 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.