Chat

Conversations only your team can read.

The same end-to-end encryption that protects iMessage and Signal now protects every word your team writes to each other.

A small team in conversation around a laptop on a coffee table

Private by default

The same encryption that protects iMessage and Signal.

The server cannot read your messages.

Decryption happens on each member's device and only the people in the channel hold the keys, and we do not pretend otherwise.

Every channel, locked to its members

A channel is sealed to the people in it with keys that live on their devices and never on our servers, so spinning up a new private channel takes two clicks.

We move sealed bytes. We don't hold the keys.

Our infrastructure only routes encrypted messages between members and cannot decrypt a single one, because there is no master key, no escrow, and no admin override anywhere in the system.

Built on the same protocol family as Signal

The cryptography is an open IETF standard that has been peer-reviewed and adopted by the messengers people already trust — read the protocol references on our security page.

Threaded replies

A focused thread under any message.

Branch off in one click

Reply in a thread instead of cluttering the channel, and the side conversation gets its own home while the original stays readable.

Each thread has its own life

Membership, read state, and notifications scope to the thread, so you can mute the channel while staying in the threads that matter to you.

Quiet by default

Subscribe to the threads you care about, and the ones you have not joined stay quiet even when the parent channel is on fire.

Reactions, mentions, presence

The everyday chat features — done privately.

The signals you expect from a modern team chat, with as little tracking as the platform can possibly do.

Emoji reactions

React to any message, and in privacy mode the server sees only the count rather than who reacted.

@mentions

Mention a teammate or a thread, and the mention rides inside the encrypted message itself, lands in the right person’s feed, and goes nowhere else.

Per-thread read receipts

Opt in thread by thread with no channel-wide watching, and turning the setting off hides who has read what from everyone, including you.

Typing indicators

Typing indicators appear while you are typing and vanish the moment you stop, never written down and never replayed.

Membership changes mean something

A new member can't read old history. A removed one can't read new history.

Joining and leaving a channel actually mean something.

The keys rotate every time membership changes, so past messages remain readable only by the people who had access at the time, and the teammate who left last quarter cannot read this morning's thread no matter what.

New people start fresh

When someone joins a channel the keys rotate, so the new member can only decrypt messages that arrive after they join.

Removed members stay removed

When someone leaves the channel they lose access from that moment, because future messages are sealed with keys they do not hold.

Yesterday stays yesterday

Even if a key were exposed later, it could not be used to read messages outside its narrow window — the cryptography is structured to make that impossible rather than promised.

Bring your team to chat that nobody else can read.

Privacy is not an upsell but the default, and your first channel goes live in minutes.

FAQ

Frequently asked questions

Can admins read messages?

No — not because we promise, but because the architecture doesn't let them. The keys live on members' devices. An admin can manage who's in a channel; they can't read inside it unless they're already a member.

What happens to message history when someone leaves a channel?

They keep the messages they had access to while they were a member. They can't read anything posted after they left — the keys rotated the moment they were removed.

Can I export my history?

Yes. Full export to JSON or Markdown, run from your device against messages you've already read. Same privacy guarantees, your data, your hands.

Are file attachments encrypted?

Yes. Files use the same locks as the messages they're attached to. We store sealed bytes; only members of the channel can unseal them.