Architecture

Privacy by architecture,
not by policy

Cloud dictation tools promise not to misuse your data. VoicePrivate physically cannot — there is no server, no API endpoint, no network call. Your voice never leaves your device.

The problem with privacy promises

Every cloud voice tool makes the same claims. Here's why they can't keep them.

Cloud Architecture

What cloud tools do

Your audio is recorded, compressed, and sent over the internet to a server. A third-party AI model processes it. The text is sent back. Your audio may be stored for "quality improvement," used to train models, or retained per legal requirements. The server can be breached. Employees can access it. Governments can subpoena it. You have zero control once your voice leaves your device.

Local Architecture

What VoicePrivate does

Your audio is captured by your microphone and processed by an AI engine running directly on your device's CPU/GPU. The text appears in your app. The audio is discarded. No network socket is opened. No HTTP request is made. No data leaves your machine. There is no server to breach, no employee to access it, no data to subpoena. The privacy guarantee is architectural, not contractual.

How your data flows

Every step happens on your device. Nothing else touches your data.

1
You press Cmd+Shift+Space and start speaking
2
Audio captured by your local microphone — stays in RAM
3
AI engine processes audio on your device's CPU/GPU
4
Optional: local LLM polishes grammar (also on-device)
5
Clean text pasted into your app — audio discarded

The numbers that matter

0
Bytes sent to any server
0
Network connections opened
0
Third parties who see your data
0
Audio stored after transcription
0
Analytics or telemetry collected
0
Servers that could be breached

Don't trust us — verify it

Unlike cloud tools, our privacy claims are independently verifiable.

  • Monitor your network. Run Little Snitch, Lulu, or Wireshark while using VoicePrivate. You will see zero outbound connections. No DNS lookups, no HTTP requests, no WebSocket connections.
  • Disconnect your internet. Turn off WiFi and unplug ethernet. VoicePrivate works identically — because it never needed the internet in the first place.
  • Block it in your firewall. Add VoicePrivate to your firewall deny list. Every feature continues to work. Try the same with Wispr Flow, Otter.ai, or Aqua Voice — they stop completely.
  • Check the binary. VoicePrivate contains no networking libraries (no reqwest, no hyper, no curl bindings) in its core transcription engine. The only network code is for optional license validation.
  • Open-source AI models. The AI model that processes your voice is an open-source model with published weights. It runs entirely on your device — no API key, no cloud dependency.

What this means for you

For healthcare professionals

Patient data never leaves the exam room. No BAA required because there is no business associate — your data never reaches a third party. Stronger than HIPAA compliance by design.

For attorneys

Attorney-client privilege is preserved architecturally. Privileged communications processed on your machine can never be produced in discovery from a cloud server — because they were never on one.

For financial professionals

Client financial data stays on your device. No SEC concerns about third-party data processing. No SOX compliance gaps from external voice processing vendors.

For everyone

Your conversations, thoughts, and voice stay private. No profile built from your dictation habits. No training data contribution. No terms of service that grant usage rights to your voice.

Privacy you can prove

Try VoicePrivate free. Monitor your network. See for yourself.