Legal
Privacy policy
Last updated 1 November 2026
kwant.si is a static website about kwant, free software you run yourself. The website sets no cookies and doesn't track you across sites; it counts page views with Cloudflare's cookie-free analytics. The software has no telemetry: it sends nothing to us, and we can't see what you do with it.
Who is responsible
kwant.si is run as a private open-source project. For anything about this policy or your data under the EU General Data Protection Regulation (GDPR), write to [email protected]. The terms of use cover the license, trademarks and security reports.
This website
Hosting
kwant.si is served by Cloudflare Pages. When you open a page, your browser sends Cloudflare the usual request data: your IP address, the page address, date and time, browser and operating system (user agent) and the referring page. Cloudflare needs this to deliver the page and protect the site from attacks, and keeps it in short-lived logs under its own privacy policy. Cloudflare can also receive network error reports from your browser when a page fails to load. We don't see these logs as personal data and we don't combine them with anything else.
The legal basis is our legitimate interest in running a secure, working website (Article 6(1)(f) GDPR). Cloudflare is a processor for us and may process data outside the EU; Cloudflare relies on the EU-U.S. Data Privacy Framework and standard contractual clauses for this.
No cookies, one privacy-first analytics script
The site sets no cookies and doesn't track you across sites. To count page views we use Cloudflare Web Analytics: each page loads a small script from Cloudflare's server (static.cloudflareinsights.com), which reports the page address, the referring page, your browser and how fast the page loaded to cloudflareinsights.com. Cloudflare also works out your country and device type from the request; we don't store your IP address. It sets no cookies, uses no local storage and doesn't fingerprint your browser, so we only see totals, not individual visitors. Cloudflare processes this as our processor, on the same legal basis as hosting.
Apart from that script, the site loads no fonts, scripts or images from other servers. Its Content-Security-Policy only allows files from kwant.si and those two Cloudflare analytics addresses. There are no forms.
Links to other sites
Links to GitHub (the source code, issues and the Mac app download) take you to GitHub, which processes your data under the GitHub privacy statement.
The kwant software
You install kwant on your own computer or server and you are in charge of it. Your bots, chats, files, memory, accounts and passwords are stored there, in kwant's data folder (~/.kwnt by default). We don't operate any kwant service, and nothing you do in kwant reaches us. If you run kwant for other people, you are the controller for their data.
What kwant connects to on its own
Without any setup, kwant makes only these connections:
- Routing model (Laya). On first start, kwant installs its local routing model: Python packages from PyPI and the PyTorch download server, a Python installer (uv, from Astral via GitHub) if your computer has no Python, and the model files (about 420 MB) from Hugging Face. These servers see your IP address. After that the model runs on your machine. Start kwant with
--no-layaor setKWNT_LAYA_MANAGED=0to skip it. - Update check (desktop app only). The kwant desktop app asks GitHub whether a newer version is out: 15 seconds after it starts, then every 6 hours, and when you click Check for updates. It downloads one small file (
latest.json) from kwant's GitHub releases. GitHub sees your IP address and the updater's name and version (tauri-plugin-updater), not your kwant version or anything in your kwant, under the GitHub privacy statement. An update is downloaded only when you choose to install it, and its signature is checked before it replaces the app. There is no setting to turn the check off. kwant started from the command line or in Docker doesn't check.
The web interface and the Mac app use fonts that ship with kwant and load nothing from other servers. There is no crash reporting or usage statistics.
What kwant connects to when you set it up
Everything else happens only after you add an account, a connection or a tool, and sends what you or your bots give it to that service, under that service's terms:
- AI model providers you sign in to or add a key for, directly or through their command-line tools: Anthropic (Claude), OpenAI (ChatGPT, Codex), xAI (Grok), Google (Gemini), OpenRouter and any compatible server you enter. Your messages, files the bots read and tool results go to the provider you chose.
- Installing tools with
kwnt setupor the in-app setup: npm, Homebrew, the Claude, Codex and Grok installers, Playwright's browser download, and Docker if you ask for it. - MCP servers and connectors you add, such as Composio, Notion, Linear or GitHub. Bots can also search the public MCP Registry by name to suggest a server; nothing is installed without you.
- Loose ends sources you turn on: your email server (IMAP, read-only) and the GitHub API.
- Passwords: Bitwarden, if you connect a vault.
- Phone notifications: ntfy or the server you set, if you add a webhook; and your browser's push service (Google, Apple or Mozilla), if you turn on notifications on a device. The push service relays them encrypted and can't read them.
- Websites your bots visit with the bot browser or web search. Those sites see a normal browser visit from your computer or server.
Your rights
Under the GDPR you can ask us for access to your personal data, and for correction, deletion, restriction of processing or a copy of it, and you can object to processing based on legitimate interest. Write to [email protected]. Because we don't keep website logs ourselves, we usually hold no data about you; for Cloudflare's logs we will pass your request on.
You can also complain to a data protection authority. In Slovenia that is the Information Commissioner (Informacijski pooblaščenec), Dunajska cesta 22, 1000 Ljubljana.
Changes
We update this page when the website or the software changes what it sends. The date at the top shows the last change, and the history is on GitHub.