> You give 8×8 (and those we work with) a worldwide license to use, host, store, reproduce, modify, create derivative works..., communicate, publish, publicly perform, publicly display, and distribute such content solely for the limited purpose of operating and enabling the Service to work as intended for You and for no other purposes.
IANAL, but it seems like that would include training on your data as long as the model was used as part of their service.
Everyone who operates a video conferencing service will have some sort of clause like this in their ToS. Zoom is being more explicit, which is generally a good thing. If Jitsi wanted to be equally explicit, they could add something clarifying that this does not include training AI models.
As I understand it, it refers to using meet.jitsi.si, not "another service" someone might provide by downloading the Jitsi software and running it on their own server.
Please correct me if I'm wrong since this would give me cause to reconsider running a Jitsi server.
The guys at 8x8 may be well intentioned, but their lawyers have done their best to not give the customer any basis to sue the company in any foreseeable circumstances. That is what company lawyers do, for better or worse.
Regardless, it appears that at present time jitsi is not including AI training in their service, and there is no explicit carve-out in their terms for AI training. However, by article 2 they do have the right to store user content, which might become a problem in the future.
To me (a former corporate lawyer) the "for You" qualifier would limit their ability to use content to train an AI for use by anyone other than "You". Is there an argument? Yes. But by that argument, they would also be allowed to "publicly perform" my videoconf calls for some flimsy reasons that don't directly benefit me.
→ https://apps.apple.com/us/app/jitsi-meet/id1165103905
And Zoom:
→ https://apps.apple.com/us/app/id546505307
Looks like one company likes to gobble data more than the other even if both privacy policies are gobble-open.
They have SFU support as of recently, so it should scale similarly to Jitsi et al.
Basically "if you wanted it you could have asked for it, if you didn't then that is a problem".
You would be well advised to use services where the traffic travels through https on port 443 on the server (because it's been my experience that it tends to get pretty good QOS favorability). My own little rule of thumb: "you can connect to any port you want, so long as it's port 443 https." ;)
Though tls/443 is usually still supported because it's most often allowed by even restrictive firewalls and networks
>...any legal entity or business, such entity or business (collectively, “You” or “Your”)
And I might have a call with any other zoom user, too, potentially, maybe. So really they are doing me a service by using my content all over the place — who knows, it might benefit me at some point!
There's Galene, <https://galene.org>. It's easy to deploy, uses minimal server resources, and the server is pretty solid. The client interface is still a little awkward, though. (Full disclosure, I'm the main author.)