it seems like a product launching in this space in 2026 should have seamless and default e2ee for everything...

ramraj07 3 hours ago | parent | next [-]

E2ee meaning what? Im assuming for compliance reasons any company needs to be able to access all of their internal chats?

	▲	mbreese 3 hours ago \| parent [-]
		Not the OP, but I’m assuming they meant end-to-end-encryption. The company (customer) would be able to see their chats, but the provider (Dock) would not. I don’t think you’d need to have the encryption on a per-user level, but you could. The main point being that the customer’s chats would only be visible to them, not Dock. It would make some features more difficult though, namely search. I’m not sure it’s entirely required, but I’d expect it as an option in the non-free tiers.

▲

jitl 2 hours ago | parent | prev | next [-]

e2ee makes it hard to do things like “search” which is important for working with teams. For personal messengers usually search is all on device w an encrypted index, once an org grows beyond 50 people that sort of thing breaks down.

▲

yadavrh 3 hours ago | parent | prev [-]

We take security very seriously (encryption in transit + at rest, SOC 2 based infra and GDPR compliance). We considered default E2EE, but currently, it introduces significant friction for features like instant server-side search (our core value prop vs Slack's hidden history) and simple multi-device onboarding without key management headaches. We are exploring E2EE for specific "Secure Channels" as a future feature, but for the general workspace, we prioritize a seamless "it just works" experience with standard high-security industry practices.