1. Request handling and disclosure scope
We do not publish how requests travel through our systems, our data flows, or our link topology. This is an internal security decision.
Customers often ask how requests travel. Instead, this page provides three verifiable substitutes: the vendor-level subprocessor list (section 4), data retention periods (section 2), and encryption and key management (section 3).
Some API responses include an X-Served-By header. When present, it identifies the provider and model that served the request.
We do not provide link diagrams or simplified topology diagrams.
2. Data retention
| Data category | Retention period |
|---|---|
| Successful API request metadata | 90 days |
| Failed API request metadata | 180 days |
IP address and User-Agent in security audit events (audit_events) | 90 days, then set to null |
| Account data | For the life of the account |
| Prompt and completion text | Not stored in CodeGateway's application database |
When you delete your account, CodeGateway deletes account data from its primary database.
This page describes primary-database deletion only.
3. Encryption and key management
Traffic between your client and CodeGateway uses TLS.
Cloudflare provides encryption at rest for D1, R2, and KV storage, with keys managed by Cloudflare.
API keys are stored only as SHA-256 hashes. The plaintext key is shown once at creation and is not stored.
Account passwords use PBKDF2-SHA256 with a per-row random salt.
TOTP secrets for two-factor authentication use AES-256-GCM with AAD pinning. Dashboard and admin use separate keys.
4. Subprocessors
We use the following providers to run CodeGateway. This list is current as of 7 November 2026.
| Provider | Purpose | Data processed | Location |
|---|---|---|---|
| Cloudflare, Inc. / Cloudflare Pte. Ltd. | Edge network, compute, storage, queues, transactional email, bot protection | Request and response traffic in transit, account data, usage metadata, uploaded bank-transfer proof files | Global network |
| Stripe, Inc. / Stripe Payments Europe Ltd | Payment processing, subscriptions, refunds | Payment and transaction data; card data is handled by Stripe | United States / Ireland |
| Anthropic, OpenAI, Google, DeepSeek, xAI, Zhipu, Moonshot, Qwen, MiniMax, ByteDance | Inference for the model you select | Prompt and completion content for the model you select | Varies by provider |
| Google LLC | Google Tag Manager and Google Analytics on the website; analytics storage is denied by default and collection starts only after consent | Website usage data after consent | United States |
Model availability changes. The model catalog shows the current models.
5. Certification status
CodeGateway does not hold SOC 2 certification.
CodeGateway does not hold ISO/IEC 27001 certification.
In October 2026, we completed an internal scope and cost assessment for SOC 2 and ISO 27001. Certification work has not started.
CodeGateway does not claim PCI DSS certification. Card payments are processed by Stripe.
6. Incident record
Current service status is at status.codegateway.dev. The page shows live health probes and pricing-data freshness. It is not an incident history.
This version of the Trust Center does not publish an incident history.
To report a security vulnerability, use GitHub Private Vulnerability Reporting on the Whitedit/code-gateway repository.
7. Enterprise security questionnaire
For a security questionnaire or procurement review, email support@codegateway.dev with the subject "Security questionnaire".
8. Company and contact
CodeGateway is a product of WHITEDIT LTD.
WHITEDIT LTD is a company registered in England and Wales, company number 16373922.
Registered address: Suite 11245, 61 Bridge Street, Kington, HR5 3DJ, United Kingdom.
Contact: support@codegateway.dev.
This page is for information only. It is not a contract, warranty, or legal opinion.