Privacy & Security
This page states plainly where your data lives, who can reach it, and where the boundaries are. No promises we cannot keep.
Where your data lives
Entirely on your own machine.
- Workspace files: in place — never copied, never uploaded;
- Project memory, call logs, configuration: the local data directory;
- The license cache: a locally held signed token — no plaintext key.
The program contains no telemetry or analytics. Everything AI clients read or write is visible in the local panel log.
How licensing works
- Activation exchanges the key for an Ed25519-signed token verified locally — no live connection required;
- Keys are stored server-side only as HMAC hashes; no database ever holds a plaintext key;
- 72-hour offline grace; past it, features lock while the panel and re-activation stay available.
Access boundaries
| Channel | Binding | Exposure |
|---|---|---|
| MCP gateway (18765) | 127.0.0.1 by default | Optionally opened on the LAN |
| Control panel (18766) | loopback only, enforced | Never exposed, in any configuration |
| Public tunnel | opt-in | Publishes only enabled workspace routes |
What is your responsibility (honesty section)
- The endpoint is the permission: anyone holding a workspace URL can read, write and execute inside it. Keep local endpoints private; treat public endpoints like keys;
- Trust the clients you connect: the model behind a client sees workspace content and can run shell commands — connect only to services you trust;
- Stay frugal in public mode: expose only the workspaces that need it, disable the rest;
- Guard your key: it is the product itself; leaking it equals transferring the right to use it.
Sandbox boundaries
Paths outside a workspace are read-only by default (and can be tightened to fully denied per workspace); shell commands run inside the workspace directory. These boundaries guard against AI mistakes — they are not an isolation layer against local malware. Device security remains your responsibility.
Reporting
Report issues via the repository issue tracker or your purchase channel; serious fixes are published with release notes.