Dicey Table
Docs
Search the docs

Stay in control

AI agent privacy: what leaves your computer

On a direct connection, an agent's tool traffic stays on your computer. DiceyTable records that a session ran, but never what the agent read or sent.

4 min readVerified

View as Markdown
On this page8 sections

On a direct connection, the agent's tool traffic stays on your computer, between the bridge and your browser tab. DiceyTable's server records that a session ran and how busy it was, but never what the agent read or sent.

Two things can change that picture: the relay, and URL imports. Both are covered below, along with what your own AI client does with what the agent sees.

The direct path stays on your computer#

The bridge listens only on your own computer, at the address 127.0.0.1. Your tab connects to it there. Screenshots, table views and tool results travel between the two without leaving your machine. How the bridge works shows the parts in more detail.

Where agent traffic goes Tool calls and results travel between the bridge and your tab on your computer. Only when the direct path is blocked do they pass through DiceyTable's relay, which stores and logs no message. Tool results also go to your AI client, which usually sends them on to its AI service. Your computer AI clientClaude Code, Cursor… bridgeruns on your computer stdio your tabdiceytable.com 127.0.0.1 :47621–47625 direct: stays on your computer relayDiceyTable serverapi.diceytable.com/agent-relay fallback AI service your AI provider's terms tool results and screenshots go to your AI client Relay: passes messages, never stores or logs one. DiceyTable's server records that a session ran and how busy it was, never what the agent read or sent.
Where your data goes. The direct path never leaves your computer; the relay is only the fallback.

What the agent changes is saved and shared the same way your own clicks are. An edit in the editor is saved to your project. A move at a table is sent to the host, like any move you make.

Your AI client sees what the agent sees#

Everything a tool returns goes to your AI client, like Claude Code or Cursor. Most clients send it on to an AI service to decide what to do next. That includes screenshots, card text and your project's details. What happens there is up to your AI provider's terms, not ours. Check your client's privacy settings if this matters for your project.

What does DiceyTable's server record?#

Our server keeps a short record of each agent session, so you can review it in Settings ▸ AI agents. The record holds:

  • the client's name and version, and the bridge's version;
  • how it connected: direct, through the relay, or as an in-browser agent;
  • which key it used, and that key's permissions;
  • when it started and ended, and why it ended;
  • how many tool calls and screenshots it made;
  • for each tab it worked in, the kind of page (editor, preview, table, lobby) and the project or room.

It never holds the arguments of a call, its results, a screenshot or any file. For each key, the server keeps a hash, which is a fingerprint that can check a key but can't be turned back into it. It also keeps when the key was last used, and by which client.

What changes when the relay is used?#

Sometimes your browser can't reach 127.0.0.1, for example in Safari, or when local network access is blocked. Then tool traffic goes through DiceyTable's relay instead. The relay is a server that passes messages between your bridge and your tab.

The relay only lets both ends connect if they are the same person: the bridge with your key, the tab with your sign-in. It looks at each message only for its size and version. It never stores a message, and it never logs one.

But on the relay, screenshots, table views and imported files do pass through our servers on their way. The consent dialog and the agent chip both say when the relay is in use. To turn it off, start the bridge with --no-relay. Then the tab must reach the bridge directly, so Safari can't pair. Allow local network access explains how to get the direct path back.

URL imports#

When an agent imports a file from a web address, DiceyTable's server downloads it and streams it back through the bridge to your tab. The file is never stored on our side. Every attempt, refused ones included, is recorded without its contents: the address, the final address after redirects, the status, the size, the file type, the outcome and how long it took.

You can read the list under Settings ▸ AI agents ▸ URL imports. Each entry is kept for 90 days. How URL imports are fetched safely covers the rules.

What stays in your tab and on your computer#

  • Activity… in the agent chip lists each call this tab answered. It keeps the names of the arguments, never their values. See watch, pause or stop your agent.
  • The bridge saves your key in a credentials file in your user profile. It writes no other files, except the ones you ask it to save with saveTo.
  • The bridge's log goes to your AI client, never to us. It replaces your key, and anything shaped like a key, with a placeholder before writing a line.

What other players see#

Other players don't see what your agent does. They do see an AI badge next to your name while it's connected. See the AI badge other players see.

Did this page answer your question?