Privacy Policy

Overview

This Privacy Policy describes how Codeo3 — the web platform at codeo3.com and the Codeo3 desktop application for macOS, Windows, and the Microsoft Store — collects, uses, stores, and shares information. Codeo3 is operated by Gold Fleece Ltd. (“Codeo3”, “we”, “us”).

Codeo3 is a development workspace: you create projects in CodeBuilder with AskCodeo (our built-in AI assistant), render them live, publish or share them, and collaborate through Codeo Chat. Because Codeo3 combines cloud features with local AI and local files, this policy distinguishes carefully between information that stays on your device and information that is transmitted to our servers or third-party providers.

Information We Collect

• Account information: email address, username, display name, avatar, bio, and other profile details you provide when registering or editing your profile.
• Age eligibility: your date of birth is requested during email sign-up to verify you meet the minimum age. It is stored in a private account-verification record, not displayed on your public profile.
• Project content: the source code, blocks, files, titles, descriptions, and metadata of projects you create in CodeBuilder or with AskCodeo, including C3 Cinema scenes and other generated content, stored in your account.
• Collaboration and social data: friend relationships, follows, Codeo Chat messages (direct and shared-project conversations), comments, likes, ratings, reports, and message-privacy settings you choose.
• Usage and technical data: pages visited, features used, events such as project creation or publishing, error reports, IP address (used for security and rate limiting), browser and device type, operating system, and app version.
• AI usage records: operational metadata about AI requests you make — token counts, model identifiers, block and line counts, timing, and success/failure status — used for metering, reliability, and abuse prevention. We do not store the text of your AI prompts in these usage records.
• Payment information: purchases and subscriptions are processed by Stripe. Codeo3 receives and stores your entitlement status and transaction references — never your full card number, which Stripe handles directly.
• Integration data: if you connect optional integrations (for example GitHub), we store the connection metadata and tokens needed to operate that integration.
• Wallet and token features: if you use the optional wallet and creator-token features, we store your public wallet address, connection disclosures, and related on-platform transaction metadata. Private keys are never collected or stored.
• Legal acceptances: records of the terms and disclosures you accept, including version, timestamp, IP address, and user agent.
• Cookies and similar storage: essential storage for authentication, security, and preferences. Optional analytics storage is disabled unless you enable it — see our Cookie Policy.

What Stays on Your Device

Several parts of Codeo3 are deliberately local-first. The following information is processed on your computer and is not transmitted to Codeo3 servers unless a feature explicitly sends it:

• AskCodeo chat history: your AskCodeo conversation transcripts are kept in your browser or desktop storage so they survive reloads. They are not stored in a Codeo3 conversation database.
• Local Files and local projects: projects stored in folders on your computer (by default under Codeo3/Projects) are read and written only inside the folder you authorize. The desktop app enforces path confinement and rejects requests that escape the project folder.
• C3 Local AI: when you install and use the C3 Local model, inference runs entirely on your own hardware. Prompts and outputs processed by C3 Local are not sent to Codeo3 servers.
• Desktop application data: app settings, window state, signed-in session tokens, and bridge configuration are stored in the desktop app's local data directory on your computer.
• Local bridge servers: the desktop app runs small servers bound to your computer's loopback address (127.0.0.1) to connect the editor, previews, and the codeo3 CLI/agent bridge. They are token- or origin-gated and allowlisted to specific actions.

Local data remains yours: uninstalling the desktop app does not delete your project folders, and deleting project folders is your choice.

How AI Features Process Information

AskCodeo is the AI assistant built into Codeo3, served by a Codeo3-managed model runtime. When you send a prompt to AskCodeo, your message together with relevant project context — such as the code blocks or file excerpts needed to answer — is transmitted to our servers solely to generate a response. We do not use provider accounts in your name and you never supply model API keys.

After each request we record operational metadata (tokens consumed, model used, counts of blocks read or changed, timing, and success or failure) under your account for metering and reliability. Prompt and response text is not written to those usage records.

If you prefer prompts never leave your device, C3 Local AI provides on-device inference inside the desktop app. Signed-out visitors may also try a limited number of guest prompts, which are processed by the same server pipeline.

Public, Shared, and Private Content

• Public profiles: your display name, username, avatar, bio, published projects, and public activity are visible to others by design — Codeo3 is a creation and discovery platform.
• Published projects: publishing a project makes its content publicly accessible. Other users can run, view, share, and — where enabled — remix it, which copies the source into their own workspace.
• Shared projects: collaborators you invite can access the project according to their role (editor or viewer). Shared-project chat is visible to all current collaborators of that project.
• Direct messages: Codeo Chat direct messages are visible to participants. Your message-audience and privacy settings control who can start conversations with you.
• Drafts and private projects: unpublished projects are visible only to you and the collaborators you add.
• Sensitive values: project environment secrets are stored server-side and returned only as masked previews; secret values are never included in AI context or API responses.

How We Use Information

• Providing and operating the platform, the desktop app, and AI features
• Storing and rendering your projects and enabling collaboration
• Authenticating your account and enforcing age eligibility
• Processing purchases, subscriptions, and entitlements
• Preventing fraud, abuse, and security threats, and enforcing our policies
• Communicating with you about the service, updates, and support
• Analyzing aggregate usage to improve the product (where optional analytics is enabled)
• Complying with legal obligations

We do not sell your personal information and we do not use your private project source or AI prompts to advertise to you.

Service Providers and Sharing

We share information with service providers only as needed to operate Codeo3:

• Google Firebase — authentication, databases, and file storage hosting your account, projects, and social data.
• Stripe — payment and subscription processing; Stripe receives payment details directly under its own privacy policy.
• Vercel — hosting and delivery of the web platform.
• GitHub — desktop update distribution and, if you connect it, repository integration.
• Microsoft — distribution and update delivery for the Microsoft Store package of the desktop app.

We may also disclose information where required by law, to protect rights and safety, or in connection with a business transfer. Service providers are limited to processing for the purposes of providing or protecting the service.

Data Retention and Deletion

• Active accounts: account, project, and social data is retained while your account is active.
• Projects: you can delete individual projects at any time; deletion removes the project and its cloud-stored content.
• Account deletion: to delete your account and associated personal data, contact us at contact@codeo3.com or through our Contact page. We will process verified deletion requests without undue delay; some records may be retained where required by law or for fraud prevention.
• Local data: project folders, desktop settings, and on-device chat history are deleted by removing them from your device — they are not held on our servers.
• Aggregated analytics: usage statistics are aggregated and de-identified over time.

Your Rights

Depending on where you live, you may have the right to:

• Access, correct, or export your personal information
• Request deletion of your information
• Opt out of optional analytics and non-essential storage
• Object to or restrict certain processing
• Withdraw consent where processing is based on consent

To exercise these rights, contact us at contact@codeo3.com or through our Contact page.

Security

Codeo3 uses technical and organizational measures including encrypted transport, scoped access controls, sandboxed project runtimes that cannot read your account credentials, path-constrained local file access, token-gated local bridge servers, and masked handling of project secrets. Agent access tokens are stored as hashes and expire automatically.

No security system is completely secure. Protect your account credentials and device, and contact us promptly if you suspect unauthorized access.

International Processing

Information may be processed in countries other than your country of residence, including where our service providers operate. Those jurisdictions may have different data-protection laws. Where required, we use appropriate safeguards for international transfers.

Children's Privacy

Standard Codeo3 accounts are limited to users age 13 and older, and you must also meet any higher minimum age that applies where you live. We do not knowingly collect personal information from children under 13. If we learn that an account holder is under 13, we will restrict or delete the account and associated personal information as required by law.

Changes to This Policy

We may update this Privacy Policy as the product evolves. The “last updated” date above reflects the current version. Material changes will be communicated through the service or by other reasonable means. Continued use after an update takes effect constitutes acceptance of the revised policy.