MobSessiondocs

Data handling and retention

preview

Exactly what stays on your machine, what is sent to the session backbone, and the retention controls rolling out for teams.

This page is precise on purpose. It describes what stays local, what is transmitted so the session can be shared, and the retention and residency controls we are rolling out.

Preview. Configurable retention, data-residency options, and self-hosting are in early access and rolling out to teams. The behavior described under "What stays local" and "What is sent to the backbone" is how MobSession works today.

What stays on your machine

The agent and your source code stay on the orchestrator's machine. The agent reads and edits files in the working directory locally, runs commands in the local shell, and uses the orchestrator's own Claude subscription. Your repository is not uploaded to MobSession.

What is sent to the session backbone

To make a session shareable in real time, the live session stream is sent to and stored on MobSession's managed backbone so every participant sees the same thing. That stream includes:

  • The prompts people submit.
  • The agent's streamed output text.
  • Tool calls and their results as shown in the transcript.
  • Attribution (display names and colors), reactions, and typing signals.
  • Images pasted into a prompt.

So source files stay local, but anything that appears in the shared session, including code snippets the agent prints, is transmitted to the backbone so the mob can see it. Treat the contents of a session the way you would treat anything you paste into a shared tool.

Retention today

Today, session data is stored on the managed backbone so participants can follow along during the session. We do not sell your data, and we do not use the contents of your sessions to train models.

Controls rolling out for teams

These are in early access:

  • Configurable retention. Set how long session data is kept, and delete sessions on demand.
  • Data residency. Options for where session data is stored.
  • Self-hosting. Run the backbone and web app inside your own environment so session data never leaves it. See Self-hosting MobSession.

If your team has specific data-handling requirements, contact us and we will walk through the options.

Related