Security

Last updated 18 November 2026.

Kemable holds the keys to your databases, so this page says plainly what it does with them. Every claim here can be checked in the source.

Passwords stay in Windows Credential Manager

  • Passwords, API tokens and SSH passphrases are kept in Windows Credential Manager, protected by Windows under your own account. They are never written to a file or a log.
  • A saved connection's password is sent only to the host, port and user it was saved for. Change any of them and Kemable asks for the password again rather than send it somewhere new. An SSH secret is bound to its SSH server in the same way.
  • On a computer shared by several Windows users, each user's passwords and trusted SSH servers are their own, even when Kemable is installed for everyone.

Your data goes straight to your servers

  • Kemable has no server of its own. Queries and rows go between your computer and your database, and nowhere else.
  • Network engines connect with TLS through rustls and the Windows certificate store. Each connection has its TLS setting; Verify fullchecks the server's certificate against its name. Cloudflare D1, Firebase and Supabase are reached over HTTPS.
  • Through an SSH tunnel, the server's host key is checked against your own known_hosts and Kemable's. A server seen for the first time shows its key's fingerprint and waits for you to trust it. A server whose key has changed is refused, as ssh refuses it.

Changes are shown before they run

  • Edits, imports, drops and truncates show the exact statements they will run before you confirm, and saving edits is all or nothing.
  • The row limit never cancels a statement that writes.

No telemetry

The app sends no usage statistics, crash reports or identifiers. Its one request of its own is the update check at launch, which carries nothing about you and can be turned off. The Privacy Policy has the details.

Updates are signed

  • Each installer is built by Kemable's release workflow on GitHub and signed there, with a key that never leaves it. The app installs an update only when its signature matches the key built into the app; anything else is refused.
  • The installer does not carry a Windows code-signing certificate yet, so Windows may warn on the first install. Download Kemable only from its GitHub releases.

This website

The website is served only over HTTPS. It asks for no password. Its database, which holds the visit counts and the waitlist, can be reached only with Kemable's own Cloudflare account.

Open source

Kemable is open source under the AGPL-3.0, so anyone can read how it handles credentials, connections and updates, and build it themselves.

Report a vulnerability privately

Use GitHub's private vulnerability report, or write to huynhtrungduc.growth@gmail.com, in English or Vietnamese. Never open a public issue for a vulnerability. Say what is affected and its version, your Windows version, the steps or a proof of concept, and what an attacker gains; leave real passwords and private data out. The full policy, with what is in scope, is SECURITY.md. Fixes ship in a new release, so check the latest one first.