Data & Privacy
ProxAI Gateway never collects, stores, or sells your secrets, API keys, or tokens. All redaction is handled locally on your machine, ensuring sensitive data never reaches our servers.
The gateway's data handling is designed to be boring and auditable:
- The gateway is open source under the MIT license at github.com/proxai/proxai_gateway. We keep it open intentionally — you can read exactly what is collected, how redaction works, and what leaves your machine.
- No proxy, no interception. The gateway never sits between your agents and their model providers. It only reads the session files the agents already write to disk.
- Redaction happens on your machine, first. Secrets are stripped before anything is stored locally, and therefore before anything is uploaded.
Uploaded
- Redacted session recordsThe agent conversations you turned on capture for, with all sensitive keys fully redacted locally before upload.
- Capture metadataWhich agent produced each record and how far it got, so the dashboard can order your sessions.
- ProxAI Gateway and agent versionsUsed to ensure compatibility as your tools update.
- A hashed host identifierA one-way fingerprint of your machine, tied to your account. It confirms uploads really came from your ProxAI Gateway and blocks spoofed ones, without ever revealing your raw hardware ID.
Never
- Unredacted secretsSecrets are redacted on-device prior to local buffering, guaranteeing raw credentials never touch our API servers.
- Your raw hardware IDOnly the one-way hash leaves your machine. The original never does.
- Files your agents did not writeProxAI Gateway reads agent session files and nothing else on your disk.
What gets redacted
Every captured record passes through a redaction pipeline before it is buffered. The rules cover 13 categories of secrets:
| Category | Examples |
|---|---|
crypto-keys | PEM, SSH, PGP, and other private key material |
llm-providers | OpenAI, Anthropic, and other model-provider API keys |
source-control | GitHub, GitLab, Bitbucket tokens |
cloud-providers | AWS, GCP, Azure, Cloudflare credentials |
payment | Stripe, PayPal, Shopify keys |
saas-tools | Datadog, Segment, Algolia, PagerDuty keys |
auth-services | Okta, Auth0, Twilio, SendGrid keys |
communication | Slack, Discord, Teams tokens |
ci-package-managers | CI tokens, npm/PyPI publish tokens |
http-headers | Authorization headers, API-key headers, cookies |
connection-strings | Database URIs with embedded credentials |
generic-tokens | Long hex strings, session ids, and other token-shaped values |
keyword-secret | password=, token=, secret= style assignments |
Every rule is part of the open-source repository, so the exact patterns are inspectable — not a black box.
Excluding specific projects
You can prevent ProxAI Gateway from capturing any data from specific repositories or folders. Excluding a folder pauses collection across all sources (Claude Code, Cursor, Codex, Gemini) and freezes database watermarks. When you un-exclude a folder later, the gateway resumes and automatically backfills your history.
# Exclude a folder
proxai-gateway exclude ~/repos/secret-project
# Resume collection (Un-exclude)
proxai-gateway unexclude ~/repos/secret-project
# Print your current list of excluded project paths
proxai-gateway exclude --listInspect it yourself
Because the buffer lives on your machine, you can always audit what was (or will be) uploaded. This command exports every record from the last 7 days in the local buffer, already redacted, directly into a JSON file on your desktop for easy viewing:
proxai-gateway logs -v --json --since 7d > ~/Desktop/records.jsonRun proxai-gateway logs --help to see more options for filtering, formatting, and outputting your local audit logs. Records of successful uploads are kept locally for 365 days by default (configurable).