Morse can't read your messages.
In an end-to-end encrypted chat, only the model provider's can decrypt your message. Not Morse, and no one in between.
What happens to your message. Your message stays encrypted from your browser to the model provider's enclave, and Morse can't read it on the way.
- Your browserChecks both enclaves, then encrypts your message
- MorseForwards your message, unable to read itRelay and enclave on AWS Nitro
- The model provider's enclaveRuns the AI model in memory even the provider can't readIntel TDX or AMD SEV-SNP, with NVIDIA GPUs
Your browser checks both enclaves. To encrypt your message, your browser needs the of Morse's and the model provider's enclave. Each key comes in an , signed by the hardware, proving the key belongs to a genuine enclave running the expected software.
, or ,Your browser encrypts your message twice. Morse needs a few details to route and bill your message, like the model you picked, but must never read the message. So the outer layer, for Morse's enclave, holds those details, and the inner layer, for the model provider's enclave, holds your message.
and , thenMorse forwards your message. Morse's passes the encrypted message to Morse's enclave, which decrypts the outer layer with its , reads the routing details, and forwards your still-encrypted message to the model provider's enclave. You can verify the enclave's code.
Relay and enclave onThe AI model replies. The model provider's enclave decrypts your message with its own private key, the AI model replies, and the enclave encrypts the reply for your browser alone.
Your browser decrypts the reply. The reply comes back through Morse, still encrypted. Your browser decrypts the reply and saves the chat on your device, encrypted.
Encrypted on your device. Only your device can decrypt your chats, and only while you're signed in: decrypting takes your browser's key and Morse's together.
Neither works alone
Your browser's key
Decrypts the data key, with the key Morse keeps. Made in your browser, and no one can copy it out.
256-bit, non-extractableThe key Morse keeps
Decrypts the data key, with your browser's key. Your browser holds it only in memory, while Morse is open.
32 bytes
Together, they decrypt the data key
The data key
Encrypts every message and file on your device. A random , cleared when you sign out.
,Each message, encrypted separately
Each message and file gets its own encryption with the data key, whatever the model.
What Morse stores, and what Morse never sees. Only what Morse needs to run your account.
- Your account
- Your email and sign-in details, so you can sign in
- Billing
- Your plan, your balance, and how much you've used
- Abuse checks
- A of your IP address, to stop spam
- One of your two keys
- Useless without your browser's key
- Your messages
- in your browser, so Morse can't read them
- Your chats
- Kept only on your devices, encrypted
- Chats you send to another device
- Encrypted end to end on the way, so only your devices can decrypt the chats
- Logs of your chats
- Morse's servers keep none