Encrypted Handoff
Move conversations between your desktop and mobile devices with end-to-end encryption.
9xchat keeps your chats, memories, and settings stored locally on your device rather than syncing them continuously through a cloud database. When you want to move a conversation to another device — such as taking a desktop chat onto your phone for a commute — you use Handoff.
Handoff connects your two devices directly through an ephemeral, end-to-end encrypted relay. Nothing is stored in the cloud, and the transfer is triggered only when you explicitly request it.
How it works
- You initiate the transfer on your source device (desktop or mobile).
- 9xchat generates a single-use, 6-digit pairing code.
- On the receiving device, select Handoff and enter the 6-digit code.
- The two devices establish an encrypted peer session over
handoff.123sudo.com. - The conversation payload is encrypted on the sender, transmitted through the relay, decrypted on the receiver, and saved to local storage.
- The pairing session terminates immediately once the transfer completes.
Handoff is point-to-point and temporary. The relay server introduces the two devices and passes the encrypted payload, but cannot decrypt or inspect what passes through it. Once the transfer finishes, the room expires.
Moving a chat from desktop to mobile
- Open the conversation you want to transfer on your desktop.
- Select the Share / Handoff icon in the chat toolbar.
- Choose Handoff to Device to generate your 6-digit code.
- Open 9xchat on your phone (Android or iOS).
- Tap Handoff in the menu and enter the 6 digits shown on your desktop.
- The conversation appears immediately on your phone, complete with its message history and context.
Moving a chat from mobile to desktop
The process works identically in reverse:
- In the mobile chat, tap the menu and select Handoff.
- Note the generated 6-digit code.
- On your desktop app, open Handoff and input the code.
- The chat is imported into your desktop workspace.
What is transferred vs. what stays local
| Item | Transferred via Handoff? | Notes |
|---|---|---|
| Active conversation history | Yes | Full message thread, citations, and metadata |
| Per-conversation context | Yes | System instructions and parameters set for that chat |
| Persistent memories | No | Memories remain in the local database of the device where they were created |
| Knowledge Base collections | No | Indexing and local source files remain on the originating machine |
| API keys and secrets | No | Kept in local secure storage per device |
Because memories and knowledge files remain local to each device, handing off a conversation transfers the conversation history itself. The receiving device will continue the chat using its own configured models and local settings.
Security and privacy
- End-to-end encrypted: The payload is encrypted by the sending device before leaving your network and decrypted only on the receiving device.
- Zero persistence: No conversation data is written to disk or stored on any intermediate server.
- Rate-limited protection: Pairing codes are protected against brute-force attempts with edge rate limiting.
- Short-lived sessions: Pairing rooms expire automatically within minutes if not claimed.