Commercial policy

Privacy policy

Candidate effective date: 6 August 2026 · Not active until public billing launches

The service is designed to retain the minimum metadata needed for execution, billing, security, and reconciliation.

Data we plan to retain

Transient model processing

The Bridge keeps the repository on the customer machine, but Claude Code sends the prompt and context it selects—potentially including code snippets, tool results, and file contents—through the Agent Delivery gateway to DeepSeek. The candidate gateway forwards this content in memory and does not add it to the Cloud audit database. DeepSeek and the hosting network process that content under the final published subprocessor and retention terms.

Data excluded from the audit record

Whole repository copies, full provider request bodies, the DeepSeek API key, device bearer tokens, payment-card details, and local CLI transcripts are not stored in the Cloud audit database. Local reports remain in the customer worktree unless the customer exports them.

Purpose and retention

Data is used to provide, secure, support, bill, and reconcile the service. Planned retention is 30 days for Pro Managed audit events and 90 days for Team Managed; billing and legally required records may be retained longer. Final deletion and export procedures must be operational before billing opens.

Processors and transfers

Planned processors include Paddle for commerce, Vercel and Supabase for service delivery, and DeepSeek for model processing. A final subprocessor list, operator contact, provider retention statement, and cross-border transfer statement will be published before launch.

Your choices

Customers will be able to request access, correction, export, or deletion through the support channel, subject to security and legal retention requirements.