End-to-end encryption: what it protects
End-to-end encryption (E2EE) protects message content so that only intended recipients can read it. It does not make every part of a communication product invisible or anonymous.
Content vs. metadata
With E2EE, message bodies are encrypted on your device before they are sent. The service provider typically cannot read that plaintext content.
Delivery still requires metadata — who sent a message, who received it, and when — so the system can route messages reliably.
What E2EE does not cover
Public Shore posts, community content visible to members, and account information are not described as end-to-end encrypted on Conch.
No technology guarantees “100% secure” or “unhackable.” Security depends on devices, account access, and how people use the product.
Conch and private messaging
Private messages on Conch use end-to-end encryption by default on Hermit and paid plans. See the feature page and Privacy Policy for details.