Privacy Policy

CCX is a self-hosted AI API proxy and protocol translation gateway. The CCX project itself does not include telemetry, advertising trackers, or user behavior analytics.

Data the maintainers do not collect

The CCX project maintainers do not collect the following data from self-hosted CCX instances:

• API request or response content
• API keys, access keys, or upstream provider credentials
• Channel, model, or proxy configuration
• User, device, or usage analytics
• Desktop app local configuration

How proxy requests are handled

When CCX runs as a proxy gateway, it processes API requests inside the user's own deployment environment and forwards them to the upstream model providers configured by the user.

This means:

• Request data passes through the CCX service operated by the user
• Request data is forwarded to the upstream API providers configured by the user
• Upstream API providers may process that data according to their own terms and privacy policies

Please review the privacy policies and data handling rules of the upstream providers you configure before use.

Logs and local data

CCX logs are controlled by the deployer. Depending on deployment method and configuration, the following data may be stored in the user's own environment:

• CCX service logs
• Access logs and error logs
• Reverse proxy, container platform, or system service logs
• Desktop app local configuration files

This data is not uploaded to the CCX project maintainers. Deployers should manage log retention, access control, and key protection policies for their own environments.

Desktop app

CCX Desktop stores its configuration on the user's local device. The project maintainers do not collect desktop app configuration, keys, or usage data.

The desktop app may access GitHub Releases to check for or download updates. Those requests may be subject to GitHub's own logging and privacy policy.

Documentation site and downloads

When visiting the CCX documentation site, GitHub repository, or GitHub Releases, the hosting platforms may generate basic access logs. Those logs are handled by the corresponding platforms and are not generated by self-hosted CCX instances.

Code signing

CCX Desktop uses the SignPath Foundation for code signing. Code signing helps users verify application origin and integrity; it does not mean the CCX project collects user data.

Contact

If you find a privacy-related issue, please contact the project maintainers through GitHub Issues or the security disclosure channel.