Privacy
Not yet a complete privacy policy
In short
| Area | What is processed | Where | What is not known yet |
|---|---|---|---|
| Local processing | Prompts, code, replies, memory, traces and model files | Your computer. KOLDOS sends no telemetry | How updates will be delivered |
| Optional external services | Search queries and requests for the pages KOLDOS reads | Public search engines, through SearxNG on your computer | What each search engine or site records |
| Developer API | Whole requests and responses, plus usage records | The hosted KOLDOS service, which has not started | Retention of logs and request contents |
| Authentication | Discord user ID, username and avatar | The KOLDOS account service | What is stored and for how long |
| This website | Preferences and checker inputs in your browser | Your browser, plus host access logs | Hosting provider and log retention |
Local processing
KOLDOS runs the model, the tools and the memory on your computer. Prompts, your code, the memory database (one per project) and the trace of every turn are stored on your disk. KOLDOS is designed with no outgoing telemetry and no cloud mode.
Local processing reduces what has to leave your machine, but it is not a guarantee of privacy on its own: it depends on the features you use and on the security of your own computer. How updates will be delivered: Pending. Not published yet
Optional external services
Web search is the one feature that needs the internet during a turn. KOLDOS starts a SearxNG instance on your computer, which sends the search query to public search engines; pages KOLDOS reads are fetched from their sites. Everything that comes back is treated as untrusted data, never as instructions.
Vision, memory, files and tools run locally. The architecture page shows where each part runs.
Developer API
The local API runs on your computer and sends nothing out. The hosted API is planned: requests sent to it would be processed outside your computer, by the hosted KOLDOS service. Everything in a request, including prompts and any data you add, is sent there, together with the response.
Usage records such as time, model, status and token counts are kept to show usage and charge credits. Retention of logs and request contents: Pending. Not published yet
Authentication
Sign-in is not live yet on this site.
As specified in the backend contract, sign-in will use Discord's identify scope: the KOLDOS account service receives your Discord user ID, username and avatar. The Discord token stays on the server, and your session is kept in an HTTP-only cookie that scripts on the page can't read.
What the account service stores, and for how long: Pending. Not published yet
This website
The site's code includes no analytics, advertising or tracking cookies, and loads its fonts and scripts from the same place as the site.
The server that hosts the site may keep standard access logs, such as IP address, requested page and time. Hosting provider and log retention: Pending. Not published yet
A few preferences are kept in your browser's local storage and are not sent anywhere:
koldos.theme: dark or light theme.koldos.hardware.v1: the last values you entered in the hardware checker.koldos.preview.v1: only in preview builds, the sample dashboard data. API key secrets are never stored.
Hardware detection reads the operating system, CPU thread count, reported memory and GPU name through standard browser APIs. The values are used on the page and are not transmitted. A shareable link is only created when you press Copy link.
Contact and responsibility
Questions about privacy: itzkoldkir on Discord.
Data controller: Pending. Not defined yet. This notice will be completed once it is formally defined who is responsible for KOLDOS and their legal address.
Applicable law: Mexico, subject to the Mexican personal data protection law in force at launch.
Describes site revision 0.1.0, built Sep 27, 2026.