PRIVACY, WITHOUT THE FOG
Local storage.
Connected intelligence.
KEORIS keeps its records on your PC and sends no usage data to us. Some features connect to other services: Jobs run through the Claude Code and Codex you installed and signed in to yourself, and those send your request and the files they use to their providers. Local storage does not mean every feature works offline.
What KEORIS stores on your computer
- Tasks, notes, memories, routines, schedules, and approved-folder settings, in
%APPDATA%\KEORIS. - An activity history of what KEORIS did, capped at the most recent 2,000 entries. Older entries are dropped, not archived.
- The local assistant's rolling plain-text conversation record, kept for roughly two days so you can recover recent answers. Bot Room conversations and job records are separate.
- Bot Room prompts, memories, and conversations. A bot using Claude or Codex still sends the context used for that turn to its provider.
- Job records and summaries, deleted the next time KEORIS starts once 14 days have passed since the job ended (a job still waiting or running is never deleted), and your one-time “Allow jobs” answer. Full coding-agent conversations stay in the history kept by Claude Code or Codex, which have their own data handling.
- Ideas, as notes in your Ideas folder. Saving an idea transcribes it on your PC and does not send it to an AI model. Only pressing Start job on an idea hands its words to Claude Code or Codex.
- Your licence key, encrypted with Windows secure storage.
- If you use Sign in Codex for bots (Bot Rooms, MANAGE), that separate ChatGPT sign-in. Codex keeps it as a file (
auth.json) in%APPDATA%\KEORIS\dev-agents\bot-codex-home. KEORIS does not encrypt it, and only checks that the file is there and not empty. - Your source files and project folders stay where they are. When a job reads them, their contents become part of what goes to the job's provider.
Local does not mean encrypted. Apart from the keys KEORIS saves itself, application data and recent conversation records are ordinary files protected by your Windows account. Anyone with access to that account may be able to read them.
What downloads on first launch and during setup
First launch and local voice and model setup connect to third parties to fetch software and model files. Those download services receive the normal network requests needed to deliver the files. Nothing about you is sent to get them.
- Python 3.12 when it is missing, through Windows Package Manager or python.org, and the Python voice packages (faster-whisper, openWakeWord, sounddevice, numpy) from PyPI.
- A faster-whisper speech-recognition model and a small openWakeWord file (about 1.3 MB), both for on-device voice. The “Hey Keoris” wake word itself ships inside KEORIS.
- The Kokoro neural voice model (about 326 MB), from Hugging Face, on first launch. Until it is ready, KEORIS uses a built-in Windows voice.
- Ollama (through Windows Package Manager or ollama.com) and a local language model when you enable the local brain.
Jobs also need Claude Code or Codex, which you install and sign in to yourself. KEORIS does not include them and never reads your own sign-in to them.
When data leaves your computer
| Feature | What connects | What may be sent |
|---|---|---|
| Claude Code and Codex jobs | Anthropic or OpenAI, through the coding tool you signed in to | Your request, and whatever the job reads while it works: files, command output, anything it opens. KEORIS switches off your connected apps for jobs, but a Claude Code job's own commands can still reach the internet. Codex job commands have no internet; a “Codex, with web” job uses OpenAI's search. Claude Code and Codex may also send their own usage data to Anthropic and OpenAI, under those makers' policies. |
| Assistant chat and Bot Rooms | The brain you select: local model or connected provider | With a connected brain, conversation text, prompts, memories, and relevant context are sent for that turn. Keeping a conversation on disk does not keep its connected processing on disk. |
| Screen vision and cloud camera analysis (optional) | Anthropic or OpenAI, using the API key you saved | When you ask KEORIS to look at your screen, or a walkthrough checks an install step on screen: a picture of your whole main screen. A walkthrough takes no picture while KEORIS sees a banking or password window open. With Cloud camera analysis switched on (off by default): a camera picture, when the local vision model can’t describe it. |
| Walkthroughs (“help me install the thing I downloaded”) | Your connected cloud brain, Anthropic or OpenAI, even if you chose the local model | The program’s name and up to your last 12 conversation turns, to plan the steps. Step checks send a screen picture, as above. |
| Fast command decisions (optional) | TypeSafe AI, if you save a TypeSafe key | With FAST (JEV) chosen: the words of each command you give at the desk and the assistant's name, so the Jev model can sort the command. Saving, testing or comparing a key also sends a sample command. Never your files or conversation history. Not used in Parental controls, from the phone, or by a schedule. |
| Licence activation | Lemon Squeezy, our store | When you activate, check or deactivate a store licence key: the key and this PC's name. KEORIS never checks a licence at launch or on a timer, and a network failure never removes an active licence. |
| Cloud cameras | Ring, Blink, or Google/Nest | Account tokens, camera requests, snapshots, and live-stream traffic required by that provider. |
| Built-in browser | The sites you open; DuckDuckGo for search text | Normal web traffic for pages and searches. The assistant's built-in browser isolates pages from KEORIS files, keys, and controls. |
| Weather and feeds | National Weather Service and feeds you configure | Your configured county or feed requests. |
| Mobile and family calls | Your Tailscale network | Encrypted companion and call traffic between paired devices. |
| Updates | GitHub | On launch, a standard request asking whether a newer release exists. No account and no personal data. Updates never install automatically. |
Anthropic, OpenAI, and other connected services apply their own data-handling policies and your account settings. This page does not promise a particular retention period or training policy for those providers.
Buying KEORIS
Purchases of KEORIS go through Lemon Squeezy, which runs the checkout as the merchant of record. Lemon Squeezy collects your payment details, email address and billing information to take the payment, handle tax and send your receipt and licence key. We receive your order details, including your name, email address and licence key, so we can support your licence and process refunds. We never see your full card number.
Lemon Squeezy's own privacy policy covers what it does with checkout data. For refunds or questions about an order, use your receipt or contact hello@keoris.dev.
Keys and connected-service secrets
KEORIS encrypts the API keys, licence keys and connected-service secrets it saves itself with Windows secure storage. If secure storage is unavailable, KEORIS refuses to save a new secret rather than write it as plain text. Plain-text secrets left by older builds are moved into secure storage at startup, or switched off with a visible repair warning. Secrets are never included in backup exports.
Your own Claude Code and Codex sign-ins stay with those tools. KEORIS starts the copy you installed and never reads or stores that sign-in. Jobs use the sign-in you set up in Claude Code or Codex. KEORIS does not pass Anthropic or OpenAI API-key variables from its own environment to a job, but if Claude Code or Codex is itself set up with an API key, jobs use it. The one sign-in kept in KEORIS's folder is the separate Codex sign-in for bots, described above.
Release notifications
When you submit the release-notification form on the live website, your email address, and your answer to the optional "What will you build first?" question if you give one, are sent to Netlify Forms and stored for Keoris Systems to send you a KEORIS access announcement and understand what Operators want to build. Netlify also processes the network request and applies its spam controls. The form does not ask for your name, create a KEORIS account, reserve a licence, or take payment.
The local website preview does not send or save your email address. It displays a preview notice instead of a signup confirmation.
To withdraw your request or ask for removal from the release list, contact hello@keoris.dev. Release announcements are sent separately from collecting this request.
Jobs and your control
- Jobs are off until you allow them. KEORIS asks once, before the first job runs. While Parental controls are locked, jobs cannot be allowed or started.
- A job can read, create, change and delete files, and run commands, without asking before each step. A Codex job changes files only in its folder, but it can read files elsewhere on your PC, and what it reads goes to OpenAI. Codex may remember a job's folder as trusted in your own Codex settings. A Claude Code job starts in its folder, but can read, change and run anything your Windows account can.
- A job with no project works in
Documents\KEORIS Jobs. If Windows syncs your Documents folder to OneDrive, those files sync too. - KEORIS switches off your connected apps for jobs, but it cannot fence what a Claude Code job's own commands do. Stop ends the job's own programs; it does not undo what the job already did or cancel anything it set up to run later. See the Security page.
- KEORIS release checks tell you about a new version rather than installing it. Changes a job makes follow that job's permissions.
Deleting your data
Remove connected keys from Settings, delete recent transcript files from the application data folder, or use Backup & Restore before removing the application data folder. Uninstalling removes the program but may leave your data folder so a later reinstall can recover your settings.
Deleting KEORIS's local files does not delete Claude Code or Codex history, records held by a connected provider, or your order with Lemon Squeezy. Manage those through the respective tool, provider or store.
Checked against KEORIS 0.21.0 on 30 October 2026. The licence covers your use of KEORIS.