Privacy
The app
The desktop app and the runmarq command run on your computer and store data only there, in runmarq's data folder. They do not need an account, make no network requests to compute estimates, and include no analytics or crash reporting.
Stored on your computer
- When each run started, waited and ended, and how it ended.
- For each event: its type, time, tool name (such as “Bash” or “Edit”), activity category and duration.
- A task category and size estimated from the prompt, and a salted hash of the prompt used only to recognise repeats.
- Unless you turn it off: a salted, hashed word vector of the prompt, used to find similar earlier runs. The prompt cannot be read back from it.
- The effort level and permission mode the agent reports.
- Unless you turn it off: numbers read from the agent's own transcript on your computer (response counts, token counts and context size), and how many files and lines changed in the repository during the run, from
git diff --numstat. - For shell commands: a salted hash of the program and subcommand (such as “npm test”) and how long it took.
- A salted hash of the repository's location, and its folder name if you allow it (on by default; off in Settings).
- The model name, when the agent reports one.
- Forecasts, and how they compared with what happened.
- Your settings, including any usage budget you set, and a log of which notifications were shown.
- If you turn it on: a short title from the first line of each prompt, with secret-looking text removed.
Never stored
- Prompt text (apart from the optional title above).
- Source code or file contents.
- Commands, their arguments, or their output.
- Transcript text, the transcript's location, the working folder's path, or the names of changed files.
- Environment variables, API keys or tokens.
Estimates are computed entirely on your computer and use none of your agent's model usage. Prompt text is read only inside the hook process, to classify the task, and is discarded when that process exits a few milliseconds later. If the collector is not running, the already-minimised events wait in a small file on disk and are deleted once delivered.
The Usage page and stuck warnings are worked out from the counts and timings listed above; nothing extra is collected for them.
Your control
- Delete history at any time in Settings → Data, or with
runmarq forget. - Set automatic deletion after 30, 90 or 365 days.
- Export your history as CSV, which contains timing data only.
- Removing an integration removes only the hook entries runmarq added to that agent's configuration.
This website
This site counts visits with Vercel Web Analytics: the page, the referring site, the browser, operating system and device type, and the country. It sets no cookies and keeps no personal identifiers, and the site has no other trackers. The server may keep standard request logs (address, time, page) for security and operations.
The early-access list is not open, so this site collects no email addresses.
Last updated .