CHATCODE · PRIVACY
Privacy Policy
Effective: August 19, 2026 · Beta Version 1
1. Scope
This policy describes how OzinTech handles data related to ChatCode, the ChatCode website, licensing, software downloads/updates, support, and optional telemetry. Third-party AI services you connect have their own policies and do not become part of OzinTech merely because they are used with ChatCode.
2. Projects, files, and source code
ChatCode is designed to work directly with projects on the user's computer. OzinTech does not need to receive a full copy of a repository merely for Project Brain to map it. Tools can access only the configured project scope and permissions.
When you ask AI to read, analyze, modify, or act, ChatCode may return the necessary file/context/result data through the connector to the AI provider handling the chat. Therefore, “local-first” does not mean that all data can never leave the computer: data that AI needs to see may be transmitted to the AI provider at your request.
3. Account, license, and device data
To provide the service, the system may process account/email information, plan, license status, technical device identifiers, activation events, application version, transactions, affiliate attribution, and operational data necessary for entitlement, security, support, fraud/abuse detection, and update distribution.
4. Efficiency measurement on the user's computer
ChatCode may locally measure AI → ChatCode data, ChatCode → AI result/context data, estimated tokens, provider/reference model, and Project Brain context reduction. These metrics cover only data passing through ChatCode and do not include the AI platform's chat history, Memory, system prompts, reasoning, or normal chat responses.
5. Sharing aggregate efficiency telemetry
On a new installation, aggregate telemetry sharing is not treated as consent by default. The installer asks separately and you may choose not to share. You can also change this choice in ChatCode.
If enabled, OzinTech may receive counters/buckets such as provider, reference model or unknown-model status, tool-call count, estimated bytes/tokens, project counts by coarse size bucket, operation category, app version/plan, and Project Brain efficiency metrics.
This aggregate telemetry is not designed to contain prompts, source code, file contents, file names/paths, chat history, connector URLs, full license keys, access tokens, passwords, private keys, or secrets. Turning sharing off stops future optional telemetry sync; local metrics may still be kept to show efficiency to you.
6. Connection and remote information
To route requests to the correct device, the system may process connector/device identifiers and required routing metadata. Private connection URLs/tokens must be protected as sensitive information and should not be published.
7. Website, cookies, and attribution
The website may use cookies or browser storage necessary for language preference, login sessions, security, and affiliate attribution. If optional analytics/marketing tools are configured, they must follow the configuration and disclosures applicable at the time of use.
8. AI providers and third parties
When you use ChatGPT, Claude, Grok, Mistral, or another service, data sent to them is governed by that provider's own terms and policies. A provider may process data in a different jurisdiction from where you live. Choose providers and data modes appropriate for the information you handle.
9. Purpose and retention principles
We should retain service data only for a reasonable period necessary for licensing/service delivery, accounting/transactions, security/fraud prevention, dispute handling, support, or legal obligations. Aggregate telemetry is designed to reduce identification of work content and is used for product analysis, system capacity, and resource allocation.
10. Security
ChatCode uses appropriate safeguards for supported local credentials, tokens, and communications; no system can guarantee absolute security. Users should protect devices, AI accounts, email, licenses, and connection URLs/tokens and should not send secrets to support unless an explicit secure process requires them.
11. User rights and choices
Depending on applicable law and the type of data, you may have rights to request information, access, correction, deletion/restriction, withdrawal of consent, or objection to certain processing. Withdrawing optional telemetry consent does not remove basic purchased usage rights and does not affect the lawfulness of processing performed before withdrawal where permitted by law.
Data requests can be submitted through the Contact page. We may need to verify identity before processing requests involving accounts or sensitive data.
12. We do not sell user work data
OzinTech does not design ChatCode around selling users' source code, prompts, chat history, or project data to advertisers. If the data-handling model changes materially, this policy must be updated before application as required by law.
13. Policy changes
This policy may be updated when the product, infrastructure, or law changes. The effective date and version appear at the top. Changes that legally require new consent will not be treated as accepted merely because you accepted a previous version where separate consent is required.