Skip to main content
Rift Rift Beta
Features Compare Plans Download FAQ
  • English
  • Español
  • Português (Brasil)
  • Français
  • Deutsch
  • 日本語
  • 한국어
  • 简体中文
  • 繁體中文
  • Italiano
  • Русский
  • Українська
Open App
Features Compare Plans Download FAQ
  • English
  • Español
  • Português (Brasil)
  • Français
  • Deutsch
  • 日本語
  • 한국어
  • 简体中文
  • 繁體中文
  • Italiano
  • Русский
  • Українська
Open App
★ Chat, voice, and communities, all in one window. ★ Chat, voice, and communities, all in one window. ★

Encryption

Last updated November 2026

How Rift encrypts your DMs and calls.

On this page

  1. What's encrypted
  2. Your keys
  3. Messages
  4. Adding a device
  5. Verifying a contact
  6. Calls
  7. On your device
  8. On our servers
  9. Deleting
  10. Test vectors

DM text and 1:1 calls are end-to-end encrypted, with keys that stay on your devices, so we can't read any of it.

What's encrypted

End-to-end encryption covers the text of your DMs and the voice, video, and screen share in 1:1 calls. Shard and Splinter messages are encrypted on our servers instead, because they go out to lots of people at once and we hold those keys. Files and GIFs you attach aren't end-to-end encrypted, and neither are Shard voice channels.

Your keys

Everything comes from your Rift Key, the 12 words you get at sign-up. The words are a standard BIP-39 mnemonic. Its 128 bits of entropy, followed by the label "rift-identity-v1", are hashed with SHA-256 to make the seed for your Ed25519 account key. Your X25519 DM key is SHA-256 over the account private key followed by the label "rift-dm-e2ee-x25519-v1".

Our servers get the public halves and nothing else. Your account public key is written once, when you register, and we only accept a DM public key that your account key has signed.

These keys don't rotate, which is how a new device can open your whole history. It's also why your Rift Key is the one thing you really need to keep safe, since it opens that history too.

Messages

There's no session to set up. Your app looks up the other person's DM key, checks its signature, and only then encrypts.

The shared secret is X25519 between your DM key and theirs. The message key comes from HKDF-SHA256 over that secret, with a random 16-byte salt and the info "rift-dm-v4|" followed by the sender's and recipient's public keys in hex, in that order, joined by "|". Each direction of a conversation gets its own keys. The message is sealed with AES-256-GCM and a random 12-byte nonce.

The associated data is a JSON object with the version, both public keys, the message id, and the thread. It isn't sent with the message. Each app rebuilds it, which stops a ciphertext from being moved to another conversation, message, or thread.

Everything in the message, formatting included, goes inside the ciphertext. The version, the algorithm name, both public keys, and the salt and nonce travel with it, and the other side runs the same checks before opening anything.

Adding a device

Sign in on a new device with your Rift Key, or approve it from one you're already signed in on:

  1. The new device shows a nine-digit code, which never leaves that screen.
  2. You type it on the device you're signed in on, and the two run CPace, a key exchange keyed by that code (draft-irtf-cfrg-cpace, over ristretto255 with SHA-512).
  3. The signed-in device encrypts your keys under the result (HKDF-SHA256, then AES-256-GCM) and sends them over.

Our server just relays. It never sees the code and can't test guesses against what passes through. Slipping in a key of its own would mean winning a one in 100 million guess, and a wrong guess breaks the pairing right in front of you.

Approval always needs that code. Requests expire after ten minutes, and the server deletes its copy once the new device reads it, or soon after the request ends.

Verifying a contact

The first time you message someone, your app gets their key from our server. To make sure it's really theirs, open Verify encryption in the DM and you'll both see the same 60-digit safety number, built the way Signal builds its own (SHA-512, run 5,200 times, over each account key and user id). Compare it in person or on a call, then mark them verified.

Your app remembers every contact's key, and since keys don't change, the conversation tells you if one ever does. For someone you've verified, messages and calls wait until you've had a look.

Your verifications follow you to your other devices, sealed with AES-256-GCM under a key from your Rift Key. We store that copy but can't read it.

Calls

In a 1:1 call, your device encrypts every audio and video frame, and our media server relays frames it can't decode. The caller makes a random 256-bit key and seals it to the other person's DM key, starting from the same shared secret as messages: HKDF-SHA256 with a random salt and the info "rift-dmcall-keywrap-v1|" followed by both public keys, then AES-256-GCM, bound to the call id. Encryption starts once both sides confirm they have the key.

Encrypted calls keep sending audio even when nobody's talking, so packet timing doesn't give away who is. If the other person's app can't do encrypted calls, you're asked before the call connects, and the call screen says so.

On your device

On web and desktop, your keys are stored in IndexedDB, encrypted under a WebCrypto key that can't be exported. On phones they're in app storage, encrypted under a key held in the iOS Keychain or Android Keystore.

Your Rift Key is only kept on the device if you save it. Sign-up offers an encrypted copy, sealed with AES-256-GCM under a key made from your password: PBKDF2-HMAC-SHA512 at 600,000 iterations on web and desktop, and your password plus a secret that stays in the Keychain or Keystore on phones.

On our servers

For a DM, we store the ciphertext and what it takes to deliver it: who's in the conversation, when each message was sent, how big it is, and its reactions, pins, and read state, but never what it says.

Push notifications for a DM don't include its text. Link previews are fetched through our servers, which keeps your IP address from the site behind the link, and you can turn them off in Settings. If someone in a conversation reports a message, their app sends us what it shows them.

Deleting

Deleting a DM removes it from our database, with no soft delete or shadow copy, and disappearing messages go the same way when their timer runs out. Database backups age out after seven days.

Test vectors

Here are two worked examples to check an implementation against. Values are hex unless they're marked as text.

A message

With no formatting, a message is encrypted as just its text.

sender DM private key               1111111111111111111111111111111111111111111111111111111111111111
recipient DM private key            2222222222222222222222222222222222222222222222222222222222222222
sender DM public key                7b4e909bbe7ffe44c465a220037d608ee35897d31ef972f07f74892cb0f73f13
recipient DM public key             0faa684ed28867b97f4a6a2dee5df8ce974e76b7018e3f22a1c4cf2678570f20
X25519 shared secret                9e004098efc091d4ec2663b4e9f5cfd4d7064571690b4bea97ab146ab9f35056
salt                                33333333333333333333333333333333
nonce                               444444444444444444444444
message id (text)                   0f1e2d3c-4b5a-4978-8695-a4b3c2d1e0f9
thread                              none
HKDF info (text)                    rift-dm-v4|7b4e909bbe7ffe44c465a220037d608ee35897d31ef972f07f74892cb0f73f13|0faa684ed28867b97f4a6a2dee5df8ce974e76b7018e3f22a1c4cf2678570f20
message key                         ad38ea32e3031e25640b42632275e6f6e948676de386d0ce503261ec30c76f57
associated data (text)              {"v":4,"s":"7b4e909bbe7ffe44c465a220037d608ee35897d31ef972f07f74892cb0f73f13","r":"0faa684ed28867b97f4a6a2dee5df8ce974e76b7018e3f22a1c4cf2678570f20","cid":"0f1e2d3c-4b5a-4978-8695-a4b3c2d1e0f9","tid":null}
plaintext (text)                    hello
ciphertext and tag                  eeb5cbc123e937885b6d0248511c455a2599ee2490
"nonce" on the wire                 MzMzMzMzMzMzMzMzMzMzMw==.RERERERERERERERE
"ciphertext" on the wire            7rXLwSPpN4hbbQJIURxFWiWZ7iSQ

Adding a device

The two devices run CPace from draft-irtf-cfrg-cpace, for ristretto255 with SHA-512, using the nine digits as text for the password, "rift-device-pairing-v2" for the channel identifier, and an empty session id. The new device goes first as the initiator, with associated data "new-device", and the approving device answers as the responder, with "approver". HKDF-SHA256 turns the 64-byte CPace session key into the bundle key, with no salt and the info "rift-pairing-bundle-v2", and the bundle is sealed with AES-256-GCM, using "rift-pairing-bundle-v2|" followed by the request id in lowercase as associated data.

code on the new device (text)       583465893
new device scalar (little-endian)   5402d700f2f01a5c1a0a5eb07d977a1265cbb53b303a10425f00ae1f47ef1e0e
new device share                    ba33d2d13a2849271150b9022a01acd02c60800852f93a694b012aef099ae550
approving device share              0c1510bd818aee9b72c9323a35d7fc60f4748d575eb7e5a36ff93fdbd0565276
shared point                        fca018e52c1faff23d5b52550023e1f10b2fd05e2206e986c4f0735bf56af356
CPace session key (ISK)             abdd4024f2b148143ce78d8446820850ae015a645848c933d2a1ebb249e13506efacc0b45bf88aad6e71656d197dca74f877a1409aa2ecc4628495e1d2b15f13
bundle key                          f49771f7584e545a65e4aaa99a3caeeefeb8b237e1d4e516ea80b5babb2c46ae
request id (text)                   3f2b9c1e-7a54-4d0a-9b1c-5e6f7a8b9c0d
associated data (text)              rift-pairing-bundle-v2|3f2b9c1e-7a54-4d0a-9b1c-5e6f7a8b9c0d
nonce                               27ededf203af3bea32b6fabc
ciphertext and tag                  da975cdc44ab5145f245638b6e45c3850eea21643fac8005cd38ac3849550b7935635d540ec1
plaintext (text)                    {"v":1,"hello":"rift"}

If our code ever disagrees with this page, that's a bug, and we'd like to hear about it. Tell us here.

800×600 HTML 3.2 RIFT
Rift Rift

Chat, voice, and communities, all in one window.

Product

  • Features
  • Rift vs Discord
  • Plans
  • Download
  • FAQ
  • Support
  • Status

Company

  • About
  • Transparency
  • Warrant Canary
  • Security
  • Encryption

Legal

  • Privacy Policy
  • Terms of Service
  • DMCA

© 2026 Rift Communications LLC. All rights reserved.

A grown-up lounge for mature conversation. No algorithms, no ads, no surveillance.