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.
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:
- a device of yours that is already trusted,
- a passkey or security key registered to your account, or
- your 2FA code together with an encryption key the device already had.
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
- 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.
- Each DM conversation has its own secret key. Messages in that conversation are encrypted with it before they leave your device.
- 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.
- 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:
- A device's key cannot be swapped out. A device that shows up with a different key is treated as a new device and must be approved again.
- Becoming trusted does not instantly unlock history. A newly trusted device can read a conversation once a device that already holds that conversation's key comes online and shares a wrapped copy. This normally happens automatically within moments.
- Anything that wipes the app's storage wipes the private key: uninstalling, clearing site data, signing in from a private or incognito window, or removing the device from your account.
3. How a device becomes trusted
- Your first device is trusted when you register it, because there is nothing to protect yet.
- Every later device starts untrusted whenever a trusted device of yours already holds DM keys.
- Approve from a trusted device. Your trusted devices get a prompt when a new device asks for approval. Confirm the short code shown on the new device. The code rotates every 60 seconds and the request expires after 5 minutes. You can also approve from Settings → Account Security → Devices.
- Approve with a passkey. On the new device, open Settings → Account Security → Devices and choose Approve with Passkey.
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.
- Open the locked DM. Under Request decrypt, verify with your 2FA code or passkey and send the request.
- The other person verifies their own identity with 2FA or a passkey on a trusted device that holds the key.
- 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
- A recovery request may not come from the person you think. Someone who has taken over a friend's account can ask you for the DM key, and approving gives them the whole conversation history. Before you approve, confirm with the person through a channel you already trust: a call, in person, or a server you share. If anything feels off, cancel.
- Verifying someone's device restores more than one chat. Approving a "verify this DM key" request re-trusts that device for their whole account, so it can then receive their other DM keys too.
- Recovery cannot be undone. Once a key copy is shared, the receiving device can read that conversation. Removing a device later stops future access, but messages it already downloaded cannot be erased remotely.
- Every bypass is also a door. Passkeys, 2FA codes, and backup codes are what make self-recovery possible, so anyone who obtains them gains the same ability. Store backup codes offline and never share a 2FA code with someone who asks for it.
- Wiping a device mid-recovery can make it permanent. Reinstalling, clearing data, or removing the device destroys its private key. Keep the app and its data intact until your DMs are readable again.
- Trusting a device you do not control exposes your DMs. Do not approve a shared or public computer. If you must use one, leave it untrusted and sign out afterwards.
6. Avoid getting stranded
- Keep two trusted devices, for example the desktop app and your phone. Either one can approve a replacement for the other.
- Add a passkey or security key while you still have a trusted device. Passkeys can only be managed from a trusted device, so you cannot add one after you are locked out.
- Save your backup codes somewhere offline so a lost authenticator does not also cost you your 2FA.
- Do not rely on a private or incognito window. Its keys are deleted when the window closes. Use a normal window or the desktop app for a device you want to keep.
- Approve the new device before retiring the old one. When replacing a phone or reinstalling, sign in on the new install and approve it first, then remove the old device.
- Remove devices you have lost. Removing a device needs your 2FA code and a trusted device, and it signs that device out.