How does Osaurus keep my data private?

Updated

Osaurus keeps your data private by running its AI agents locally on your own computer rather than in a remote cloud. According to the product's own description, the agents "live on your computer, not in someone else's cloud," and the core promise is that "whatever you use them for, it stays with you." This matters if you want to use AI on sensitive material — contracts, client files, personal notes — without shipping that content to a third-party server. It applies to the desktop app (available for Mac, with a Windows Beta), not to any hosted service, since the pitch is specifically about local execution.

The mechanism: local execution instead of cloud processing

The privacy claim rests on where the model runs. In a typical cloud AI tool, your prompt and any attached files are sent to a remote server, processed there, and the response comes back. With Osaurus, the agent runs on your machine, so the working material stays on your disk.

The site's own demo illustrates this. In one example, a "Legal Helper" agent reads MSA-v3.docx and Playbook.md, compares §9 of the contract against the playbook's liability rules, and drafts a tracked edit — all shown as local file operations ("Read MSA-v3.docx and Playbook.md," "Edit MSA-v3.docx"). The status line reads "Raptor 0.6 · Local" and "Nothing left this Mac." In a second example, a "Practice Helper" reads three files in ~/Practice/Intake and produces a handoff summary. In both cases the files being read and written are local paths, not uploads.

What this means for your files

Aspect What the product shows
Where agents run On your computer (local), not in a cloud
Files referenced Local paths like MSA-v3.docx, ~/Practice/Intake
Where edits land Back in the local file (e.g., tracked in Word)
Stated retention "Nothing left this Mac" in the demo UI

The practical takeaway: if an agent reads a document on your machine and writes changes back to it, that document does not need to leave your computer for the task to complete.

What to verify yourself

The site's headline and demo support the local-execution claim, but they don't spell out every storage or syncing detail. Before relying on it for sensitive work, check the app's own documentation for:

  • Whether any telemetry, crash reports, or usage analytics are sent off-device.
  • Whether model downloads or updates involve network calls (expected) and what they transmit.
  • Whether any optional cloud or sync features exist, and whether they're off by default.
  • Where conversation history and agent state are stored on disk, and how to clear them.

These are the specifics that determine whether "stays with you" holds for your particular setup. The product page states the principle; the documentation is where the edge cases live.

Who this fits

Osaurus is a reasonable fit if your main concern is keeping source documents and prompts on hardware you control, and you're working on a Mac (or willing to try the Windows Beta). It's less relevant if you specifically need cloud-scale models or cross-device sync, since the value proposition here is the opposite of that. The download figures shown on the page (232.9k downloads, 7.8k stars) indicate an active user base, but they don't tell you anything about your own data handling — that's what the local-execution design and your own review of the docs are for.