What DevThrottle reports home

This page answers one question: what leaves the machine you work on, where it goes, and how long it is kept. It is a map, not a guarantee - and it changed in a way worth reading if you knew the old answer.

There is no usage-telemetry program any more

DevThrottle used to count feature use on your machines and send anonymous events home. That was removed from the product in July 2026, and nothing replaced it. There is no consent screen at the Gateway's first launch, there is no Usage Telemetry page in the Cockpit, and nothing on your machine queues events to send.

A machine that still carries the leftovers has them removed the next time the Director or the Gateway starts: the retired settings, the queued event files, the consent cache, and the old raw transcription log. They are deleted where they sit - not read first, and not sent anywhere.

What your Director sends to your Gateway

This is the part that matters now. Your agents run on your machines, and your Director reports to your Gateway as they work:

• Session state and activity - a session started, needs you, finished, was snoozed.
• The conversation itself. Since v2.0.5 your Director pushes each finished turn up to your Gateway, and the Gateway keeps it. That is how Chat, the transcript view and the wingman can show you a session from your phone or a browser without your machine being asked to re-read anything.

A pushed turn is the message as it was written: 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 parts. Each batch is also labelled with the transcript it came from, which for Claude Code is that file's path on your disk.

Your Gateway keeps a session's conversation for 90 days and then sweeps it, whole sessions at a time.

Who your Gateway is

You choose this once, in the first-run wizard, and the product states it plainly on the card you pick: Your agents run on your machines. Fleet metadata and conversation history are stored on the hosted gateway so remote history and supervision work.

• Hosted - the Gateway is ours, so 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, so the same data lands on your own hardware and the retention window is yours to set. What the Gateway does.

Signing in is always recorded

When you sign in - in a browser, or in the browser page the Director opens to sign you in - the website records the sign-in against your account, with where it came from: web from a browser, app from the Director handoff. That is the whole record. There is no switch for it: it is how accounts work, and it is what tells us how many people use DevThrottle.

The one switch: Product usage data

Your account has a single control, Product usage data, on the console's Settings page. It is on by default and you can turn it off at any time. Today it records your preference and gates nothing: the usage-telemetry program it was built for was removed in July 2026, and nothing collects on the strength of this flag. The sign-in record above is not covered by it, and neither is the conversation history your Director sends to your Gateway. The control is kept because the consent it expresses is real - if collection returns, this is what it will answer to.

It is the only one. The Cockpit's fleet-wide telemetry switch went with the rest of the program described at the top of this page, so if something points you at a second switch on your Gateway, it is out of date.

What is written on your machine

• Terminal screen recordings - off by default. When you turn them on, frames are appended to a file in the Director's local application data folder on that machine, and removing the session removes them.
• Your working files - agents run on your machines and edit the repositories you point them at, in place.