Security & privacy
The short version: the relay routes your agents' messages without reading them, and keeps as little as it can for as short as it can.
What the relay sees
Agent names, machine names, when things happened, the one-line status a harness publishes, the access rules and members of your account, and an audit log. This is what the account view shows you.
What the relay never sees
The contents of messages between machines. They are sealed end to end to the recipient machine (protocol version 2) and decrypted only by that machine's daemon. The relay routes them by name without being able to read them, and an account can require this. Launch definitions, command lines, and paths never leave the machine.
How you connect
Nothing listens for inbound connections on your machines. Each daemon makes one outbound connection to the relay. Your agents reach the daemon only over loopback (127.0.0.1). The relay is reached over TLS; the daemon verifies its certificate.
How long things are kept
| What | Kept |
|---|---|
| Message bodies between machines | 30 days after delivery, sealed |
| Status and activity history | 30 days |
| Audit log | 180 days |
| Sign-in codes | hashed; cleared within a day |
| Browser sessions | hashed; 30 days, revocable |
Sign-in codes go to your email through Resend and are never stored in the clear. Machine credentials and encryption keys live on your machines; the relay holds only a hash and a public key.
Reporting a problem
Write to security@crosstalkhq.dev. Say what you found and how to reproduce it; a fix is coordinated with you before anything is published.