Security Guide

Trusted devices and encrypted DMs

CatRealm DMs are end-to-end encrypted. The keys live on your devices, so signing in is not enough to read them: a device has to be trusted first. This page explains why that rule is strict, how the keys work, and what to do if you are locked out.

Locked out right now? Do not uninstall CatRealm, clear its data, or remove this device from your account. Those erase the encryption key on this device, and that key may be your only way back in. Jump to Locked out? Start here.

1. Why trusted devices are strict

On most chat services the server can read your messages, so a new device only needs your password. CatRealm Central stores your DMs in a form it cannot read. That protection only holds if Central also cannot hand a readable copy to a new device on its own.

So a password, a session, or even a request from CatRealm staff does not unlock your DM history. A device earns trust only through something you hold:

The cost of that design is real: if you lose every one of those, nobody can open your old DMs for you. CatRealm cannot reset or bypass it.

2. How the keys work

  1. Each device makes its own key pair. The first time you sign in on a device, the app generates a private key and a public key. The private key stays in that app's storage on that device and is never sent to Central. Only the public key is registered.
  2. Each DM conversation has its own secret key. Messages in that conversation are encrypted with it before they leave your device.
  3. The conversation key is wrapped once per trusted device. A device that holds the conversation key encrypts a copy to each trusted device's public key (X25519 key agreement, then AES-256-GCM). Central stores those wrapped copies and delivers them, but it has no private key that opens them.
  4. Untrusted devices get no copy. A signed-in device that is not trusted can use servers and settings, but encrypted DMs show as locked.

Three consequences follow from this:

3. How a device becomes trusted

Devices protected by a passkey or security key are held to one more rule: they must pass their passkey check at least every 30 days before they can share DM keys with your other devices. If a conversation is waiting on such a device, verify on it, or use Re-trust from another trusted device.

4. Locked out? Start here

Work down this list and use the first path that matches your situation. All of them are under Settings → Account Security → Devices unless noted.

A. You still have another trusted device

Safest option. Use it whenever you can.

Open CatRealm on the trusted device and approve the new one from the prompt, or from the Devices list with your 2FA code. Keep the trusted device online for a moment so it can share your DM keys.

B. You have a passkey or security key on your account

Works with no other device, but the passkey must have been added before you were locked out.

On the locked device, choose Approve with Passkey and complete the passkey check. The device becomes trusted. Conversations unlock as soon as a device holding their keys is online. If none exists any more, continue with path E for each conversation.

Risk: anyone who is signed in to your account and holds your passkey can trust a device this way. Treat a hardware key like a house key, and remove passkeys you no longer control.

C. This device used to be trusted and still has its data

For a device that lost trust but was never wiped, for example after switching accounts.

Enter your 2FA code and choose Verify this device with 2FA. The device proves it still holds the same encryption key Central saw earlier, and trust is restored. If Central reports it has no earlier key copy for this device, use path B or E.

Risk: low. The check fails for a device that never held your keys, so a stolen password and 2FA code alone are not enough here.

D. None of your trusted devices holds DM keys any more

For example, your only trusted device was a private browser window that has since closed.

Sign in on the device you want to keep and complete your 2FA or passkey check. When no trusted device of yours holds any DM key, that device is trusted automatically so your account is never blocked forever.

Risk: in this state your password and second factor are the only things guarding device trust. Earlier conversations stay locked until the other person shares the key again (path E).

E. Ask the other person in the DM

Last resort, one conversation at a time. Use it when no device of yours can open that conversation.

  1. Open the locked DM. Under Request decrypt, verify with your 2FA code or passkey and send the request.
  2. The other person verifies their own identity with 2FA or a passkey on a trusted device that holds the key.
  3. They see a final warning with a 20-second wait, then their device sends your device an encrypted copy of that conversation's key. Central never sees the key.

The request expires after 24 hours and either side can cancel it. If your device still holds the conversation key but lost trust, the DM offers Ask them to verify this DM key instead: both devices prove they hold the same key without sending it anywhere, both accounts confirm with 2FA, and your device is trusted again.

Risk: this is the path an attacker would choose. See the next section before you approve a request from anyone.

F. None of the above

If you have no trusted device, no passkey, no surviving key, and the other person cannot or will not share, that conversation's history cannot be recovered by you, by them, or by CatRealm. You can keep using your account and start fresh on a newly trusted device.

5. Risks you accept when recovering

6. Avoid getting stranded

Back to HomeDocsPrivacy