techsimplified@knowprose Great question! No — the voice processing happens locally in your browser. The Chrome extension uses the Web Speech API for recognition, so audio never leaves your machine. The AI processing for tone-matching and action execution also runs client-side. No cloud servers, no data collection, no accounts required. That's the whole point — privacy-first by design, not by promise. Happy to answer any other architecture questions! 🔒
Taran Rampersad@techsimplified the chrome fies seem the weak point. 😬
@knowprose Yeah, browser extensions do have a trust surface area — but the key difference is local processing vs cloud. Most voice tools send your audio to remote servers. Extensions that process locally in-browser actually reduce the attack surface compared to cloud-based alternatives. The code runs in a sandboxed environment too. Still worth scrutinising though, you're right to question it 👍
@techsimplified yeah. I get it. But that means I would need to run chrome. I don't want it on my systems.
That's the rub.
@knowprose I totally get the security concern about Chrome. That's actually why browser-based voice tools process everything locally - no data leaves your machine. But I respect the principle of keeping minimal browser footprint. What's your preferred browser ecosystem?