Local means local.
WidePane is built so your source code, prompts, conversations, and API keys stay on your machine unless you explicitly choose a cloud model — and even then, only the request you make is sent.
No silent uploads
There is no code path that falls back from a local model to the cloud. Local‑only mode blocks cloud and unapproved LAN requests at the provider gate — enforced in code and covered by tests, not just promised.
Secrets in the OS keychain
API keys and secret headers live in Windows Credential Manager, macOS Keychain, or the Linux Secret Service. They are referenced by name and resolved only inside the trusted host — the webview never receives a secret value.
A real trust boundary
The desktop webview can't touch the filesystem, run a process, or make a network call except through a fixed set of typed, workspace‑contained commands. Paths are canonicalized; traversal and symlink escapes are rejected.
Permission‑mediated agent
Every agent tool call is validated, risk‑classified host‑side (the model can't lower risk), explicitly approved, then executed. Destructive and sensitive actions are never auto‑approved. Actions are recorded as redacted metadata.
Untrusted by default
Repository text, tool output, and MCP‑server results are treated as data, never instructions. MCP is off by default with per‑tool allowlists, and server output is sanitized and fenced before it reaches a model.
Your website account
Creating a WidePane account lets you manage downloads and your workspace. The account identifies you — it does not receive your code, prompts, conversations, keys, or model traffic. Passwords are stored only as strong salted hashes; verification and reset codes are hashed, single‑use, and time‑limited; secrets are never logged.
Questions about trust?
Read the privacy policy or reach out to security@widepane.com.