When you run a model locally, Ollama's FAQ says it does not see your prompts or data. A cloud model is different: Ollama runs it on its own service, so your prompts go there, where Ollama says it processes them transiently, does not store or log them and never trains on them. Three other things use the network even in local use, according to its documents: pulling a model downloads it from the Internet, the Mac app downloads its own updates, and signing in for cloud models adds your installation's public key to your Ollama account. To keep Ollama local only, set disable_ollama_cloud in ~/.ollama/server.json or the environment variable OLLAMA_NO_CLOUD=1, which also turns off cloud models and web search. This page repeats Ollama's documents and tested nothing.
Ollama's local FAQ answers this question with: "Ollama runs locally. We don't see your prompts or data when you run locally." The same answer goes on to cover cloud-hosted models, below.
| Activity | What Ollama's documents say |
|---|---|
| Pulling a model | The FAQ says Ollama pulls models from the Internet. |
| Updates | The FAQ says Ollama on macOS and Windows will automatically download updates, and that you apply one with Restart to update. |
| Signing in | ollama signin, or the Settings page in the Mac app, adds your installation's public key to your Ollama account. On a Mac the key file is ~/.ollama/id_ed25519.pub. |
| Cloud models | They run on Ollama's cloud service and need an Ollama account. Ollama's docs run one with a :cloud name, such as gemma4:cloud. |
| Web search | The FAQ lists web search with cloud models as what you lose when you turn Ollama's cloud features off. |
The cloud FAQ says Ollama operates with a zero data retention policy: it processes prompts and responses of cloud models transiently, does not store or log that content and never trains on it. It also says Ollama collects basic account information and limited usage metadata that does not include prompt or response content, does not sell your data, and lets you delete your account at any time. Ollama's cloud overview points to its privacy policy for details.
Ollama's FAQ gives two ways. Either set this in ~/.ollama/server.json:
{
"disable_ollama_cloud": true
}
or set the environment variable OLLAMA_NO_CLOUD=1. Restart Ollama after changing either. The FAQ says that once cloud is disabled, Ollama's logs will show Ollama cloud disabled: true; on a Mac the logs are in ~/.ollama/logs, per Ollama's macOS page.
The FAQ says that when Ollama runs as a macOS application, you set environment variables with launchctl setenv and then restart the Ollama application. For this variable that reads as follows; this page did not test it:
launchctl setenv OLLAMA_NO_CLOUD 1
The FAQ also says that turning cloud features off means you lose Ollama's cloud models and web search. It does not say whether pulling a model still works.
| Claim | Source |
|---|---|
Local use: Ollama does not see prompts or data; models are pulled from the Internet; Mac updates are downloaded automatically; cloud features can be disabled; the launchctl rule | Ollama docs, Local FAQ |
| Zero data retention, account information and usage metadata, the public key | Ollama docs, Cloud FAQ |
| Cloud models run on Ollama's service and need an account; the privacy policy | Ollama docs, Cloud |
Cloud models are run with a :cloud name | Ollama docs, Cloud models |
~/.ollama/logs on a Mac | Ollama docs, macOS |
disable_ollama_cloud to true in ~/.ollama/server.json or set OLLAMA_NO_CLOUD=1, then restart Ollama. Ollama's FAQ says you then lose its cloud models and web search.