build

Architecture and privacy

Build stores the account and device records needed to authenticate you, approve a host, and establish a connection. Device records include the host's registered identity and connection status.

Connection diagnostics

The hosted Build service stores content-free transport diagnostics: session, account, and device identifiers; connection timestamps; the current and first carrying path (relay, direct, or TURN); and counters for carrying, TURN, and lost-channel events. These diagnostic rows remain as transport history after the associated account or device is deleted.

Optional browser notifications

If you enable browser push notifications, the hosted Build service stores the browser's push endpoint and its p256dh and auth encryption keys with your account. Unsubscribing removes that endpoint for the signed-in account.

Where agent work runs

Coding agents execute on your paired host. Workspaces, terminals, files, diffs, and Git operations are produced there and sent to the browser over the encrypted application session.

How a browser reaches a host

The app and relay coordinate WebRTC negotiation. A direct connection exposes each peer's IP address to the other. If direct connection is unavailable, Cloudflare TURN may relay DTLS ciphertext and can observe connection metadata such as source IP, timing, and traffic size.

Provider boundary

The hosted Build service does not receive or store your coding-harness credentials. Each harness is installed and authenticated on the host, and its own provider terms and data handling still apply.