Codag
Privacy and data flow

What leaves your machine

Provider traffic stays yours. Eligible tool output is processed transiently. Exact content stays local.

Codag is built so that your provider relationship stays yours and your content never becomes Codag's. This page describes the actual data flow; the privacy policy is the legal version.

Model traffic never touches Codag's cloud

After setup, your agent's model traffic goes through a local proxy on your machine and then directly to your provider. Provider credentials are never sent to or stored by Codag. Streaming and cache behavior are preserved. Compatible custom gateways you already use are kept in the path.

What Codag receives

When your agent runs a tool and the result is large and eligible (logs, test or build or lint output, search results, file listings, document reads, agent handoffs), the local service sends that tool output plus the minimum task context to Codag's service. It is processed transiently to produce the reduced evidence and is not retained. Source code, diffs, configuration, exact structured data, and anything Codag does not recognize are never sent; they pass through unchanged. Customer content is processed only on Codag-controlled inference endpoints.

Exact retrieval stays local

The parts a reduction omits are kept encrypted on your machine for seven days with a 1 GiB cap. When your agent needs an exact omitted section, it retrieves it locally by selector: specific line ranges, JSON paths, or groups. There is no way to request the unrestricted original through the retrieval tool, and Codag's cloud cannot retrieve it at all.

Accounting is contentless

Billing and savings reporting run on contentless metrics: byte and token counts, estimated costs, latency, reduce or passthrough decisions, fail-open reasons, and retry and retrieval counters. Metrics never include prompts, commands, paths, filenames, task text, or tool output. These metrics are required; optional product telemetry can be turned off with codag config set telemetry off.

Failure means passthrough

Unknown action types, validation failures, service timeouts, policy failures, and exhausted quotas all resolve the same way: your agent gets the original bytes, unmodified. Codag is designed to be safe to leave attached.