Analytics & privacy
What anonymous usage data Quorum collects, what it never touches, and the several ways to turn it off.
Last updated
Quorum reports anonymous, aggregate usage stats so development can be steered by how the tool is actually used. It is designed around one rule: send the shape of usage, never its content. Your work never leaves your machine.
What is collected
A run may report a small, fixed set of non-identifying facts:
- Quorum version, operating system, architecture, Node version, and whether the run was in CI.
- Which command you ran (
startorinit). - The provider types in play (e.g.
claude,fake) and the number of agents, as a coarse band (1,2-3,4-8,9+) rather than an exact count. - Whether MCP, custom capabilities, triggers, or a budget are configured — as
booleans — plus the kinds of triggers
(
schedule/webhook/process/inbox). - A random install id and a coarse run duration.
Each install is identified only by a random UUID minted locally. It counts runs as coming from one machine without knowing whose machine it is, and it is never linked to you, your account, or your IP.
What is never collected
By construction, none of the following is ever read or sent:
- Your mission, your
QUORUM.md, or any agent prompt or persona. - Goal, task, CRM, or document content.
- Your organization’s name, MCP server names or URLs, or any file path.
- Command arguments, environment values, or API keys.
Turning it off
The choice is machine-global — make it once and it covers every org you run.
quorum analytics status # what's collected, whether it's on, and why
quorum analytics disable # turn it off, remembered across orgs
quorum analytics enable # turn it back on
Environment variables work too, and the cross-tool
DO_NOT_TRACK standard is honored:
DO_NOT_TRACK=1 quorum # off for this run
QUORUM_ANALYTICS_DISABLED=1 quorum # off for this run
Analytics is off by default in CI — a build isn’t a person’s decision to
share. The on/off choice and the random install id are the only things stored, in
~/.config/meffecta_quorum/config.json (or $XDG_CONFIG_HOME/meffecta_quorum/).
See Configuration & env vars for the related settings.