PRIVACY BOUNDARY
Can local AI really be private?
A downloaded model can process prompts on your computer. That does not establish where the rest of your workflow sends documents, search queries or conversation history.
Editorial update: 24 October 2026. This is an audit procedure, not a claim that HostingLinks has independently tested every application or version.
Map where your data goes
Consider a document assistant with a local chat model. If its document index uses a hosted embedding API, extracted passages still leave the computer. If it searches the web, the search service receives the query. Keeping one part local does not move the other parts with it.
| Part | What to check | What to record |
|---|---|---|
| Chat model | Downloaded model or hosted API | Model, runtime and server address |
| Document processing | OCR, embeddings and conversion providers | Where text and indexes are processed and saved |
| Tools | Search, remote MCP servers, plugins and fallbacks | Enabled integrations and what they receive |
| Storage | History, logs, exports and synchronised folders | Locations, access and retention |
| Server access | Other users, network listeners and remote access | Who can connect and how access is controlled |
Check the selected model, not only the app name
Applications can offer local and cloud models in the same interface. Ollama distinguishes local inference from its cloud service. Its FAQ documents OLLAMA_NO_CLOUD=1 as one way to disable cloud features, with a restart required. Apply it to the actual Ollama process using the operating-system instructions; a variable in an unrelated terminal will not configure an already running app.
This setting does not configure a separate interface or plugin. Check those independently. See the official Ollama FAQ and configuration instructions.
LM Studio documents offline operation for downloaded models, document chat and its local server. Model searches, downloads and update checks need connectivity. These core behaviours do not describe every third-party tool you might connect. See LM Studio’s offline operation guide.
Run a small offline test
- Download the model and required runtime while connected. Prepare a made-up document with a distinctive sentence, without personal or client data.
- Record the model and endpoint. Disable remote tools, web search and provider fallbacks.
- Disconnect Wi-Fi, Ethernet and other internet connections. Start a new conversation and ask a simple question.
- Import the test document and ask about its distinctive sentence. Testing an existing index would miss a remote dependency used during import.
- Record errors. Reconnect and investigate each failed step before using private material.
Success supports the conclusion that those particular steps work offline. It does not prove the app never makes requests when online, that logs contain no private data, or that another user cannot read stored files. A failure can also be a missing download rather than evidence of an upload.
Protect the copies left behind
Check whether history, extracted text or indexes live in a cloud-synchronised folder. Deleting the original may leave those copies behind. Review device access, encryption and backup destinations. Avoid exposing a model server publicly just to connect another device.
Repeat these checks after changing providers or adding features. For work documents, follow your organisation’s data rules even when processing runs locally.
Keep an audit note
Record the app version, model, endpoint, document processor, enabled tools, storage locations and test date. That is more useful than a blanket label saying “private AI”.
Next: compare local and hosted AI or plan a document workflow.