3 ms·

I tried that. The lack of mentioning voice data in their privacy page is disturbing. Except one mention: >Developers: Developers using our SDK or API will hav

by gsich 8y ago

I tried that. The lack of mentioning voice data in their privacy page is disturbing. Except one mention: >Developers: Developers using our SDK or API will have access to their end users’ information, including message content, message metadata, and voice metadata. Since voice metadata is explicitly mentioned, real voice data must also be stored somewhere. Also, >... your activities within the Services is very vague. The lack of mentioning voice data is probably because of the huge backlash. Wiretapping every user.

vel0city 8y ago
> Since voice metadata is explicitly mentioned, real voice data must also be stored somewhere. That's not necessarily true. "voice metadata" could be things like quality settings, latency history, when you join a voice channel, when you leave a voice channel, etc. It may have a lot of metadata about it without actually storing the audio streams. A phone PBX will have tons of metadata about calls placed through it, but it might not bother recording every call that goes through it.