Data Use
A plain account of where your data lives, what we store, and what we don't. For the full legal text, see the Privacy Policy.
What stays on your machine
- 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
.atlarixfolder 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.
What goes to AI providers
- 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.
What we store
Our hosted infrastructure stores only account and billing data — never code.
| Data | Where | Retention |
|---|---|---|
| Email, name, profile picture | Supabase (US/EU) | Until you delete your account |
| Subscription tier and credit balance | Supabase (US/EU) | Until you delete your account |
| Payment details | LemonSqueezy (we never see card data) | Per LemonSqueezy's policy |
| Product analytics | PostHog (EU) — opt-in only | 12 months |
| Error reports | Sentry — sent regardless of the analytics setting | 90 days |
| Encrypted database backups (includes account records) | Cloudflare R2 — encrypted before upload; we hold the only key | Rolling nightly |
| Atlarix Core requests in transit | Railway (our proxy) and OpenRouter (routes to the serving model) | Not retained by us |
| Account emails we send you | Resend | Per Resend's policy |
| Website hosting and DNS | Vercel (hosting), Cloudflare (DNS only — it does not proxy or inspect traffic) | Standard request logs |
| Website analytics | Google Analytics 4 and Tag Manager (atlarix.dev only, not the app) | Per Google's policy |
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 product analytics without your consent — it is opt-in, and off until you say yes
One thing that setting does not cover: crash and error reports are sent whether or not you opt in to product analytics. They carry stack traces and device information — never your code, prompts, or file contents — and we use them only to fix crashes. The app says so at first run and in Settings.
Questions about how your data is handled? Contact us at support@atlarix.dev.