Privacy Policy
This policy explains what the CADUCEX Codex Cloud Workspace (cct) collects, why, who we share it with, how long we keep it, and the rights you have.
1Scope
This policy applies to the Codex Cloud Workspace provided by CADUCEX ("we", "us", "our"), including the invitation signup page, the admin console, the authentication pages, your dedicated container workspace, and email we send about the service.
Third-party services you connect yourself (for example OpenAI or DeepSeek) collect and process information under their own privacy policies. This policy does not cover them.
2What we collect
2.1 Information you provide
- Account information: email address (your login name), a cryptographic hash of your password (one-way, not reversible), tenant code, trial dates, and plan/seat markers. Before your first login, the system generates a one-time initial password, stored with 0600 permissions in your dedicated directory for first login and manual re-sending; it is deleted immediately after you change it at first login.
- Invitation information: the invitation code you use, the email bound to it, and when it was redeemed.
- Consent records: when you accepted the Terms and Privacy Policy, the version, the document hash, and the source IP of the registration/first-login request.
- Order and billing information: plan/seat, order number, payment status, billing period and renewal records. We do not store full card numbers.
- Communications: emails with us about opening, support or renewal.
- Model credentials: a DeepSeek API key you enter, or credentials created by the OpenAI
device-auth flow. They are stored only in your dedicated container's working directory
(
secrets/key files andauth.json, permissions 0600). The admin console does not display or forward them.
2.2 Information generated by using the service
- Login and security records: login time, source IP, session cookie, failed-login lockout records, and admin audit records (who did what to which tenant, and when).
- Operational and delivery logs: container resource usage (CPU, memory, disk), service health, and email delivery status/message IDs (used for troubleshooting).
- Content you create: files you upload, documents you generate, conversation history with the agent, and code in your workspace. By default this is stored in your dedicated container (one container per customer, isolated from others).
2.3 Data minimisation
We collect what is necessary. We do not collect information unrelated to providing the service, billing or security. We do not include advertising SDKs or cross-site behavioural tracking.
3What we do not collect
- Your actual login password. We store only an irreversible hash; we cannot see your password. The initial password is a one-time system-generated credential: before your first login, an administrator can read it in the admin console to re-send it; it is deleted as soon as you change it at first login.
- Full card numbers, expiry dates or security codes. Payments are handled by a payment processor or a manually confirmed method; we do not receive or store full card data.
- Advertising identifiers or cross-site tracking data.
- Your model-provider password. OpenAI subscription login uses the official device-auth flow; the password is entered only on the provider's page and never passes through us.
4How we use information
| Purpose | Information involved |
|---|---|
| Open and maintain your account; provide the workspace | Account information, tenant code, usage records |
| Send service notices (opening, expiry, security) | Email address, delivery status |
| Bill, reconcile, handle renewal or refunds | Order and billing information |
| Troubleshoot and support | Operational logs, communications |
| Security (brute force, abuse, attack detection) | Login records, source IP, security logs, consent records |
| Quota and resource management | Resource usage, daily turns, storage |
| Comply with law and lawful requests | As required by law |
5What we do not do
- We do not sell, rent or trade your personal information to anyone.
- We do not use your files or conversations to train our own models or improve our own models.
- We do not use your model key for anything other than the model calls you request, and we do not give it to third parties.
- We do not display your model key or workspace token in the admin console; it shows only connection status.
6Sharing
We share information only where necessary:
- Model providers (OpenAI, DeepSeek, or another provider you choose). Your prompts and code are sent to the provider you selected, under your own account and their terms. We do not choose a provider for you or share your credentials with other tenants.
- Email delivery to send account, expiry and security notices. We provide the recipient address and message content; delivery status and message IDs are retained for troubleshooting.
- Infrastructure hosting for servers, network and storage, only as needed to host the service.
- Legal requirements. We may disclose information in response to valid legal process, a court order, or where the law requires it. Where lawful, we will try to notify you.
We do not share your personal information with other third parties except as described above.
7Where data is stored
- The service servers and tenant data are currently hosted in Canada.
- Your model provider may be located in the United States, China or another region. When you ask the agent to call a model, the relevant prompts and code are sent to that provider. Choose a provider that meets your own compliance requirements.
- Email delivery may process message metadata and content in other regions.
- Cross-border transfers may be subject to different data protection laws. We use reasonable safeguards for transmission (such as TLS).
8Retention
- Account and tenant data: retained while you use the service. After closure, data is retained for a period under our internal process (usually no more than 30 days) and may then be deleted. If you ask us to delete it, we will delete the account and tenant data directory after processing the request (irreversible).
- Audit logs: retained while needed for security and accountability; we clean or anonymise them on an internal cycle. They are not used for marketing.
- Email delivery logs: used for troubleshooting and delivery reconciliation; cleaned on an internal cycle.
- Consent records: retained while you use the service and for as long as required by law after deletion, to evidence consent.
- Order and accounting records: retained as required by applicable tax and accounting law.
Deletion is irreversible. Export anything you need before deleting your account.
9Your rights
Subject to applicable law, you have the right to:
- access the personal information we hold about you;
- correct inaccurate or incomplete information;
- delete your account and tenant data (deletion is irreversible);
- export files and content in your workspace;
- withdraw consent (which may mean you can no longer use the service);
- complain to a competent data protection authority.
Email the address below to make a request. To protect your account, we may need to verify your identity first. We will respond within 30 days unless the law provides otherwise.
10Cookies
- We use one strictly necessary session cookie (
cct_session) to keep you signed in. It is not used for advertising or cross-site tracking. - The signup page and workspace may store small preferences (such as language or theme) in your browser. That data stays in your browser and is not automatically uploaded.
- You can clear cookies in your browser; you will need to sign in again.
11Security and its limits
- HTTPS/WSS in transit; tenant containers are isolated with read-only root filesystems, dropped capabilities and resource limits;
- passwords are stored as irreversible hashes; model credentials and workspace tokens are stored with 0600 permissions in the tenant's dedicated directory;
- the admin surface is behind the edge and a separate authentication layer, and admin actions are audited;
- abnormal logins, brute force and abuse are subject to lockouts and rate limits.
No system is perfectly secure. Use a strong password, do not share your account, and back up important data. If a security incident may affect your rights, we will notify you as required by applicable law.
12Minors
The service is intended for adults with full legal capacity. You must be at least 18 years old. If you are under 18, use the service only with the consent and supervision of a parent or guardian. We do not knowingly collect personal information from minors.
13Changes
We may update this policy. For material changes affecting your rights or the way we handle information, we will give 30 days' notice by site notice or email, and update the version and effective date at the top of this page. If you continue to use the service after a change takes effect, you accept the updated policy.
14Contact
| Trade name | CADUCEX |
|---|---|
| Product | Codex Cloud Workspace (cct) |
| Privacy contact | talarixcanada@gmail.com |
| Governing law | Ontario, Canada |
If you need the legal entity name and address for a privacy request or legal process, email the address above and we will provide it within 3 business days. This policy is also available in Chinese. Last updated 25 October 2026.