Privacy

Who we are

Codee3 is run by Jeremy Linton, sole trader, Victoria, Australia, trading as Codee3, ABN 80 516 644 158. For anything on this page, contact Hello@Codee3.dev.

The Codee3 IDE: what leaves your computer, and when

The update check (testers only)

Only after you have entered a tester code, in Settings › Updates & diagnostics. Then it runs each time Codee3 opens, unless you turn off Check when Codee3 opens, and whenever you press Check for updates. Without a code the tester build makes no update request at all, and the free IDE has no updater, so it never asks.

It sends your tester code, the version of Codee3 you have, your system and your processor type to www.codee3.dev, which Cloudflare hosts. Like any web request, it also reveals your IP address. Each code is issued to a name; our server keeps a fingerprint of the code (a SHA-256 hash) with that name, not the code itself, and our code does not record each check. Cloudflare keeps its own request logs; we have not verified what they hold or for how long.

We keep a code’s name and fingerprint while the code is active, and delete them within 90 days after it is cancelled.

Diagnostics (only when you press Send)

Only when you open Send diagnostics… and press Send. The sheet shows you every byte first, and nothing is sent on its own. After a crash, Codee3 offers the report the next time it opens; it still waits for you.

A report holds the problems Codee3 wrote down on your computer, scrubbed first (your home folder becomes ~, anything shaped like a key or a code is blanked, and each message is cut short); the versions of Codee3, Windows, WebView2 and your AI apps; how many projects and repositories you have, not their names; your note; and the ideas waiting in your ideas box. Folder and project names below your home folder can still appear in a problem line.

Send needs a tester code. A report is filed privately, in Cloudflare’s storage, under the name your code was issued to: at most 1 MB, and at most 20 a day. We delete a report within 90 days of reading it. Save to a file writes the same report to your computer and sends nothing.

The extension library

On by default. When it is on, the IDE downloads the signed list of extensions from www.codee3.dev/extensions/, and any extension you choose to install. These requests carry no code and no name; they reveal your IP address to our host. You can turn the library off in Extensions. An extension you install may connect to the internet addresses it declares, which you approve when you install it.

Installing an AI app (only when you press Install)

If you press Install in Settings › AI apps, Codee3 opens a terminal and runs that vendor’s own installer, which you can watch: Claude Code from Anthropic, or Codex from npm, installing Node.js through Microsoft’s winget first if it is missing.

Your code, prompts and conversations

When you chat with Claude Code, Codex or Gemini CLI in Codee3, you are using that provider’s own app, signed in with your own account. What you send goes to the company behind that app, under its terms and privacy policy. Codee3 sends it nowhere else. Codee3 never sees, stores or relays your Claude, ChatGPT or Google sign-in: you sign in with the provider’s own tool.

In the tester build, opening a chat with Claude Code first runs a short sign-in and model check in Claude Code, which asks no model anything and sends no prompt. Codee3 shows the plan it reports and never keeps your email. The free IDE does not run this check, and reads no plan or usage.

Nothing else

There is no usage analytics, no automatic crash reporting and no advertising in the IDE.

What stays on your computer

Your settings, your tester code, Codee3’s event and audit logs, your recorded decisions, the diagnostics log (its last 2 MB) and your ideas box are kept as plain files in Codee3’s folders under your Windows account. They are not encrypted; your Windows account is what protects them. Uninstalling may leave these folders behind (%APPDATA%\com.codee3.ide, %LOCALAPPDATA%\com.codee3.ide and .codee3 in your home folder); delete them to remove everything.

The Brain Kit (testers)

The Brain Kit’s guards run on your computer and in your own CI. Its only network request is an optional cached update check for release information (npm run brain:check:updates), at most once per 24 hours, sending no repository content, and failing quietly when there is no connection.

Codee3 measures repository knowledge structures, not developers. There are no per-developer metrics, no rankings and no leaderboards.

This website

This website sets no cookies, except one when a customer signs in to their account (below), and runs no advertising. It does use analytics, to understand which pages are useful, where visitors arrive from and how quickly pages load. One script runs in your browser when you open a page:

• Cloudflare Web Analytics, from our hosting platform: page views, referring sources and page-speed measurements, loaded from static.cloudflareinsights.com.

Cloudflare describes it as cookieless. What it records is stated by Cloudflare, in its own documentation, not by us; we have not audited it.

We also count clicks on the download button, as a number only: one count for each day and installer file, kept in Cloudflare’s storage with nothing about who clicked.

If you join the email list, your address is emailed to our inbox through Resend, and a fingerprint of it is kept in Cloudflare’s storage so sign-ups can be counted. If you ask on the Download page to hear when Codee3 comes to macOS or Linux, which one you asked about is emailed with it. We use it only to tell you about releases, including that one, and, later, paid features. It is not sold. To leave the list, email Hello@Codee3.dev. Every email we send to the list names us and says how to leave. We keep your address until you leave the list, and delete it within 30 days after you leave.

This site does not track you across other sites, so it does not respond to Do Not Track signals differently.

Your Codee3 account (customers)

If you buy Codee3, you can sign in at www.codee3.dev/account with the email address you bought it with. There is no password. We email you a six-digit code through Resend; it works once, for 10 minutes. A bot check, Cloudflare Turnstile, runs on the form that asks for the code, and Cloudflare sees your browser and IP address to do it.

Polar (polar.sh) is our merchant of record. It takes the payment and holds your name, email address, billing address, payment details, invoices and licence key. When you are signed in, we ask Polar for your plan, its renewal date and amount, your licence key and your computers, show them to you, and keep none of it. Changing your card and your invoices are on Polar’s own pages. The Codee3 IDE may ask this site for your renewal date with your licence key, to remind you itself; we ask Polar and keep nothing.

We keep a sign-in code only as a keyed hash: a fingerprint that can’t be turned back into the code, or checked against a guess, without our secret key. It is filed under a keyed hash of your address, never the address itself (it is pseudonymised, not anonymous). How often an address, or an IP address, has asked for a code is counted the same way. Both are deleted within two days.

Signing in sets one cookie, __Host-codee3-account. It keeps you signed in for 7 days, and holds Polar’s id for you and a random session id, signed so that it can’t be changed. It is strictly necessary to keep you signed in, so it needs no consent. It is set only if you sign in, and signing out clears it.

About 35 days before each yearly renewal, and 21 days before any charge higher than your last, we email the address Polar holds for you: the date, the amount, and how to cancel. If you cancel, we email you a confirmation. To never send one twice, we keep Polar’s subscription id and which email went out, until a year after that renewal.

If your billing address is in Germany, you can also cancel without signing in („Verträge hier kündigen“); in the EU or EEA you can withdraw within 14 days of buying („Vertrag widerrufen“, “Withdraw from contract here”). Either form asks for your email address and licence key (and, to withdraw, your name), and a bot check, Cloudflare Turnstile, runs on it. We check them with Polar and email the confirmation to the address Polar holds for you, with a link that undoes it, once. To prove what was declared and when, we keep a record of it for three years: when it arrived, which subscription, the kind of cancellation and any reason you gave. We don’t keep your name. Where the form is offered depends on your billing country, or before you sign in, on the country Cloudflare reports for your connection, which we don’t keep.

On your account page you can download what this site holds about you, and delete it. Deleting removes your sign-in code, its counts and the fingerprint of your address on our email list (if you joined the list, email us to remove its copy in our inbox too). We keep, while your subscription runs, what your licence needs (a hash of your licence key and of each computer’s install id, with Polar’s id for that activation) and the record of which renewal emails went out; we keep a cancellation or withdrawal record for its three years; and we keep the list of keys and subscriptions Polar revoked, so they stay refused. Polar keeps its own records as merchant of record.

We hold your account, the renewal emails and the licence because our contract with you needs them (GDPR Article 6(1)(b)); the bot check and the limits on how often a code can be asked for protect the service (our legitimate interests).

Where your data is held

Our providers are Cloudflare (this site, the update check, diagnostics, the extension library, analytics and the bot check on the account’s sign-in), Resend (email delivery), Polar (payments, as merchant of record, for customers) and Google (the inbox list sign-ups reach). Some of them hold data outside Australia: Cloudflare serves this site from data centres around the world, including the United States, and holds this site’s data, diagnostics and sign-up fingerprints in its storage. Our providers protect data sent abroad through their own contractual safeguards, such as the EU’s Standard Contractual Clauses.

We make no automated decisions about you.

Your choices

• Turn off the update check at opening, or remove your code, in Settings › Updates & diagnostics.
• Turn off the extension library in Extensions.
• Use Save to a file instead of Send.
• Ask us what we hold about you, to correct it, or to delete it, by emailing Hello@Codee3.dev. A customer can also download or delete what this site holds about them on their account page.
• Where we rely on your consent, you can withdraw it at any time, by leaving the list or asking us to delete a report. Withdrawing it does not affect what was done before.
• If you are in the EU or the UK, you have rights under the GDPR, including access, correction, deletion, restriction, portability and objection, and you can complain to your data protection authority. We rely on legitimate interests for the update check and the extension library, on your consent for diagnostics and the email list, and on our contract with you for a customer’s account, renewal emails and licence.

Changes

If this notice changes, the date below changes, and anything that changes what leaves your computer is said in the release notes of the version that does it. The licence terms are on the terms page.

Last updated: 19 October 2026.