Privacy for OpenRig's developer tools

Last updated 2026-11-12.

This page covers OpenRig's developer tools:

It doesn't cover the openrig.dev website.

What we receive

Nothing, by default. The tools have no analytics, telemetry or crash reporting, and they don't send your code, prompts, conversations or usage to us.

The plugin starts rig mcp serve on your machine. That server talks to your own OpenRig daemon, on the same machine, unless you've pointed it at another. You can point it elsewhere with OPENRIG_URL or a port setting, or by serving it with rig mcp serve --http beyond this machine, which needs a grant.
The extension runs the rig command and git on your machine and has no network code of its own. Its "Get OpenRig" button opens openrig.dev in your browser. When you join from Cursor, it adds an openrig entry to your project's .cursor/mcp.json.
The daemon keeps its records on the machine it runs on, in your OpenRig home folder (~/.openrig by default). Those records include tasks, messages, transcripts and logs.

When the daemon starts, it makes one request to GitHub to check for a plugin update. The request sends no data from your machine, but GitHub sees the request and your IP address.
Services you connect yourself talk to those services under their own terms. These include Slack, ntfy, webhooks, OpenRouter, a remote OpenRig daemon or a grant service. rig context downloads a web address only when you give it one.

The app you connect (Claude Code, Codex, Cursor, VS Code with Copilot) and its model provider see the tool results their model asks for, as with any MCP server.
The coding agents OpenRig runs use your own accounts with their providers.
How those apps and providers handle your data, and any telemetry your editor collects, is set by their privacy terms, not ours.

Questions: team@openrig.dev. If this changes, we'll update this page and its date.