Your code stays on your machine
Codelux AI works on your computer. Our server knows who you are and what you are licensed for, and nothing about your code. When a team shares work, it is encrypted so that only the team can read it. Here is what goes where, and why.
Four places your data can be
From the most private to the least. Most of what you do never leaves the first one.
Stays with you
- Your source code
- The project's memory, notes and history
- The app itself and its screens
- The keys of your AI providers and of your team
Why: this is your work. We have no reason to see it, and we never receive it.
Only to run your account
- Your name, e-mail and password (stored scrambled, never readable)
- A licence check: an anonymous fingerprint of your computer and of the app
- The names of your projects and the folder they are in — never the files
- A payment reference; card details stay with Stripe
Why: to sign you in, apply your plan to your projects and stop a licence being copied to other machines.
Shared, encrypted end to end
- Shared memory, notes, history, tasks, standups and chat
- Encrypted on the author's computer, opened on teammates' computers
- Our server passes them along and stores them, unreadable
- We see only who sent something, when, and how big it was
Why: so colleagues' agents work from the same knowledge without us being able to read it. The key is created in the team owner's app and never sent to us.
Between you and them
- Your AI tool talks to its provider (Anthropic, OpenAI, Google…) directly
- Nothing of that conversation passes through Codelux AI
- We keep no record of your AI requests
Why: Codelux AI sits next to your AI, not in the middle. Usage and cost figures are read on your computer, as numbers only.
If the owner's master key and every copy of a team key are lost, the team's shared data on our server can no longer be read — by the team or by us. That is why the owner's app asks to keep a copy of the master key when it is made.
What we measure when you visit
Three levels, and you choose the optional one.
Always on: what the site needs
Your sign-in, your cookie choice and your light or dark theme. Nothing else.
Without cookies: page counts
Which public pages are visited and where visitors come from, with a key that changes every day and cannot be traced back to you. Raw records are deleted after 14 days.
Only if you agree: analytics
Anonymous visit counts, with no third-party tools. Off until you switch it on; you can change your mind at any time.
How your account and your work are protected
Sign-in with a code
A password sign-in also asks for a one-time code sent by e-mail. You can sign in with Google, GitHub or Slack instead.
Company sign-in
On Team and Enterprise: single sign-on through your identity provider, automatic removal of people who leave, and two-step sign-in the admin can make mandatory.
Secrets tied to your computer
Your sign-in and keys are sealed to your machine: a copy taken elsewhere does not open.
Encrypted connections
Everything between the app and our server travels encrypted, and the app checks that the replies really come from us.
A record of every change
The history shows who changed what, with which agent and when. Team owners and admins can export a full audit.
Your own server, if you prefer
Teams can run on their own company server instead of ours, with their own access keys for connected tools.
Where our part runs
No AI provider is among them: we send them nothing.
| Company | What for | Where |
|---|---|---|
| Kamatera | Our server: website, accounts, team relay | Frankfurt, Germany (EU) |
| Cloudflare | Delivering the website safely | USA, global network |
| Dynadot | E-mail: sign-in codes, invitations, receipts | USA |
| Stripe | Payments | USA |
Transfers outside the EU are covered by Standard Contractual Clauses. Retention periods and the full list are in the privacy policy.
Limits you should know about
Certifications and tests
- No SOC 2 or ISO 27001 certification yet.
- The penetration tests of September 2026 were done by us, not by an independent firm.
On your computer
- The app needs an internet connection to check your licence; there is no offline mode yet.
- The project data on your disk is not encrypted by the app, like other developer tools: use your system's disk encryption.
- The app is not code-signed yet, so your system may warn you the first time you open it.
Security documents
The technical detail — encryption, keys, identity, logging — is in these files, free to download and forward to your review. A countersigned DPA is available on request.
Found a vulnerability?
Write to [email protected] with the subject “Security”, and please do not open a public issue. We reply within 3 business days and send a fix or a plan within 30 days for confirmed issues. Rules and scope: the responsible disclosure policy.
Evaluating Codelux AI for your company?
Ask for the DPA, a call with the security questionnaire in hand, or a one-month pilot.