All commitments

Commitment

Peer-to-Peer Privacy

Mobile Scout and team Enclave traffic is built to stay between hardware you own — not a Recursion hop that reads the payload.

How it works today

How “sync” usually works

A phone app that talks to a desktop agent almost always means a hosted relay. Your messages hit a vendor server, wait in a queue, and get forwarded. The vendor can read, store, or inspect the payload even if the UI says end-to-end.

Team products do the same with a public endpoint: members reach a cloud workspace, and the vendor's network is the path. Convenient. Also a copy in transit that is not yours.

If the product needs your data to “pass through us to work,” you do not have a private path. You have a middlebox.

Data path — today

Your phoneRelay appVendor relayYour MacAfter they copied it

Phone traffic goes to a vendor relay, then to your Mac — the middlebox sees the payload.

How Recursion does it

Device-to-device, not Recursion-to-device

Courier Relay — the mobile companion that connects to Scout running on your Mac — is set up with peer-to-peer connections so traffic does not pass through Recursion servers.

Enclave's mesh is the team version of the same idea: members reach the Hub over an encrypted link on your own network. LAN-first. No public endpoint for the outside world to knock on.

A remote Enclave relay is on the way so teams can connect from home or a client site. Connections are peer-to-peer wherever possible; even the fallback only forwards encrypted traffic it cannot read.

Data path — Recursion

Your phoneCourier RelayYour MacScoutCloud

Phone and Mac connect peer-to-peer. The cloud is not on the path.

Relay

  • Courier Relay is a mobile companion to Scout on your Mac — not a Recursion-hosted chat backend.
  • The intended data path is peer-to-peer between devices you control.
  • Relay does not yet have a public marketing landing page; this policy is the public description.

Enclave mesh

  • Members reach the Hub over an encrypted mesh on your network — auto-configured, LAN-first, with no public endpoint.
  • Joining is a single-use invite that carries a pre-authorized key. A member never has to touch network settings.
  • An Enclave-supported relay is coming so the Hub can be reached from any network. Peer-to-peer wherever possible; a fallback relay only forwards ciphertext it cannot read.