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 would love to know what do you recomend so it doesnt seem weak and seems strong :)
@techsimplified I am thinking over what you are saying. I have to look into it, honestly. I have a bit of a cognitive bias but I am not sure it is well founded in this case.
It is something that might cause some knee jerk reactions. I'm considering it privileged information between friends.
Maybe I will have some time to think it through this weekend. 🙃
@knowprose No rush at all — honestly, that kind of thoughtful consideration is rare and I respect it. Cognitive biases about browser extensions are completely valid, the ecosystem has earned some scepticism over the years. Take your time, happy to answer anything that comes up. Weekend thinking is the best kind. 🙂