What leaves your machine when you run DevThrottle
Before you let a tool watch your coding agents, you should know what it sends off your machine. Your agents read your source code. Anything that sits beside them can see what they see. "We take privacy seriously" does not answer that. A list does.
So here is the list for DevThrottle, as it stands, including the part that changed.
No usage telemetry
DevThrottle used to count which features you used and send anonymous events home. That was removed from the product in July 2026, and nothing replaced it. There is no consent screen at first launch, no telemetry page, and nothing on your machine queues events to send.
If a machine still carries leftovers from the old program - its settings, queued event files, a consent cache - they are deleted the next time the Director or the Gateway starts. They are deleted where they sit. Nothing reads them first, and nothing sends them anywhere.
What does leave: your sessions, to your Gateway
The Director, which runs your agents on your machine, reports to a Gateway. That is how your phone and a browser can show you a session that is running on a desk somewhere else. Three kinds of thing go up:
- Session state. A session started, needs you, finished, was snoozed.
- The conversation. Each finished turn: who spoke, the message text, the agent's thinking, the tool calls with their input, and the tool results. When an agent reads or writes a file, what it read or wrote is inside those tool results. Each batch is labelled with the transcript it came from, which for an agent that keeps its transcript on disk includes that file's path.
- Fleet metadata. Which repositories the machine has and the state of each one's branch; the agent accounts the machine is signed in to and how much of each one's usage limits it has used; and the errors the Director logs. An error report does not carry your prompts, terminal content or files. While you watch a session from a browser or your phone, its terminal output is relayed through the Gateway.
The Gateway keeps a session's conversation for 90 days, then sweeps it, whole sessions at a time.
That second item is the change. An earlier version of our docs said DevThrottle never sends your prompts or your agent conversations. That sentence was written about the telemetry program, and it is not true of the conversation push, which arrived in v2.0.5. The docs now say so.
Whose Gateway it is is your choice
You pick once, in the first-run wizard, and the card you pick says it in plain words: your agents run on your machines, and fleet metadata and conversation history are stored on the Gateway so remote history and supervision work.
- Hosted. The Gateway is ours. Everything above is stored by DevThrottle, in your account's own partition, on the published retention windows.
- Self-hosted. The Gateway is a machine you own. The same data lands on your own hardware, and the retention window is yours to set.
Two smaller things
- Signing in is recorded. When you sign in, the website records it against your account with where it came from: a browser, or the Director's sign-in handoff. That is the whole record, and there is no switch for it.
- One switch that gates nothing. Your account settings have a Product usage data control, on by default. Today it records your preference and nothing collects on the strength of it. It is kept because the consent is real: if collection ever returns, that switch is what it answers to.
What stays on the machine
Your agents edit the repositories you point them at, in place. Terminal screen recordings are off by default; turned on, they are written to a file in the Director's local data folder on that machine, and removing the session removes them.
What this does not cover
Your coding agents have their own flows. An agent sends code to its own AI service to do its job, and that is between you and that service. Voice features send audio to be transcribed and reply text to be read aloud; those are described where voice is documented.
The full map is on the What leaves your machine page of the docs, and every class of content, where it is stored and for how long, is in the Privacy Policy.