Your privacy deserves a clear explanation.

1. Information linked to your account

To provide the service, Codz may store your account email address, username, selected language, plan, token balance, interface preferences, and profile photo if you add one.

This information helps maintain your session, display your profile, apply your plan limits, and respond to support requests. Your email address is not shown to other regular users in the public interface. Authorized administrators may access it when necessary to operate the service, maintain security, or resolve an issue.

Never share your password, authentication codes, or API keys in your profile name, messages, or files.

2. Messages, historique et conversations

When you send a message, its text is processed to generate a response. Conversations and replies may be stored so you can revisit your history and the service can maintain conversation context.

Usage records may include the requested model, provider, request time, token volumes, and credits used. This information helps track limits, explain unexpected costs, and diagnose errors.

A conversation should not be treated as a vault. Avoid sending passwords, banking information, identity documents, private keys, business secrets, or any data you are not authorized to share.

3. Files, images, and content sent to models

Attachments are processed to extract supported text or send images to a compatible model. Extraction may be partial or fail depending on the format. Relevant content may be included in the context sent to the AI provider selected by the app.

The external provider must process this content to generate a response. Its own terms, retention rules, and privacy settings also apply. Codz cannot guarantee a third-party provider’s internal practices beyond its published commitments.

Some administration tools may show authorized personnel recent conversation excerpts to help diagnose issues or investigate abuse. File metadata, such as names and types, may also appear in this context. Only send information strictly necessary for the task.

4. Who can access the data?

Access to data is restricted by the service’s authorization controls, but you should not assume that every conversation is visible only to you. Authorized administrators may review certain account information, security logs, and recent conversation text when operating the service, resolving incidents, or investigating abuse.

AI providers receive the content needed to answer your requests. Technical service providers may also process operational data for hosting, security, or service delivery.

Do not treat an assistant response as a guarantee of confidentiality. For sensitive tasks, anonymize names, remove identifiers, and replace secrets with fictional values.

5. Why is this data used?

• Create and secure account sessions.
• Display your profile and retain conversations for your history.
• Send requests to models and display their responses.
• Track tokens, apply limits, and update balances.
• Detect spam, abuse, suspicious sign-in attempts, and automated traffic.
• Diagnose errors, improve reliability, and respond to support requests.

Data should not be used for an incompatible purpose without an appropriate explanation. Technical controls and the service’s actual configuration determine which processing is enabled.

6. Cookies and local storage

A session cookie keeps you signed in. Your browser may also remember preferences such as the display theme or language. These preferences improve continuity but do not replace server-side security controls.

On a shared device, sign out after use and avoid saving credentials in the browser. Read the cookie notice for a separate explanation of the mechanisms used.

7. Retention, correction, and deletion

Account data and history are retained for as long as they are useful for providing the service, maintaining security, preventing fraud, or resolving disputes. Some technical logs may be retained for a limited period when needed to investigate incidents or meet applicable obligations.

To request access to your data, correction, export, or deletion, contact support through the contact page. To protect your account, reasonable verification of account ownership may be required. Timing and scope depend on the request and applicable technical or legal constraints.

8. Security and shared responsibilities

Codz uses server-side controls, authorization checks, request limits, and secret-protection mechanisms. Two-factor authentication is available for compatible accounts and should be enabled when offered.

No online service can guarantee zero risk. Use a unique password, keep your devices updated, never share temporary codes, and promptly report unusual activity. More recommendations are available in the Security Center.

9. Sensitive data and minors

Do not submit health data, official identifiers, financial information, or sensitive information about other people unless you have the necessary authorization and understand the consequences of processing it through third-party models.

You are responsible for checking that you may legally use the service in your country and meet the applicable age requirements.

10. Policy updates

This policy may be updated as the product, its providers, or applicable requirements change. The date at the top of the page indicates the latest revision. Significant changes may also be announced in the service.

For privacy questions, use the contact page. This page describes the service’s intended operation and is not personalized legal advice.