DocsHow it works
What stays on your machine
StateSync never receives your code, prompts, chats, commands or voice. What it does receive is counts.
Your agent connects to its provider exactly as before, on your own account. No StateSync server sits in that path.
Stays on your computer
- Your code, and the map StateSync builds of it.
- Your prompts and the agent's replies.
- Terminal commands and their output.
- Voice recordings, which are transcribed on your machine and then discarded.
- API keys, in your operating system's secure store or the agent's own config.
Leaves your computer
- The request your agent was always going to make, to its own provider, on your own account.
- Usage figures, sent to StateSync. Counts and totals, listed below.
The usage figures
StateSync receives figures about how the app ran, never anything you wrote or your agent produced. The service refuses any upload that carries a field it has not declared, so nothing extra can slip in.
- The StateSync version, your operating system, and basic facts about the device, such as processor type and time zone.
- How many tokens, requests and tool calls ran, how long they took, and how much StateSync saved.
- Which models ran, and the plan you have with each provider, for example Claude Max. Never its billing details.
- Which features are on, a project's rough size and the programming languages in it, and an error report when something fails.
Never sent: prompts, replies, code, file names or paths, commands, search queries, tool output, keys or passwords.
Deleting your data
Archive a project, then delete it from Settings, under Archive. StateSync deletes its own record of the project. Deleting the project's map, and deleting the project folder itself, are separate boxes that stay empty unless you tick them.
The full list
Every field StateSync receives is listed in the privacy policy. The list is short, and written to be read.