Legal information
Privacy policy
Updated:
Codex API processes only the data needed to run accounts, API access, balance accounting, security, and user support.
Operator and contacts
Service operator: Codex API Staging. Jurisdiction: Российская Федерация.
For privacy and deletion requests, contact support: https://t.me/VIDADS_RU_SUPPORT.
Data we process
Account data: email, optional name, role, creation date, password hash, and signed browser session.
API access data: key prefix, SHA-256 key hash, status, creation and revocation dates. The full key is stored so you can view it again in the dashboard; it is deleted when the key is revoked.
Billing and audit data: token balance, usage events, request ID, route, model, status, latency, error code, and charged amount.
Telegram bot: Telegram ID and the history of your chats with the bot (questions and answers), so the bot keeps the conversation context. Also subscription proof for bonuses, referral links, and operator balance adjustments.
Images: the prompt is processed for generation, and the generated image is kept for up to 12 hours so it can be downloaded.
Data we do not store by default
The API request log does not store request or response text: only model, volume, status, latency, and the charged amount.
Studio history stays in your browser. Telegram bot chat history is stored by us, and you can delete any chat in the bot itself.
Why we process data
To create accounts, verify passwords, issue API keys, authorize gateway requests, and protect access.
To calculate usage, charge balances, display logs, diagnose errors, and prevent abuse.
To handle support requests, balance adjustments, refunds, bonuses, and referral operations.
To send service emails about the account: registration, onboarding tips, and account balance. Every such email has an unsubscribe link; promotional emails are sent only with the user's consent.
Service processors
AI model requests are processed by Codex API infrastructure and service processors needed to return model output.
Hosting, database, Telegram, and payment/support channels may process data only within their operational role.
Retention
Accounts, keys, balances, and usage ledgers are stored while needed for the account, financial accounting, security, or obligations.
Generated images are deleted after 12 hours.
Backups and infrastructure logs are removed according to the production retention schedule.
User rights
A user may request access to their data, correction of profile data, account deletion, or review of a disputed operation. API keys can be revoked and bot chats deleted by the user directly.
If a request affects financial accounting, security, or mandatory logs, some data may be retained until the required period ends.
If a support conversation differs from the published text, the current version on this page controls.