DeepCodex
TerminalsPricingDocs

Legal

Privacy Policy

Effective: September 16, 2026Last updated: September 17, 2026

This policy explains what DeepCodex collects, how it is used and how it is protected.

01What we collect

Account details (email, phone, WeChat nickname), sign-in and security logs (IP, device), API usage and billing records, and, when you turn on message storage, request and response bodies.

02How we use it

To provide and bill the Service, prevent abuse, diagnose faults, and send notifications when you enable usage alerts. Request bodies are used only for your own project profile and task-merging features, never to train models.

03Storage and retention

Account and billing records are kept while the account exists and, after closure, for the period regulations require. Message storage can be switched off and cleared from Settings at any time.

04Third parties

Inference is performed by upstream model providers; we forward only what a request needs. SMS, captcha, WeChat sign-in and payments are handled by their respective providers under their own privacy policies.

05Your rights

From Settings you can view and edit your profile, manage sessions, disable message storage and close the account. Other requests can be sent through the contact details in the footer.

06Your controls and deletion paths

Each of these is self-service in the console; no ticket needed.

  • Message bodies are stored only while the switch is on; off, we keep model, tokens, cost, duration and status.

    Turn off in Settings
  • Project memories can be disabled or deleted one by one; a deleted memory is never injected again.

    Manage memories
  • Sign-in sessions can be ended remotely; an unfamiliar device is cut off at once.

    View sessions
  • Closing the account needs a security confirmation; keys and sessions stop immediately and data is deleted after the statutory period.

    Close account

Cloud agents perform only the actions you allow and never bypass the terminal's own permissions, sandbox or confirmations.

07Security

Credentials are hashed or encrypted at rest and every connection uses TLS. We will notify you promptly of any security incident that affects you.

08How to reach us

Questions about a bill, your data or the account status: write to support@deepcodex.com; we reply within two business days.

Send emailOpen the console
Back to the siteTerms
Sections
01What we collect02How we use it03Storage and retention04Third parties05Your rights06Your controls and deletion paths07Security08How to reach us
DeepCodex

The DeepSeek API tuned for writing code.

Capabilities

Features & availabilityCodebaseParallel tasksRouting

Use

TerminalsSetup guideDocsPlaygroundConsole

Account

Pricing

Legal

TermsPrivacySupportsupport@deepcodex.com
© 2026 DeepCodex