For Privacy-Conscious Users

We are technically incapable of reading your messages.

MLS Protocol (RFC 9420) encrypts every message client-side. Your keys never leave your device. Even your file attachments are AES-GCM encrypted before upload.

Messages and files — both encrypted

It's not just your messages. Every file attachment uses AES-GCM encryption with per-user keys before it ever leaves your device. Our storage layer holds ciphertext. We have no key to open it.

No phone number, real name, or ID

Sign up with an email address. That's it. No phone number, no government ID, no biometric scan, no real name requirement. We don't verify your identity because we don't need to.

The encryption layer is public — go check it

The enclave-mls-sdk is open source on GitHub. MLS group key negotiation, client-side key generation, message encryption and decryption — all readable. Don't trust our claims. Read the code.

Multi-account support for compartmentalization

Enclave Social lets you save and switch between multiple accounts in the same app. Keep your communities, identities, and contexts separate without juggling different installs or browsers.

Proof

See it for yourself.

We sent a message and opened the database while it was in transit. The ciphertext column is what gets stored — Enclave Social cannot read your messages even if ordered to.

Verify it yourself. Then invite someone.

Join Enclave Social