DDC Agent Proxy

Privacy policy

Last updated: September 11, 2026

This policy describes how DDC processes information when you visit the Agent Proxy website, use the operator console, or send traffic through the gateway. Contact ddc@vdtdata.com with privacy questions.

Information processed by the service

The gateway processes proxy requests to authenticate clients, select upstream routes, enforce limits, and forward traffic. Operational records can include customer and API-key identifiers, destination host, route and exit IP, request timing, status and error categories, transferred bytes, and usage totals.

Customer configuration, key metadata, provider accounts, routing configuration, and usage records are stored to operate the deployment. Provider credentials and recoverable tenant keys are encrypted in application storage. Session keys are hashed for lease binding.

Proxy traffic and third parties

The selected upstream proxy and target website receive the information needed to carry your request. HTTPS content remains encrypted inside the CONNECT tunnel between your client and the target. Plain HTTP traffic does not have that content protection. The gateway does not operate a browser or store your browser cookie jar.

Hosting, infrastructure, and monitoring services may process network information and diagnostic records needed to operate the deployment. Providers and target websites handle information under their own policies.

Cookies and browser preferences

Operator sign-in uses an essential, HttpOnly session cookie with a 12-hour maximum lifetime. Signing out removes the browser's session cookie. This product uses operator-managed access and does not request a Google account or social-login permissions.

Your browser stores appearance, language, time-window, and refresh preferences locally. Public language URLs determine the language of the page you open. The website does not include advertising trackers. Optional error and performance monitoring depends on the deployment configuration.

Storage and retention

Configuration and usage records remain available according to the deployment's database and retention settings. Lease state expires according to configured absolute and idle lifetimes. Signing out, revoking a key, or releasing a lease does not automatically erase historical usage records.

Logs, monitoring systems, and backups may have separate retention periods. Contact DDC or the operator of your deployment for the retention settings and deletion scope that apply to your service.

Your choices and requests

You can clear browser preferences, sign out of the console, and ask an authorized operator to revoke keys or change access. To request information, correction, or deletion of records relating to you, email ddc@vdtdata.com. We may need to verify your authority to act for the relevant customer or deployment.

Access-request details stay in your browser until you open your email application or copy them. DDC receives them when you send the email. Contact information and correspondence are used to respond to your request. Do not send passwords or API keys.

Updates to this policy

DDC will update this page and its revision date when the policy changes. Deployment-specific agreements and notices may provide additional information about your service.

Continue exploringRead the integration guide