Privacy

Hanoki stores your chats, folders, workspaces and settings in a SQLite database inside your operating system's application-data directory. That file never leaves your machine unless you copy it somewhere yourself.

API keys are not written into that database in plaintext. They're encrypted through Electron's safeStorage, which on macOS is backed by the system Keychain, so decrypting them requires your logged-in user session.

There is no account, no sign-in, no sync and no licence check. Deleting the app and its application-data directory removes everything Hanoki has ever kept about you.

Only the requests you cause. When you send a message, it goes to the provider you selected for that message — Anthropic, OpenAI, Google, OpenRouter, Groq, xAI, Mistral, Together AI, DeepSeek, Cohere, Hugging Face, or an OpenAI-compatible endpoint you configured. When you list available models, Hanoki asks that provider's models endpoint. That's the extent of it.

Those requests are subject to the privacy policy of whichever provider you chose, and Hanoki has no visibility into them. If you'd rather nothing left your machine at all, point Hanoki at a local runtime such as Ollama and nothing will.

There is no telemetry, no analytics SDK, no crash reporter and no update check. The app does not phone home — which is also why updates are manual.

hanoki.app is a static site. It sets no cookies, runs no analytics, embeds no tracking pixels, and loads no third-party scripts or fonts — the typefaces are served from this domain precisely so that visiting the page doesn't tell anyone else that you did.

It is hosted on Cloudflare, which processes ordinary server logs (including IP addresses) to serve and protect the site. Following a link to GitHub or Discord hands you over to those services and their own policies.

If any of this changes, the date at the top of the page changes with it, and the diff is public in the repository.

Questions are welcome at hello@hanoki.app, in the Discord, or as an issue on GitHub. Security reports have their own process in the repository's SECURITY.md — please don't open a public issue for those.