Privacy notice
Last updated: 4 September 2026
This project collects no data about you, runs no server your data reaches, and has no way of knowing you use it at all. The detail below is what backs that up.
1. There is no data controller
Data protection regimes such as the GDPR build their obligations on there being a party that decides the purposes and means of processing. In this project there is no such party: no server, no database, no account, no log, no sub-processor. The data you create while using the software stays on your machine and on your own server, both of which are under your control alone.
So there is nothing held here for you to request access to, correct or erase. Deletion is local: uninstall the application, delete its configuration folder, and clear its credentials from the Windows credential store. There is no second copy anywhere else.
2. This website
Static pages, built ahead of time, with no application server and no database. Specifically:
- No analytics and no visitor measurement. No Google Analytics or any substitute for it, no tracking pixel, no browser fingerprinting.
- No cookies. The site sets no cookie of any kind and stores nothing in your browser.
- No third party requests. The fonts, images and icons are all served from this origin. There is no external CDN and no Google Fonts request.
- One exception, and only with your consent: the Hermes documentation frame in the Hermes section does not load unless you press the button yourself. When you do, your browser connects to nousresearch.com and that site's own policy applies to you. Before that, no request leaves this page to anyone.
- The specification estimator runs entirely inside your browser. The cores, memory and disk you enter are sent nowhere and stored nowhere. The page also reads the core count and memory estimate the browser advertises in order to fill the fields in to begin with. Both are coarse local readings and neither leaves the device.
The site's host, like any web host, may keep technical server logs including IP address and request time. Those logs belong to the host and are governed by its policy; the author neither accesses nor requests them.
3. The application: what is stored on your machine
%APPDATA%\JARVIS\config.json: the server address, the user name, the ports, and your language, voice and model preferences. An ordinary text file you can read and delete.- The Windows credential store: the SSH password and the Hermes key the application read off your server. Neither is written into
config.jsonor into any log. - The in-flight run file: a task still running is written to disk so it can be picked back up if the window is closed and reopened.
- The speech models: kept inside the installation folder. The
smallandtinymodels and the two voices arrive with the installer. Choosing a larger model in the settings makes the application download it from Hugging Face at that point, which is the only network connection the application ever opens to anyone but your own server, and it happens only because you asked for it.
4. The application: what leaves your machine, and where it goes
- To your own server, over SSH: read commands against
/proc,ps,df,crontabandsystemctl, the text of your commands, and HTTP calls to Hermes through a locally forwarded port. The address it connects to is the one you entered. - Nothing to the author. No automatic update, no version check, no crash report, no usage measurement. The application contains no server address other than
127.0.0.1and whatever you type in. - Audio never leaves at all. The microphone is owned by a local Python process, and the wake word, the transcription and the speech all run on your own processor or card. Raw audio is not uploaded and not saved. What reaches Hermes is the finished text, because that is what you asked it to act on.
When you type or speak a command, its content reaches Hermes on your server, and Hermes sends it to whichever model provider you configured in it. That is a relationship between you and that provider, and its policy governs what it does with the text. Review it if you say sensitive things out loud.
5. The permissions the software asks for
- The microphone, and only if you turn voice on. With voice off the microphone is never opened, and its indicator is struck through so you can see that it is off and not broken.
- The network, to reach the server you entered, and to download a larger model if you ask for one.
- No administrator rights. It installs inside your own user folder, touches no system setting and registers no service.
6. Children
This is a server administration tool aimed at developers and system administrators, and it is not directed at children. It collects no data from anyone.
7. Changes to this notice
If anything here changes, the date at the top changes with it, and the edit stays recorded in the repository's history on GitHub where it can be compared line by line. Any future release that does collect something will say so here before it does.
The legal counterpart to all of this is in the terms of use.