# What leaves your box

At the end, you know what stays on the machine Loopgate runs on, what reaches Loopgate's servers, and the one switch that sends more.

## At a glance

**Time:** 2 minutes to read.

**You need:**

- Nothing. On a laptop that is not signed in to an org, nothing reaches Loopgate at all.

## Stays on your box

- Your code, the agents' changes and every diff.
- What each agent was told and what it said back.
- The task, in your words.
- Your Claude and ChatGPT sign-ins. The coding tool keeps them; Loopgate never reads them.
- Your GitHub token and your Slack app's tokens.

## Reaches Loopgate

- **A heartbeat**, once a minute from a runner: its address and its version.
- **Requests for your team's member list, its policy and its workflows.** The box asks; nothing of yours travels with the request.
- **One record per finished run**: the member who started it, the workflow and its version, the repository's folder name, each step's persona id, harness, model, rounds, time, tokens and cost, each decision's kind, who made it and how long it waited, how the run ended, and the pull request's address when there is one.

Never code, diffs, prompts, transcripts or the task.

## Step summaries

An org can add each step's final message to that record: the portal's **Policies → Audit detail → Metadata and step summaries**. Metadata only is the default. A step's final message can repeat what is in your repository, so turn it on only if your team means to.

## Reaches the services you chose

- Your AI model company gets what the agents send it, as with any coding tool.
- GitHub gets your pushes and pull requests.
- Slack gets the thread's posts.

## Next

- [Words we use](words.md)
- [On your server](server.md)