EELML STUDIO PERSONAL 0.18
EELML Studio privacy, permissions, and data flow
EELML Studio Personal keeps local conversations, model records, service records, and workspace state on the Mac. Local inference does not require prompts to leave the device. Data can leave only when the user chooses an online model, remote MCP service, EELML Link, account service, download source, or another network capability.
Updated 2026-10-02 · This page describes the current Personal 0.18 release.
Local data by default
- Model, service, plugin, and conversation records are stored locally in SQLite.
- Secrets are stored in the macOS Keychain rather than the application database.
- A work conversation retains its selected directory and permission scope across turns.
- Local .eelml inference runs through the local Runtime Service.
When data can leave the device
Network transmission occurs only through a capability the user has enabled or invoked, such as an online model provider, remote MCP service, model download, account API, support submission, or EELML Link. The destination service has its own data policy.
Workspace permissions
A selected workspace root is part of the conversation identity. Tool calls are checked against that scope and the service authorization available to the current user. Connecting a tool does not grant arbitrary filesystem access.
Current product boundary
This page describes EELML Studio Personal 0.18. It does not claim that every third-party MCP service is offline, that online model providers retain no data, or that planned Enterprise controls are already available.