Security model
The cloud can’t read
what it never receives.
Identity and project data have different homes. That is the core security decision.
Cloud stores
- Email and display name
- Passkey public keys
- Session and token hashes
- Device labels and audit events
Desktop stores
- Meetings, notes and chat
- Source code and documents
- Provider keys in OS keychain
- Local project database
Loopback core
The local core is bound to 127.0.0.1 and is never a public API.
Encrypted relay
Remote requests are opaque envelopes. The relay cannot read project data.
Explicit actions
Tool calls and code edits go through approvals and protected paths.
Report a vulnerability
Email security@llm-ide.com with reproduction steps. Do not test against other users or their data.
Remote phone/browser access is being built as an end-to-end encrypted relay. Until it is enabled, the web client uses only the desktop-host path you explicitly configure.