> Additionally, some people have privacy concerns about running their data through anything associated with the big G. It's important to point out that Web RTC

> Additionally, some people have privacy concerns about running their data through anything associated with the big G. It's important to point out that Web RTC is E2E encrypted, so Google never actually sees your data. As long as the server you use for signaling is secure, your TURN server may as well be run by the NSA. Since initial signaling is extremely low-bandwidth compared to the actual call, it's usually fine to handle it in your application directly. THe actual problem with WebRTC is that, in its default setup, every call participant leaks their IP address to everybody else, and you need to upload your data n-1 times for n call participants, making it almost unusable on slow connections. You can mitigate both of these problems with an SFU, essentially a central server that takes in streams from all clients and distributes them further, but then you lose the E2E.