Data Use

• Your code — files are read and edited locally. We never upload your source code to our servers.
• Workspace settings — your project configuration, rules, and preferences live in a local .atlarix folder inside your project.
• Conversation history — chat sessions are stored locally in an SQLite database on your machine.
• API keys you bring — stored in your OS keychain (macOS Keychain, Windows Credential Manager, or the system secret store on Linux). Never sent to Atlarix servers.
• Local model inference — when you connect Ollama, LM Studio, or any local endpoint, all inference stays on your hardware.

• Atlarix Core (default) — unless you set up your own models, Atlarix runs on Atlarix Core. Your request passes through our authenticated proxy, which verifies your account before anything is sent — we don't log or retain the request. From there it goes directly to the model provider that serves it, who processes it under their own data policy. We don't have zero-retention agreements with these providers, so we can't guarantee what they keep. See our Models page for how models are connected in Atlarix.
• Local models (you set up) — run a local model — for example through Ollama — and your code and prompts never leave your machine. Nothing is sent, stored, or logged — by us or anyone.
• Your own API key (you set up) — add your own provider key and requests go directly to the provider you chose. Atlarix acts as a local client; we never see the traffic.

Training: We never train on your code, in any mode.

Our hosted infrastructure stores only account and billing data — never code.

We do not

• Train on your code or prompts
• Log or retain prompt content on our proxy
• Store your source files on our servers
• Share your data with third parties for advertising
• Sell your personal information
• Collect analytics without your consent