Privacy Policy
Effective September 10, 2026 · supersedes the version of August 31, 2026
1. Summary
This section is a plain-language overview. It does not replace the rest of the document, but nothing below contradicts it.
- Your source code, prompts and project files are never sent to Clodex. They travel from your machine directly to whichever coding agent you are running, under your own subscription with that provider.
- Your API keys and linked-service credentials are stored on your computer and are never transmitted to us.
- We receive your account details, the status of services you have connected, and counts of activity used to render your usage dashboard.
- The desktop application measures how it is used — which parts you open, how long a session runs, which agent and model you pick, and how often you do things. It does not record what you are working on.
- Your prompts, code, file contents, command output, agent transcripts and the names of your files, projects and directories are never measured and never transmitted. There is no screen capture, no session recording and no keystroke logging.
- You can ask us at any time to delete what usage measurement has recorded against your account. See sections 8 and 10.
- The application's own activity log is written to a file on your machine and is never uploaded.
- This website uses the Meta Pixel to measure our advertising on Facebook and Instagram. It sets a Meta cookie in your browser and tells Meta which of our pages you visit. It is not loaded for visitors in the European Economic Area, the United Kingdom or Switzerland, or if your browser sends Global Privacy Control or Do Not Track. See section 8.
To be completed before publication. The registered legal entity, its trading address, the governing law and venue, and where required an EU or UK representative are deliberately not stated in this document. They must be supplied before it is relied upon.
2. Information We Collect
All information described below is either provided by you directly or generated as a by-product of operating your account. There is no additional category of information gathered without your knowledge.
| Information | Purpose | Recipient |
|---|---|---|
| Email address, and the display name and photograph you choose to provide | To identify your account and represent you within the application | Clodex account service |
| Authentication data — a password hash, or an identifier from Google or GitHub sign-in | To authenticate you | Clodex account service |
| Subscription status — plan, state and renewal date | To license the application and process billing | Clodex account service, Stripe |
| Connection status — which services you have linked, whether each is connected, and a display label such as an account handle | To present your connections consistently across the application and the web dashboard | Clodex account service |
| Usage counts — the number of requests, deployments, messages or image generations attributed to each connected service | To render the usage dashboard and apply plan limits | Clodex account service |
| Correspondence you send to support | To respond to you | |
| IP address, recorded against sign-in, sign-up, password-reset and verification requests | To rate-limit those endpoints, which is what prevents password guessing and stops the mail sender being used as an amplifier | Clodex account service |
| In-application usage — which parts of the application you open and how often (for example the visual editor as against the terminal), when a working session begins and ends and how long it lasts, which coding agent and model you select, and counts of actions such as runs started, previews opened or dictation used | To learn which parts of Clodex are used and which are not, so that development effort and support go where they are needed | Clodex account service |
| Application environment — the version of Clodex you are running, your operating system and your processor architecture | To know which builds are in use, so that a support report can be answered against the right version and an old build can be retired safely | Clodex account service |
| Website activity — the pages you view on this website, the site that referred you (its address only, never the full link), your country, and whether you are using a phone or a computer | To understand which pages are read and where visitors come from | Clodex account service |
| Advertising measurement on this website — collected by the Meta Pixel, for visitors outside the European Economic Area, the United Kingdom and Switzerland: the pages you visit, the page that referred you, your IP address, details of your browser and device, and an identifier held in a Meta cookie | To measure whether our advertising on Facebook and Instagram brings visitors to Clodex | Meta, under its Business Tools Terms and privacy policy |
| Account events — when an account is created, verified or signed in to, when a checkout is opened, and when a trial starts, converts or is cancelled | To operate your account, to support you, and to understand how the service is taken up | Clodex account service |
| Downloads of the application — which build and platform you chose, your country, and the page you started from. Your email address is recorded only if you were signed in at the time | To know which builds are being installed, which is what makes a support report answerable | Clodex account service |
Connection status is a fact, not a secret. What is transmitted is the service name, a boolean value and a label — never the token, key or password behind it.
What in-application usage never contains. Your prompts. Your code. The contents of any file. The output of any command. The transcript of any agent run. The names of your files, your projects or the directories you open. Your screen, or anything you type into it. None of these is measured, none is transmitted, and none is held by us. We record the shape of your use of the tool — which parts, how often, how long — and never the substance of your work.
3. Information That Remains On Your Device
The following are written to the application-data directory maintained by your operating system and are read only by the application running on your computer.
- Every API key and service credential you enter, including those for Anthropic, OpenAI, Google AI, Stripe, Resend, Cloudflare and Render. Model-provider keys are expressly excluded from any synchronisation with our servers.
- Your session token, encrypted at rest using the credential protection provided by your operating system (Electron
safeStorage, which uses DPAPI on Windows and the Keychain on macOS). - Your application-activity log, comprising a daily count of prompts sent and the name of the directory you worked in most. This file is never uploaded, and the directory name never leaves your machine — it is not part of the usage measurement described in section 2, which records which parts of the application you used and never what you used them on.
- Your projects. Every file the agent reads, writes or executes remains in the directory you opened.
- Your conversation history, which the underlying coding-agent tool stores in its own directory beneath your home folder.
The application additionally removes ANTHROPIC_API_KEY from the environment supplied to the Claude Code process, so that a key present in your shell cannot silently transfer your work from your subscription to metered API billing.
4. Coding Agents And Your Code
Clodex is an interface to coding agents you already hold. When you submit a prompt, the application executes the relevant command-line tool on your machine, and that tool communicates with its provider directly. This traffic does not pass through our infrastructure and we cannot observe it.
- Claude Code transmits your prompt and any project context it reads to Anthropic, under your existing Claude login.
- Codex transmits the equivalent to OpenAI, under your existing login or key.
- Image generation, where you have supplied a key for it, sends your image prompt to OpenAI or Google AI according to the generator selected. Where a request includes a reference image — a crop, or a screenshot of your own interface taken by the design tools — that image is sent with it. The request is made from your machine using your own key.
The handling of that data is governed by the terms and privacy policies of those providers and not by this document. If your project contains information you are not permitted to disclose to a third-party model provider, you should not direct an agent at it.
5. Voice Dictation
Dictation is inactive unless you start it. When active, audio captured from your microphone is streamed to a broker service operated by Clodex, which forwards it to AssemblyAI for transcription and returns the resulting text.
The broker exists so that the shared transcription credential is not distributed inside the desktop application. It validates your session, issues a short-lived audio-only token, and enforces per-user rate and duration limits. Request URLs, credentials, audio and transcripts are not written to its logs. A refused request records the reason, the plan and a truncated hash of the account — enough to explain a rate-limit report, not enough to identify you from it. No recordings are retained.
6. Connected Services
You may link third-party services so that an agent can act on them at your instruction — pushing a repository, deploying a site, creating a payment link or sending a message. Linking is at your election and may be reversed at any time from Settings, then Connections.
- The credential is stored on your machine only and is used locally by the agent when you instruct it.
- We receive the status of the link and a running count of actions attributed to it. We do not receive the content of those actions.
7. Subprocessors
The following third parties are engaged in operating Clodex. Services you elect to connect are not listed, as those remain your own accounts under your own agreements.
| Provider | Purpose | Data involved |
|---|---|---|
| Stripe | Payment and subscription processing | Billing details, held by Stripe; we do not receive full card numbers |
| AssemblyAI | Speech-to-text transcription | Microphone audio, only while dictation is active |
| Render | Hosting for the dictation broker | Audio in transit; not logged |
| Cloudflare | Hosting for the website and account API | Standard request metadata, including IP address |
| Resend | Transactional email — address verification, password reset and account notices | Your email address and the content of those messages |
| GitHub | Distribution of application releases and updates | Your IP address when the application checks for or downloads an update |
| Google Fonts | Typeface delivery on this website | Request metadata, on the website only |
Anthropic, OpenAI and Google are not subprocessors of Clodex. You hold those relationships directly, under your own subscription or API key, and their traffic does not route through our infrastructure.
Meta is not listed because it is not engaged in operating Clodex. It receives the website data described in section 8 through the Meta Pixel and processes it under Meta's Business Tools Terms and its own privacy policy.
8. Cookies And Tracking
The desktop application measures how it is used. It records which parts of the application you open and how often, when a working session starts and stops, which coding agent and model you select, and counts of the actions you take. Those measurements are sent to us and are listed in section 2. This is our own software sending to our own servers: there is no third-party analytics package inside the application, no advertising identifier, and no data broker anywhere in the path. This website is different, and is described below.
It does not record what you are working on. Your prompts, your code, the contents of your files, the output of your commands, the transcripts of your agent runs, and the names of your files, projects and directories are not measured, not transmitted and not stored by us. There is no screen capture, no session recording and no keystroke logging. The line is between the shape of your use of the tool and the substance of your work, and only the first side of it reaches us.
If you would rather we did not. Usage measurement is part of how the application works and is not separately configurable; it applies for as long as you hold an account. You can ask us at any time to delete what has been recorded against your account — write to support@useclodex.com, you do not have to give a reason, and nothing you can do in Clodex changes as a result. If you would prefer that it did not continue, you can cancel your subscription at any time from your account; access ends when the period you have paid for does, and the measurement ends with it. Section 10 sets out the rights you may hold under your own law, including the right to object to processing, and those are honoured whatever this section offers. Records that are the product rather than a study of it — your plan, your trial state, whether you are signed in — continue while the account exists, because those are how your subscription works; section 2 describes them separately.
On this website we set one cookie of our own, to maintain your signed-in session. We also count page views and downloads, again using our own software on our own infrastructure, and that counting stores nothing on your device: no analytics cookie, no local storage, no advertising identifier. To count visitors rather than requests we derive a temporary identifier from your IP address and browser using a secret value that changes every day; your IP address itself is never stored beside that data, and because the secret rotates daily the identifier cannot be linked from one day to the next. We record the page viewed, the referring site (its address only, never the full link), your country, and whether you were on a phone or a computer.
We honour the Do Not Track and Global Privacy Control browser settings. With either switched on we record no page views and no downloads, the Meta Pixel described below is not loaded, and nothing at all is stored.
The Meta Pixel. This website also loads the Meta Pixel on its pages, a script provided by Meta, so that we can tell whether our advertising on Facebook and Instagram brings people here. It is not loaded at all for visitors in the European Economic Area, the United Kingdom or Switzerland: we tell where you are from the country your connection comes from, and where we cannot tell, it is not loaded. It sets a cookie named _fbp, and _fbc when you arrive from one of our Meta ads, which let Meta recognise later visits from the same browser. Each time you view a page it sends Meta the address of that page and of the page that referred you, together with what your browser sends with any request, including your IP address and details of your browser and device. We have set it to report page views only, not the buttons you select or what you type into a form, and we do not give Meta your name, your email address or anything else from your Clodex account. Meta may connect this information with a Facebook or Instagram account signed in on the same browser, and uses it under its Business Tools Terms and privacy policy, including to measure, target and deliver adverts.
We do not sell personal data. Sending website activity to Meta in this way is, under some laws, “sharing” personal information for cross-context behavioural advertising. Switching on Global Privacy Control opts you out of it on this website automatically. You can also block or delete these cookies in your browser, and opt out of interest-based advertising through Your Online Choices or the Digital Advertising Alliance.
9. Retention
- Account data is retained while your account exists and is deleted when you delete it.
- Usage counts are retained as a rolling history so the dashboard can display trends.
- In-application usage and website activity are retained as daily aggregates. Once aggregated they hold no direct identifier.
- Information received by Meta through the Meta Pixel is held by Meta under its own retention policies. We receive only the aggregated reports Meta provides.
- Account events, downloads and trial records are anonymised rather than erased when an account is deleted: the account reference and the email address are removed, and what remains — which build, which day, whether a trial converted — is kept so that historic totals do not change retroactively. Nothing in a row that survives identifies you.
- Rate-limiting records, including the IP address they are keyed on, expire with the window they belong to — an hour in most cases — and are swept from the database thereafter.
- Billing records are retained for the period required by tax and accounting law, typically several years.
- Dictation audio is not retained.
- Data held on your machine remains yours for as long as you keep it.
10. Your Rights
Depending on your jurisdiction you may have the right to access, correct, export or delete your personal data, to object to or restrict its processing, and to lodge a complaint with a supervisory authority. Contact us to exercise any of these and we will respond within the period prescribed by the applicable law.
We do not sell personal data. The Meta Pixel described in section 8 shares website activity with Meta for advertising measurement, which some laws treat as sharing for cross-context behavioural advertising. Switching on Global Privacy Control opts you out of it on this website, and section 8 describes the other ways to opt out.
11. Children
Clodex is a professional development tool and is not directed at children. We do not knowingly collect personal data from any person under the age of 16. If you believe a child has provided us with personal data, contact us and we will delete it.
12. Changes And Contact
Where this policy changes materially — for instance through the addition of a subprocessor or a new category of data — the revision date will be updated and, for significant changes, account holders will be notified by email. Continued use of Clodex after a change constitutes acceptance of the revised policy.
Privacy enquiries and data requests: support@useclodex.com.
- Terms of Service — what you are agreeing to, and who owns the code.
- Security — credential handling, permission modes and residual risks.
- Contact & Support — to raise a privacy question or data request.