How Diction handles privacy

Voice keyboards sit in an uncomfortable position. Every app you use, every message you send, every search you type — the keyboard is there. It sees all of it. Most people install a keyboard and never think about this. I did, because I was building one. Earlier this year, someone reverse-engineered a popular voice keyboard and posted their findings. The app was collecting full browser URLs, names of focused apps, on-screen text scraped via the Accessibility API, clipboard contents including data copied from password managers, and sending it all back to a server. There was a function in the binary called sendTrackResultToServer. None of this was in the privacy policy. This is not a hypothetical. It happened. And the only reason anyone found out is because the app was installed on a machine where someone was curious enough to look. That is the problem with closed-source software and privileged access: you cannot verify the claims. A privacy policy is a document. The code is what runs. Ful