Every time you paste something into a cloud AI tool, a small question flickers past: where does this actually go? For a quick search it rarely matters. For your inbox, your contracts, your customer list, or your code, it matters a lot. "Private AI" gets used as a marketing word, but most people never get a straight answer about what actually stays on their device and what quietly leaves it.
That uncertainty is the real problem. It is hard to use AI for the work that would benefit most — the sensitive, valuable, confidential work — when you cannot tell where your data ends up. So let us be concrete about what private actually means, and how to tell the difference.
What "private" should mean
A genuinely private setup has a simple property: your data does not leave your control unless you explicitly send it somewhere. That breaks down into three honest tests.
- Where does the model run? If the model runs on your own device, your prompts and files are processed locally and never touch an outside server. If it runs in the cloud, everything you send is, by definition, leaving your machine.
- Where is your data stored? Local files, local history, local logs stay on the box. Cloud tools keep your conversations and uploads on their infrastructure, often to improve their service.
- What is sent over the network, and when? This is the part marketing skips. A truly local task sends nothing. A "private" tool that still calls home for every request is not private; it is just polite about it.
If a product cannot answer those three questions plainly, treat its privacy claims as decoration.
The honest middle ground
Here is the part most privacy pitches leave out: fully offline and fully cloud are not your only options, and pretending otherwise is dishonest.
Local models are excellent for routine, sensitive work — summarising your own documents, drafting replies, sorting your inbox, answering questions about files you own. They are private by construction because nothing leaves the device. But for the heaviest reasoning, a large cloud model is still stronger.
The sensible setup runs local by default and lets you choose, per task, when to reach for the cloud. Your private data stays on the device for the everyday work, and you make a deliberate decision to send something out only when the bigger model genuinely earns it. Privacy then becomes a choice you control, not a default you cannot see.
What actually stays on your device with a local-first setup
When AI runs on hardware you own, the privacy story gets concrete:
- Your prompts and documents are processed on the device. The local model reads your files where they already live.
- Your history and logs stay on local disk. There is no conversation archive on someone else's servers.
- Your integrations — email, chat, browser sessions — keep their credentials and data on the box, not in a third-party cloud.
- The network is quiet unless you point a task at a cloud provider on purpose. Setup and updates aside, a local task simply does not phone out.
This is the difference between trusting a privacy policy and not needing one. If the data never leaves, there is nothing to leak, subpoena, or quietly repurpose.
How to check any tool's real privacy
You do not have to take anyone's word for it. A few practical checks:
- Ask where the model runs. Local or cloud. If they dodge, assume cloud.
- Watch the network. A local task should generate little to no outbound traffic. Tools that constantly call home are not local.
- Find your data. Can you point to the file or folder where your history and uploads live? If it is "in our cloud," it is not on your device.
- Check the off switch. Can you run it with the network disconnected for the tasks that matter? If yes, it is genuinely local.
These tests cut through the marketing fast. Privacy you can verify beats privacy you are promised.
The takeaway
"Private AI" only means something if you can answer where the model runs, where your data is stored, and what crosses the network. The strongest setup is local-first: routine, sensitive work handled on hardware you own, with the cloud as a deliberate choice for the rare heavy task rather than the silent default. That way privacy is something you can check, not something you have to believe.
OpenClaw is built around exactly this model — it runs a local model on a device you own, keeps your data on the box, and reaches for cloud providers only when you tell it to.