Privacy and Security
ChatShell has no account and no telemetry. Your conversations live on your computer, and the only things that leave it are the requests you make: messages to your AI provider, searches and page reads on the web, and encrypted sync if you turn it on.
What goes where
Section titled “What goes where”| Where | What |
|---|---|
| On your computer | Conversations, assistants, prompts, attachments, and settings |
| On this computer only, never synced | Your sent-message history, translation history, remembered approvals, backups for undoing file changes (kept 30 days), long command output (kept 7 days), and the Auto-mode review log |
| With your AI provider | The messages you send, the attachments and tool results the conversation includes, and in Auto mode, the actions being reviewed |
| With your auxiliary models’ provider, if you set them up | What those jobs need: the start of a conversation for its title, older messages when a long conversation is compacted, and images the AI asks about |
| With search engines and websites | Your search queries, and requests for the pages the AI reads |
| In your iCloud Drive, if you turn on sync | Encrypted copies that only your own devices can open |
| With us | Nothing. Update checks download a public release file; see Updates |
If you pick a model that runs on your own computer, such as one in Ollama or LM Studio, your messages never leave it either.
Your data folder
Section titled “Your data folder”Everything ChatShell stores is in one folder:
| System | Folder |
|---|---|
| macOS | ~/Library/Application Support/app.chatshell.desktop |
| Windows | %APPDATA%\app.chatshell.desktop |
| Linux | ~/.local/share/app.chatshell.desktop |
The AI cannot read this folder with any of its tools, in any permission mode.
API keys and tokens
Section titled “API keys and tokens”API keys and MCP tokens are encrypted with AES-256-GCM before they are saved. The key that unlocks them is held by your system’s credential store: Keychain on macOS, Credential Manager on Windows, or Secret Service on Linux. A copy of the data folder on its own can’t reveal your keys.
Shell commands the AI runs start with a minimal set of environment variables, so the app’s secrets never reach them. You choose any extra variables to pass in Settings → Permissions.
What the AI can’t touch
Section titled “What the AI can’t touch”- ChatShell’s own data folder, in every mode
- Your shell configuration files, which often hold secrets, without asking you first
- Stored credentials such as your keychain, which the sandbox blocks
See Permissions and Sandbox for how the modes and the sandbox decide what runs without asking.
Updates
Section titled “Updates”To check for updates, ChatShell downloads a public release file from dl.chatshell.app, or from GitHub Releases if that fails. The request carries no account or identifier beyond what any web request does, such as your IP address. Every update is signature-checked before it installs, and nothing installs until you click. See Updates.
Builds you can trust
Section titled “Builds you can trust”- ChatShell is open source under the Apache 2.0 license, so anyone can read the code.
- macOS builds are signed and notarized by Seedvector LLC.
- Windows builds are not code-signed yet, so Windows may warn you the first time you open the installer.
Removing everything
Section titled “Removing everything”- If you used sync, open sync settings and choose Delete cloud data, so the encrypted copies leave iCloud Drive too.
- Quit ChatShell and delete the app.
- Delete the data folder.
- Remove the saved keys from your credential store: the entries named
app.chatshell.desktop, plusapp.chatshell.syncon macOS if you used sync.