Privacy statement
Collects nothing.
Sirius collects nothing. This is the repository's statement, rendered word for word.
Rendered from PRIVACY.md in the repository, so this page and that file are always the same text.
Sirius IDE collects nothing. There is no telemetry, no crash reporting, no usage analytics, and no account.
This is not a setting you have to find and turn off. There is no code in Sirius that reports anything about you anywhere.
What leaves your machine, and only when you ask
Sirius talks to a model provider when you send it something — a chat message, an inline edit, a completion. What goes with that request is what the model needs to answer:
- the text of your prompt
- whatever context you attached or the editor included (a selection, a file, a tool result)
- the contents of files a tool read, if the model called one
That request goes directly from your machine to the provider you chose. Sirius operates no proxy and no relay, so nothing routes through us and there is nothing for us to log.
Your use of a provider is governed by your agreement with that provider, not by this document. Their policies are the ones that apply to what you send them:
| Provider | Policy |
|---|---|
| Anthropic | https://www.anthropic.com/legal/privacy |
| Google (Gemini) | https://policies.google.com/privacy |
| OpenAI | https://openai.com/policies/privacy-policy |
| OpenRouter, Groq, DeepSeek, Mistral, xAI | see each provider’s own policy |
Nothing leaves your machine at all, if you want
Ollama, LM Studio, llama.cpp and vLLM run models on your own hardware. Configure one of those and no prompt, file or fragment of code reaches any third party.
Your API keys
Keys are kept in the editor’s secret storage, encrypted with your operating system’s own facility — DPAPI on Windows, the Keychain on macOS, libsecret or KWallet on Linux. On a Linux desktop with no keyring available, the editor says so and asks before falling back to weaker encryption.
Keys are never written to settings.json, never synchronised, and never sent
anywhere except to the provider they belong to. Earlier builds did store them in
settings.json; if you used one, Sirius moves that key into the keyring on
startup and clears the setting.
What Sirius stores locally
Ordinary editor state, in your profile directory: settings, keybindings, extensions, workspace history, chat history. It stays on your machine.
Extensions
Sirius ships with the Open VSX marketplace. Extensions you install are third-party software with their own behaviour and their own privacy practices. Nothing in this document constrains what an extension does.
Update checks
Every Sirius install checks for updates — 30 seconds after it starts, then
hourly — by asking update.siriuside.com whether a newer build exists. The
request names the platform, the release channel and the build commit you run,
which is enough to answer the question, and carries the headers any request
carries, including a User-Agent that names the editor and the operating system.
It contains no identifier for you or your machine. The update server is a
Cloudflare Worker that writes no logs; Cloudflare’s own handling of the request
is covered by its privacy policy.
Installs from a distribution package — the .deb, the .rpm, the [sirius]
pacman repository — make the same check, even though your package manager is
what installs the update.
To turn the check off, set "update.mode": "none" in your settings, or
"manual" to check only when you ask.
Changes
Material changes to this document will be noted in the release notes.