I'm building Kryzz AI, a free, open-source (MIT) Android app for chat, voice and agent tasks. A lot of apps say "privacy-first" and leave it there, so here's the plain version of what that means in mine, including the parts that aren't private.
What stays on the phone
- Chats and memory are stored on the device. There's no Kryzz account and no Kryzz server.
- API keys are yours. You paste them in, and they're encrypted with the Android Keystore. No keys ship inside the APK.
- Generated files (DOCX, XLSX, PDF) sit in private app storage until you choose to share them.
- No analytics, no telemetry, no HTTP logging. I turned those off on purpose, and since the code is MIT you can check that yourself instead of trusting me.
What leaves the phone
This is the part people skip, so I'll be direct:
- The models are not on-device. When you send a message, it goes from your phone to OpenRouter, or to the optional providers you turn on (MiniMax, Fish Audio for voice, Parallel for web research). Those providers see the prompt. That's the trade for using strong models on a phone.
- Web research means the agent fetches pages, so those sites see the requests.
What I can promise is that nothing goes through me in the middle. Your key, your bill, your provider.
Why I care about the boring bits
The agent can run multi-step tasks: it keeps a live plan, runs searches, and writes files. An agent with that much access should be easy to audit. That's also why there's a work log under each answer ("3 searches · read 4 pages · 1 file") and a per-turn cost cap (default $0.25), so you can see what it did and it can't quietly burn your credit.
Honest notes
- The APK on the release page is a debug build, Android 9+. A properly signed release build is on my list.
- I'm one person building this, so "you can read the code" is a real part of the trust story, not a slogan.
Try it
- Release (v1.1.2): https://github.com/kriddss3/kryzz-ai/releases/tag/v1.1.2
- Source: https://github.com/kriddss3/kryzz-ai
If you've shipped an Android app that talks to cloud models, how do you explain the "what leaves the phone" part to users? I'd like to steal a better way of saying it.
Top comments (1)
Thank you for spelling out what leaves the phone! “No telemetry” sounds reassuring, but it doesn't answer that question on its own. More app descriptions like this, please 🙂