Wispr Flow uses something called context awareness, which is how it knows whether you're dictating a Slack message, an email, or a doc and adjusts the tone accordingly.
To do that, it needs to read what's on your screen. Early on, that raised some concerns from users, there was even a public incident and the CTO had to come out and apologize.
Since then, they've made changes to the product: context data is now processed locally on your device rather than through screenshots, you can toggle it off entirely, and they've earned SOC 2 Type II, ISO 27001, and HIPAA certifications. To toggle it off, just go to Settings > Data & Privacy > Context awareness.
My co-founder Alex said it well: the product is better because it's cloud-first. That's the tradeoff, and it's fine. Honestly, that's where I land too.
In the AI era, a lot of tools need context to do their job. Littlebird, which we also use, see's what's happening on your screen at all times. That's the whole product.
Finally, what I'd argue is that because Wispr Flow had the privacy incident and responded to it publicly, they've probably been more careful about this than most tools in the category that haven't been called out yet. If you're going to try a voice dictation tool, the one that already had to fix its privacy practices is a reasonable place to start.
If you work in healthcare or law and handle genuinely sensitive material, turn context awareness off and sign the HIPAA Business Associate Agreement (BAA). But otherwise, just go ahead and use it.