Privacy and data boundaries
Where your data lives, and exactly when anything touches the network.
What stays local
- Local transcription and desktop AI processing run on your computer, without uploading to a cloud service.
- Source media is read-only and is not changed by transcription.
- Once the required models are downloaded, local transcription and AI processing can work offline.
- When you choose LAN compute, data is sent to the selected node.
The only times it uses the network
- Downloading models, from the official repositories in the curated list.
- LAN compute sends media to the selected node; requests to its language-model API also send the submitted text to that node.
The LAN boundary
- Nodes talk over plain HTTP. No encryption, no tokens, no pairing.
- So LAN compute belongs on trusted networks only.
- Media a node receives is kept in its lan-host directory, and automatic cleanup is off by default.
- The app does not configure public access, port mapping or the firewall.
The MCP boundary
- MCP runs over local stdio only.
- No network listener, no unrestricted filesystem access, no shell execution.
- Input and export directories must be declared explicitly. Undeclared paths are denied.
What it does not do
- No accounts.
- No cloud sync.
- No telemetry.
Where data lives and what uninstalling leaves
- App data, models and job records live in the Application Support directory the system gives the app.
- LAN node media and results live in its lan-host subdirectory, alongside its logs.
- Uninstalling the app does not delete any of it. You clean it up by hand.