Privacy Policy
How DriftWatch AI LLC handles your account data and the LLM traffic you route through our proxy — what we collect, what we deliberately do not keep, and the controls you have.
This Privacy Policy outlines how DriftWatch AI LLC ("DriftWatch AI", "we", "us", or "our") collects, processes, and safeguards your operational telemetry data. Users retain full control over their account data, team seats, and API credentials directly within their Account & Workspace Settings dashboard. For escalated privacy rights or formal data inquiries, contact privacy@driftwatchproxy.com.
1.Information We Collect
We collect the minimum needed to run your account, bill you correctly and show you proxy telemetry.
- Profile data — your email address and account identifier, handled through our managed authentication service, plus any display name you choose to add.
- Billing metadata — plan, subscription status, renewal date and invoice history received from our payment provider. Raw credit card numbers are never sent to or stored on our servers; the payment provider handles card data directly.
- Operational API telemetry — per-request timestamps, model provider, token counts before and after pruning, latency added, schema pass or fail outcome and drift signals.
- API key metadata — key labels, scopes, creation time and last-used time. Secret values are shown once at creation and stored only as a hash.
- Basic technical data such as IP address and user agent for dashboard sessions, used for security and abuse prevention.
2.Zero-Training & Payload Privacy
DriftWatch AI does not store, sell, or train AI models on the raw prompt payloads or user message content passing through the proxy.
- Prompt and completion bodies are processed in memory to prune context and validate structure, then discarded — what we persist is the numeric telemetry described above.
- We do not use your traffic to train, fine-tune or evaluate any model, ours or a third party's.
- We never sell, rent or share your payloads or telemetry with advertisers or data brokers.
- If you explicitly enable payload capture for a project so you can inspect raw vs. pruned requests in the dashboard, those captured bodies are stored under your account only, are visible only to your account, and follow your plan's retention window. Capture is off by default and can be turned off at any time.
3.Third-Party Service Providers
We use a small number of providers to deliver the service. Each receives only the data needed for its function.
- Managed Postgres and authentication provider (Supabase) — stores your account record, profile, API key metadata, schema rules and proxy telemetry.
- Payment provider — processes checkout, subscriptions, invoices and tax as merchant of record; it holds your card and billing address, we hold only the resulting subscription metadata.
- Edge and cloud hosting (AWS / Fly.io regions) — runs the proxy ingress and dashboard; traffic transits these networks but payload bodies are not persisted there.
- Model providers you address (OpenAI, Anthropic, Google and others) — receive the request you asked us to forward, governed by your agreement with them.
- We do not run third-party advertising or cross-site tracking scripts on the app.
4.Data Security & Retention
We aim to hold as little as possible, for as short a time as your plan allows, and to protect what we do hold.
- Data in transit is encrypted with TLS 1.3 between your client, our proxy and upstream providers.
- Data at rest is encrypted with AES-256 on our managed database and object storage.
- Access to production data is limited to the engineers who need it, authenticated with multi-factor login, and row-level security scopes every dashboard query to your own account.
- Automated log purging follows your active plan tier: 7 days on Developer, 30 days on Pro, 90 days on Growth and 365 days on Enterprise. Older records are deleted by a scheduled job.
- After account termination, logs and keys are purged within 30 days; invoices are retained where tax and accounting law requires it.
- No system is perfectly secure. If an incident affects your data, we will notify affected account owners without undue delay.
5.User Rights
You stay in control of your account data, and we will help with any request within 30 days.
- Access and export — download your proxy logs, schema rules and account data from the dashboard, or ask us for a machine-readable export.
- Correction — update your profile and billing details at any time from Account & Profile.
- Deletion — delete individual logs or request full account deletion, which revokes all keys and purges associated data.
- Restriction and objection — ask us to limit specific processing, including turning off optional payload capture.
- Contact our privacy team at privacy@driftwatchproxy.com for any of the above, or for a data processing agreement.