Application Privacy Policy

Application: DCP Proxy

Effective date: September 29, 2026

This policy explains what DCP Proxy does — and does not do — with your data. The short version: it runs entirely on your machine, collects nothing, and stores no credentials.

Data Accessed

  • DCP Proxy reads the OpenAI-compatible chat requests your client sends through it, solely to shrink conversation history (deduplication, pruning, summarization).
  • It forwards your Authorization header to the upstream engine you configured, untouched. It never reads, logs, or stores API keys.
  • Configuration (listen address, upstream URLs, compression settings) is stored in a local config.json next to the executable.

Data Usage

  • Request content is processed in memory only, to apply the token-saving transforms you enable.
  • Summaries are produced by the same upstream engine your client already uses — the proxy adds no third parties and no external services.
  • DCP Proxy contains no telemetry, no analytics, no accounts, and no phone-home code of any kind.

Data Storage and Retention

  • A local log file (dcp-proxy-gui.log) records request routing lines (method and URL path) to help you debug connections. It may contain URLs of your upstream engines. Delete it at any time.
  • Cached conversation summaries live in memory only and disappear when the proxy exits.
  • No conversation content is written to disk by the proxy.

Data Sharing

Digit.Solutions does not receive any data from DCP Proxy. The only network traffic is between your client, the proxy, and the upstream engines you configure — all on your own setup.

User Controls

  • All processing happens locally; stop the proxy at any time from the tray icon.
  • Delete config.json and dcp-proxy-gui.log to remove all local state.
  • Disable compression entirely by raising the threshold if you want pure passthrough.

Public Access and Official URLs

Back to Manual View Terms of Service