shellnaga.sh · last updated
Privacy policy
This page covers the website shellnaga.sh. Shell'Naga, the app, has no account and sends only anonymous usage statistics (install and launch counts, the previous version and update results, unexpected closes and, in ranges, daily time in use and openings), which you can limit or turn off. To check for updates, it downloads one small file from shellnaga.sh at most once a day, with no id attached. An optional AI assistant, off by default, talks only to the provider you choose. More about the app.
In short: we count visits and downloads ourselves, without cookies. We never store your IP address, not even a truncated one. We keep only the country, region, city and internet provider it points to. Google Analytics runs only if you click Accept in the cookie banner.
Our own analytics, without cookies
A small script on the page and the download link send these to our server (Amazon Web Services, United States), at the same address as the site:
- the page you open and the site that sent you there (the host only, like
news.ycombinator.com), and theutm_campaign tags of the link; - the class of your screen (phone, tablet or desktop) and your browser's main language;
- how fast the page loaded for you (Core Web Vitals) and clicks on the main buttons and links;
- on the home page only, how far down you scrolled (25, 50, 75 or 100%), each mark at most once each time the page loads. It is kept only as a number added to the day's total, with no page address, time, place or visitor code;
- for a download, which file (installer, portable or exe) and which button.
From the connection itself, through our content delivery network (Amazon CloudFront):
- the country, region, city and internet provider that your IP address points to (an estimate made by CloudFront; no outside service is asked). The address itself is never stored, not even a part of it.
To count unique visitors in a day, we compute a one-way code from your IP address, your browser's user agent and a random value that changes every day. That value expires after two days and the database deletes it within two more, so a visit today cannot be linked to a visit on another day. We never store your IP address, a cookie or anything in your browser's storage. These counters do not keep the user agent either. The file server's access log, described in the table below, does keep the name of the program that asked, for 30 days and without any IP address.
If your browser sends Do Not Track or Global Privacy Control, we only add one to an anonymous counter: no page, no place, no address in these counters. (The file server's download log, described in the table below, is separate: it records the country of every request, including yours, for 30 days.) A download is the one exception to "only one counter": it still counts in the download total and in the file-type counter (so the totals stay true), but not by button, country or referrer, and nothing about the click is recorded.
Google Analytics, only if you accept
A banner asks first. Until you click Accept, nothing from Google loads and no cookie is set. Your choice is saved in your browser for 12 months (the key sn-consent in its local storage). Do Not Track and Global Privacy Control count as Decline.
If you accept, Google Analytics 4 (Google LLC) sets the cookies _ga and _ga_<id> for 13 months and collects the pages you view, how you reached the site, your device, browser and approximate location, and events such as clicks and scrolling. Google says Analytics 4 does not log or store IP addresses. Google signals and ad personalization are off, and nothing is used for advertising. Google keeps the event data for 14 months. See Google's privacy policy.
How long we keep it
| What | Kept for |
|---|---|
| Each visit or download event (page, referrer host, place, provider) | 90 days, then deleted automatically |
| Daily totals (counts per page, country, city, provider, and how far down the home page visitors scrolled; country, region, city and provider are also counted together, per day, and per file for downloads from the page; never with an IP address) | 400 days, as numbers per day |
| The daily random value and the unique-visitor codes | 2 days, and at most 4 if the database is slow to delete them |
| Server error logs (only the kind of error, never the request) | 14 days |
| Download log of the file server, which records every request to the site, not only downloads (date and time, method, path, result, the country, and the name of the program that asked, such as a browser, winget or the app with its version; this includes the app's anonymous usage message to /t; never an IP address, cookie or referrer) | 30 days, then deleted automatically |
| Google Analytics, if you accepted | 14 months, at Google |
| Emails you send to support@shellnaga.sh | as long as needed to answer you |
We don't sell or share any of it. Only the owner of Shell'Naga sees it, in a private dashboard.
The app
Shell'Naga has no account. What you type, the servers you connect to and the passwords in its vault stay on your PC, or in the sync folder you choose. The only thing it sends on its own, besides the update check below, is the anonymous usage statistics described here.
Anonymous usage statistics. They are on by default (opt-out), and nothing pops up in the app about it: this policy, the download page, the installer and the choice in Settings › App › Privacy tell you so. When the app is installed (install) and when you open it on a new day (launch), it sends one small message to https://shellnaga.sh/t with:
- a random ID that the app creates on your PC (not derived from your name, PC, account or hardware) and keeps only in its local state folder, never in the config, the vault or the sync folder;
- the app version, the operating system version number (on Windows, for example 10.0.26300; no edition and no PC name), the processor type (x64 or ARM64), the interface language and the install type (installer, portable, winget, Chocolatey, Scoop or other);
- in the daily
launchonly, since the last one that got through: the version the app was updated from, when it changed, and whether the update worked, failed or was rolled back; and how many times the app closed without a clean exit after opening its first window (0, 1, or 2 or more: a count, never an error message, a file name or a memory dump; a power cut also counts); - at the level All statistics only, also in the daily
launch: how long a Shell'Naga window was in front on the last day you used it, not counting while the PC is locked or asleep (under 15 minutes, 15 minutes to 1 hour, 1 to 4 hours, or more) and how many times you opened it that day (1, 2 to 5, or 6 or more). The exact times and counts stay on your PC.
It never sends your name, email, files, paths, commands, host names, passwords or anything you type, and the collector does not store your IP address or user agent. (The file server's access log keeps the date and time, the method, the path /t, the result, the country and the program name ShellNaga/<version> for 30 days, never your IP address or your ID; see the table above.) We use it only to count installations and how many are in use, by version, operating system version, language and install type, and to know whether updates work, whether a version closes unexpectedly and how much the app is used, so we know which versions and systems to support and what to fix. The legal basis is our legitimate interest in knowing that; the message holds nothing that names you, and you can object at any time by turning it off.
Each time you open the app, it sends each message at most once. If a message does not get through (no network, or a server that is busy or failing), the app tries again the next time you open it; the server still counts each installation at most once a day. On the server, the message becomes daily counters (numbers per version, operating system version, language, install type and processor type, and, each on its own, per update result, previous version, range of unexpected closes, range of time and range of openings; only the unexpected closes are also counted per version, and no other two of these are ever combined). To count each installation once a day, we keep a one-way code made from the random ID and a value that changes every day; it expires after two days and the database deletes it within two more, so the ID is never stored and a day cannot be linked to another. Active installations over 7 and 30 days are estimated from those daily codes, not from stored IDs. The counters are kept as numbers per day, and those with open values (version, operating system version, previous version) are deleted after about 13 months.
To limit or turn it off: Settings › App › Privacy offers All statistics, Errors only (the install and daily launch messages above still go, with the random ID, but the daily one carries only the unexpected closes and the update results, never the time or the openings) and Off, and you can change it at any time. Turning it off also deletes the random ID and what the app counted for it, and nothing more is sent. For many PCs, an administrator can set the Windows policy DisableUsageStats (DWORD 1) under HKLM\Software\Policies\ShellNaga, which turns it off and hides the choice; the environment variable SHELLNAGA_NO_USAGE_STATS=1 does the same for scripts and CI. Debug builds never send it.
AI assistant (off by default). Shell'Naga can explain a failed command or write a command from your description, using an AI model that you choose. It is off until you turn it on in Settings › AI, and while it is off it shows nothing and sends nothing. Shell'Naga has no AI service of its own: the app talks directly to the provider you configure, and nothing goes through our servers.
- Local models (Ollama, LM Studio, llama.cpp or another server on
localhost): nothing leaves your PC. When you open Settings › AI, the app checks ports 11434, 1234, 9931 and 8080 onlocalhostto find a local server. It never scans other hosts. - Cloud providers (Anthropic, OpenAI, Google Gemini or an
https://address you enter): the request goes from your PC to that provider, under that provider's terms and privacy policy. Some providers may use what you send to improve their models, for example on free tiers. Check your provider's settings.
When something is sent: only when you click Explain, Ask, Send or Test connection, never by itself. For cloud providers, the app first shows what will be sent and waits for Send (you can change this in Settings › AI). "See exactly what is sent" shows the full request, without your key.
What is sent: for Explain, the command line, its exit code, your shell, your Windows version, the current folder (with your user folder shown as ~) and up to 200 lines (by default) of that command's output. To write a command, what you typed, your shell, your Windows version and the current folder. Before anything is sent, the app hides what looks like a secret: tokens and API keys, private keys, passwords in URLs, PASSWORD=-style values and the values stored in your unlocked vault. In remote tabs (SSH, Telnet, serial), the output and the folder may include that server's user and host names, and they are not hidden yet: with a cloud provider, the app always shows what will be sent, with that warning, and waits for Send, even if you turned the review off. The app does not read your environment variables or history; they are sent only if they appear in the output you choose to send. Other tabs are never sent.
Your API key is stored only in the Shell'Naga vault, protected by Windows or by your passphrase. It is sent only to the provider it belongs to, never to us. If you sync your vault (only a vault sealed by a passphrase can be synced), the key travels inside it, encrypted.
What stays on your PC: answers live only in memory and disappear when you close them. The app keeps today's token counts per model, with no text, in its local state folder, to show your usage and enforce the daily limit. That file is never synced or sent.
To turn it off for everyone on a PC, an administrator can set the Windows policy DisableAI (DWORD 1) under HKLM\Software\Policies\ShellNaga, which also hides the setting. SHELLNAGA_NO_AI=1 does the same for scripts. A profile can also be set to never use AI. Using the AI assistant adds nothing to the anonymous usage counts.
Update check. At most once a day, the app downloads https://shellnaga.sh/downloads/latest.toml, a small signed file that says which version is current. The request carries the app's version in its user agent (ShellNaga/<version>) and nothing else about you. Like any connection, it shows your IP address to our content delivery network (Amazon CloudFront), once a day. The file server's download log (see the table above) keeps the day, the file name, the country and that version for 30 days, never your IP address, so we can count update checks per version. You can turn the check off in Settings › App; "Check now" still works when you click it. A new version is downloaded only after you click Update now.
Fonts. The fonts in Settings › Appearance › More fonts are downloaded only when you click Install, from our own server at https://shellnaga.sh/downloads/fonts/, like the update check; opening the list downloads nothing. The request carries the app's version in its user agent (ShellNaga/<version>) and nothing else about you. Like any connection, it shows your IP address to our content delivery network (Amazon CloudFront). The file server's download log (see the table above) keeps the date and time, the path of the font file, the country and that version for 30 days, never your IP address.
Local MCP server. The app can run a local MCP server so that an AI assistant on your PC can read a tab and type in it. It is off by default. It listens only to programs of your Windows account on the same PC, never to the network. Reading asks once per connection and typing asks every time. What the assistant does with what it reads, including sending it to its own provider, is up to that assistant and its privacy policy.
Agent usage. Settings › Agent usage is optional and off by default. When it is on, the app reads the session files that Claude Code and Codex write on your PC and keeps only numbers, the model, the time and the folder, never the conversation. Nothing leaves your computer. "Connect to Claude Code…" changes only the statusLine entry of ~/.claude/settings.json: it shows the change first and keeps a copy of the file, and "Disconnect…" puts it back.
Contact
Questions, or a request to see or delete data about you: support@shellnaga.sh. Since we never store your IP address or anything that identifies you beyond a few days, we usually cannot tell which records are yours, but we answer every request.
If this policy changes, the date at the top changes too.