That's correct, we process the input and send it through an API. However, as an editing keyboard, we don't track what you type. Moreover, in the UI, we've ensured that we only have access to the text you explicitly select. I understand that privacy is a major concern, so we're currently exploring ways to build a classifier that can locally remove/replace or truncate PII from any text you process, so that it doesn't reach our backend and the API provider.
Not yet, it's API-based. We're developing a smaller model for local grammar, rewriting, and summarization tasks. However, the smaller model needs to be tiny due to OS memory limitations on third-party keyboards. For tasks like co-writing, we'd still rely on the large models, therefore it'll be partially API-based.