Privacy & security

If we don't have it,
we can't lose it.

Productive Voice is built on a single architectural rule: your voice and your text never touch our infrastructure. We're not the cloud. We're the desktop app you bought once.

Four commitments

What we promise.
And how the architecture enforces it.

01

Neither your audio nor your formatted text reaches our servers.

We don't have a server in either path. Your microphone stream goes directly to Deepgram over your own API key, under your contract with them. The LLM refinement step goes directly from your machine to OpenRouter (or whichever provider you've configured), again under your key. Productive Voice never sees a packet of either.

02

Your API keys are encrypted at rest.

AES-256-GCM, with the encryption key derived from your operating system's keychain. Even with raw disk access, your keys can't be exfiltrated without first unlocking your OS user account.

03

Your dictation history lives only on your machine.

Encrypted, searchable, and exportable, but only by you. No sync. No cloud backup. No "for our records." If you reinstall the OS, your history is gone unless you exported it yourself.

04

We have no account system. By design.

You don't sign up. You don't log in. You buy a licence, install the app, paste two API keys, and you're done. There is no profile we can compromise because there is no profile at all.

Data flow

Where your voice actually goes.

Every byte. Every hop. Spelled out.

Microphone

Raw audio

↓ in-memory only

Productive Voice app

Encrypts & routes

→ TLS 1.3 →

Deepgram

Speech → text
your API key

↓ TLS 1.3 ↓

OpenRouter

Text → formatted
your API key

Pasted at cursor

Where you typed

↑ in-memory only

History (encrypted)

Local disk only

Not present in this diagram
Productive Voice servers · Account database · Telemetry pipeline · Audio storage · Transcript logs
0
Audio bytes that touch our servers
0
Transcripts logged anywhere besides your disk
0
Required accounts, tokens, or sign-ups
0
Bits of AES-GCM protecting your keys at rest
Encryption

What's encrypted on disk.

Everything sensitive that Productive Voice stores locally is encrypted at rest with AES-256-GCM. Encryption keys are derived from your OS keychain so they can't be extracted without first unlocking your user account.

Deepgram API key
%LOCALAPPDATA%\ProductiveVoice\credentials.enc
AES-256-GCM

Your Deepgram speech-to-text API credentials. Decrypted in-memory on demand during recording sessions and never stored in raw text on disk. OS keychain protection ensures safety at rest.

OpenRouter API key
%LOCALAPPDATA%\ProductiveVoice\credentials.enc
AES-256-GCM

Your LLM orchestration credentials. Derived from your OS account password, preventing unauthorized access by sandboxed applications or physical drives without your system login credentials.

Dictation history
%LOCALAPPDATA%\ProductiveVoice\history.db
AES-256-GCM

Your local transcripts and search index database. Completely secure and local. Decrypted on the fly as you search or browse your timeline, ensuring other processes cannot read your records.

Custom dictionary
%LOCALAPPDATA%\ProductiveVoice\dictionary.enc
AES-256-GCM

Your personalized spelling corrections, industry acronyms, and custom nomenclature. Encrypted securely on your local file system to prevent harvesting by unauthorized background software.

Style snippets
%LOCALAPPDATA%\ProductiveVoice\snippets.json
AES-256-GCM

Your custom system prompts and formatting instructions (e.g. summaries, translations, formatting guidelines). Stored locally in encrypted format to keep your custom configurations confidential.

By absence

Things Productive Voice literally does not have.

The strongest privacy guarantee is the one enforced by architecture: data we never collect can't leak, can't be subpoenaed, can't be sold.

  • User account database
  • Audio storage bucket
  • Transcript logs
  • Analytics SDKs
  • Telemetry pipeline
  • Ad partner integrations
  • Cross-device sync service
  • Push notification gateway
Payments

How purchases are handled.

Productive Voice uses Lemon Squeezy as its payment processor and merchant of record. All purchase transactions are processed by Lemon Squeezy, which receives the billing information needed to complete your order: your email address and payment details. This data is subject to Lemon Squeezy's own privacy policy and is entirely separate from the app itself.

The app sends no telemetry and transmits audio only to your own configured provider (Deepgram, OpenRouter, or equivalent) using your own API keys. Productive Voice never receives or stores your payment card details.

Privacy you can inspect and verify.

Check the binary, watch the network requests in your proxy of choice. The data flow on this page is exactly what you'll see.