Nothing to hand over.

Messages are encrypted on your phone before they leave it, and travel through a relay you or a friend runs. There is no rChat company server holding your account or your chats.

An Android phone showing the same chat: a photo, a voice note and text messages, with Encrypted in the header.
Android
An iPhone showing a chat with a photo, a voice note and text messages. The header says Encrypted.
iOS
what it’s like

Chat the way you already do.

calls

Calls that need nothing but your relay.

  • Voice and video calls are end-to-end encrypted. Your relay can’t hear or see them.
  • There’s no TURN, STUN or other call server run by someone else. The call goes through the relay you already use.
  • Calls use the same HTTPS port as your messages, which helps on networks that block the ports other calling apps use.

It doesn’t hide that a call is happening: the network can see you’re connected to your relay, and your relay can see that a call is running.

On Android now; iPhone later.

how it works

Your phone, your relay, their phone.

Your phone locks every message before it leaves. The relay passes it along without the keys to open it. Only the phone it is meant for can read it.

The relay can see

  • Which accounts are online, when, and from which IP address
  • Which two have a conversation open, while it is open
  • When two people first connect, or after one of them gets a new phone or changes keys: for up to ten minutes, which account is trying to reach which
  • Message sizes in buckets, and timing
  • That a call is happening: roughly when, how long and how much data, whether it has video, and roughly when there’s movement on camera

It never has

  • Message content
  • Your keys
  • Your contact list
Read the full security model →
under the hood

Built from well-studied parts.

your message
  1. Double Ratchet Every message is locked with a new key.
  2. Post-quantum key agreement Recording traffic today won’t let a future quantum computer read it later. Signatures are not post-quantum yet.
  3. Signed keys The relay can’t swap in keys of its own.
  4. TLS 1.3 to the relay No older versions and no plaintext fallback.

The relay’s logs carry no identifiers.

Read the whitepaper →
run your own relay

Run your own relay.

A relay is a small program on a server with a domain name. You or a friend runs it, and everyone you invite connects through it.

You need a small Linux or FreeBSD server and a domain name pointing at it.

Full setup guide →
# 1  a server with a domain pointing at it
# 2  install (checks the download first)
curl -fsSL https://assets.r-chat.net/install.sh | sudo sh
# 3  write the config (see the setup guide), then print your invite QR
sudo -u rchat rchat-server --config /etc/rchat/server.toml --print-invite
comparison

How it compares.

rChat trades a hosted service for one you control. It is younger and smaller, and it does not have everything the large messengers have.

Feature rChat Signal Telegram
Who runs the server You Signal Telegram
End-to-end encrypted by default Yes Yes No (secret chats only)
Run your own server with the official app Yes No No
Contact key verification Safety numbers and QR Safety numbers Secret chats only
about

Who makes rChat.

Get rChat.

Install the app on your phone. Run the relay on a Linux or FreeBSD server.