Most privacy discussions about dictation stop at the microphone. That is the wrong place to stop. A dictation tool is a keyboard replacement, which means it sits inside whatever app you are using, at the moment you are using it — and the text around your cursor is often more sensitive than the words you say out loud.
What is optional
“If you enable the optional Context Awareness feature, we may collect limited, relevant content from the specific app in use (such as the text on the screen) to enhance the accuracy of Wispr Flow's Outputs.”
Opt-in, and described accurately. If you turn Context Awareness on, expect the service to read text from the active window. That is the deal, it is disclosed, and it can be turned off. Nothing unfair is happening.
What is not optional
“Wispr always uses information about the app you are dictating in (e.g. app name) to format messages (e.g. formal tone in email, casual tone in messages). It also takes into account the surrounding textbox content to help determine correct capitalization and punctuation, and to edit text with Command Mode.”
The word is always. App identity and surrounding textbox content are part of the product, not a feature you enable. It is easy to see why: tone selection and punctuation repair genuinely need context, and the results are better for it.
It also means that during a dictation, the service sees the field you are typing into. A password reset form, a medical portal, a support ticket containing someone else's data, a draft you have not sent — all of it is "surrounding textbox content" by that definition.
The part that is easy to forget
Cloud dictation already sends your voice. Context awareness sends the neighbourhood. Together they reconstruct something close to "what you were doing at 2:14pm", which is a different and more useful category of data than either alone.
Wispr's answer to this is disclosure plus switches plus an Enterprise tier with data sharing off. That is a reasonable answer from a company that has to run a cloud service. It is not the same as a product where the text never leaves the phone.
What local processing changes
Jot transcribes on the device and inserts into the field you are in, which means the surrounding text is on the same machine it was already on. There is no upload of the window, because there is no upload of the dictation. The optional corrective pass sends a de-identified text snippet — never audio, never app identity — to a zero-retention provider, and it can be turned off entirely.
That is the structural difference in one sentence: Wispr needs context on a server to format your text; Jot has the context already, because the text is being produced there.
Verdict
Context Awareness is opt-in and disclosed. If you turn it on, you know what you are getting, and the accuracy gains are real.
App awareness and textbox context are not opt-in. They are part of the formatting engine, and they mean the service sees more than your voice.
If the surrounding text is the sensitive part — and for anyone dictating into a clinical, legal, or financial system it usually is — Jot on the App Store keeps that context on the device.
Sources
Primary sources, read on the date above. Quotations are verbatim from Wispr Flow's Data Controls and privacy policy.