Xerg Privacy

Xerg is built around a local-first audit path. This page summarizes the data boundaries that public docs, the CLI, and hosted services should keep aligned.

Local CLI

Local audits run on your machine. Xerg may write local audit snapshots for compare, but local audit data does not leave your environment unless you explicitly use hosted push, connect, or hosted MCP setup flows.

Hosted services

When you push an audit to Xerg Cloud, Xerg receives audit totals, rollups, findings, recommendations, comparison deltas, and source metadata needed to show hosted dashboard and MCP results.

What push payloads exclude

Push payloads exclude raw prompt and response content, local source file paths, local snapshot store paths, and internal-only finding details.

Account and billing providers

Hosted sign-in, workspace management, and billing may be handled by third-party providers such as Clerk and payment processors. Those providers process the account and billing data needed to operate hosted workspaces.

Contact

Privacy questions can be sent to query@xerg.ai.