I think what makes at least me nervous is that Zoom has such a long history of lying and it takes time to earn back trust. Proton themselves came out with that 2024 blog post “Open source Zoom alternatives that respect your privacy.”
Obviously, increasing adoption is great and all, but Proton’s whole brand is supposed to be private by default, which Zoom is clearly not.
I can criticize something and still offer users the ability to use it if they want (which most corporations do). Create an alternative that can compete, maybe Proton will add it. I think they talked about Signal links being added someday.
True also a privacy company should make these features opt in and not default.
True, but this type of integration feels more like an endorsement than just “offering the ability to use it.” You could always manually add a Zoom link to calendar events if you wanted to before.
One funny thing about this “integration”, is that it you cant join that Zoom meeting without having a separate Zoom.us / Google / Apple / MS account, all it does is a simple button. 
Zoom is definitely bad, but Proton tries to “Integrate” a service that simply ignored them, is pathetic.
Proton can simply “Integrate” Jitsi / Brave Talk / Element Call which don’t require an account at all, Proton can set one of these as default.
If they want to add other services, fine, then also add Google Meet / MS Teams / Skype / Cisco Webex / Signal Call, these services require an separate account anyway, you can simply “automate” the “integration” process by detecting the URL in description box, then pop that fancy little useless button.
Why Why Why Why Why Why Why Why Why , @Proton_Team ?
Unfortunately, I think Jitsi Meet these days does require an account. But I wish they would have instead hosted Jitsi themselves, enabled E2EE by default, and maybe contributed to the code base to improve it further.
No but they enable the integration by default allowing employees of businesses using Proton to violate GDPR as well as and company policies without the firm noticing. This could be a big compliancy failure. If someone just shares data with Zoom hosted outside the EU and with no data processing agreement this is troublesome.
Please back this up with sources and numbers.
I highly doubt it is that high in EU at least. 90% of the time people use Teams for me. But yeah doesnt matter, this is also not “default” so to say.
If you don’t understand the difference between building a stickers feature or improving a product design, and porting in a privacy invasive product as-is from a third-party company that doesn’t care about security, I’m not sure what to tell you 
Simple guesses, tldr is $
They will not say it’s about money, but it’s about money. Let’s just hope they add secure alternatives.
Funny thing is Unless that’s what was actually changed You can in fact join zoom meetings without an account.
Also @overdrawn98901 has one thing almost right. It’s likely that proton did the market research for businesses to decide on Zoom. And I agree with them that I hope Proton just adds more options like Signal, Jitsi and more.
Feel free to correct me but as far as I know this only applies to the official jit.si, I think other frontends or with self host you can do without an account requirement.
If you don’t understand how enterprise software works, just say so. Companies have locked in contracts and obligation to indulge clients and vendors with convenience. People can’t convert close friends to use encrypted messengers, but expect Proton or other companies to change entire ecosystems at once. Surely Proton should have handicapped their pitch to business users to wait for jitsi or whatever flavor of the month Foss, community funded software to get their stuff together.
Here’s a wikipedia link: Appeal to ridicule - Wikipedia
Next time link an alternative with the scale of adoption Zoom has. Hopefully y’all don’t disintegrate when they integrate software like MS Teams (which is crazy invasive too).
I want a calendly integration next.
As an aside, I one time needed to do video conferencing with someone. They suggested Zoom, I suggested Jitsi, and their reply was “well let’s just meet in person to keep it simpler”. Even the tiniest friction against what everyone else typically uses is enough to block people in their tracks. I’d imagine that the total percentage of people using Jitsi vs Zoom is like the number of people using Internet Explorer vs Chrome, but that is just my opinion.
Calendly has been very useful for my individual business ventures. I wouldn’t mind a Proton integration with that.
They certainly did some research, but Zoom / MS / Google all offer mail and calendar in their ecosystems, I don’t understand what makes Proton to decide to include ONLY Zoom. If there’s a deal between the two companies, then Zoom would also include Proton as one of their “login” options. However, as I captured above, it does not.
More importantly, In Proton’s Proton Mail and Proton Calendar winter product roadmap | Proton, they mentioned
Video conferencing integration
We’re introducing the ability to link video conferencing accounts from external providers to Proton Calendar, so you can create video links for events or join video conferencing calls from within Proton Calendar.
with a “s”.
In Results of the 2024 Proton community survey | Proton , 22% of respondents wanted a Encrypted VC Tool , not 3rd party integration, but anyway.
While Zoom now offers E2EE in their meetings , given their excellent background and track record, I would 100% avoid using their services, just like avoiding Whatsapp. But business is business, so can’t blame them for including Zoom, but including ONLY Zoom and no alternatives (esp. better alternatives exists) is the issue.
Yeah I get it.
More or Less I have this with the uphill battle I have with signal where I tell them to use it but they say “BuT You HaVe ViBeR”
Well here’s a meme for them:
Start small, test out one integration, add more over time. Iterative software development is the norm for most tech companies nowadays. They may patch some bugs for this integration, then move onto the next one. It’s hardly controversial to do 1 integration, then do another following the release and test of that one.
