Data Security and Compliance

CodexZH processes customer data only as necessary to provide services, billing, troubleshooting, security audits, anomaly detection, abuse prevention, content safety, compliance retention, dispute resolution, and lawful cooperation.

• No active use of customer inputs, outputs, code, or business data for general model training, fine-tuning, or distillation.
• No selling, renting, or trading of customer data.
• No active use of customer data for advertising, profiling, or public case studies.
• Model identifiers, costs, and call status follow console usage records.

To complete model calls, customer input, request parameters, necessary context, and response content may be transmitted to necessary partners such as model providers, cloud providers, network providers, or security providers. Their terms, privacy policies, regional restrictions, quotas, and data processing rules may apply, and updates to those rules may affect the service.

• CodexZH does not maintain a fixed public list of supported countries or regions. Actual availability depends on local law, payment availability, network conditions, and restrictions imposed by model providers and cloud providers.
• If a region, channel, model, or provider is unavailable, restricted, or presents compliance risk, CodexZH may limit, suspend, or adjust access.
• Users are responsible for confirming that their location, use case, data type, and end-user location may lawfully use the relevant third-party model service.

If a supported model, node, or service provider involves overseas processing, inputs, request parameters, necessary context, and responses may be transferred overseas or accessed by overseas entities. Confirm data legality, authorization, redaction, and any required personal information or cross-border compliance procedures before calling.

CodexZH may use model providers, cloud providers, network and security providers, payment providers, and email providers only as necessary to deliver model calls, hosting, security, billing, notifications, and support.

• Call metadata is retained by default for billing, audit, usage analytics, troubleshooting, and security handling.
• Complete prompts and responses are not retained long-term by default; short-term processing may occur only as necessary for call completion, customer-authorized troubleshooting, or security review.
• Call metadata for billing, audit, and security (request_id, token counts, status codes, cost, etc.) is retained under a data minimization principle and is separated from complete inputs and outputs where feasible.
• CodexZH may apply rate limits, quotas, anomaly monitoring, or necessary blocking for security, billing, service stability, or third-party provider requirements.