Privacy

Last updated 18 September 2026

DBClient is a Mac app that connects to your databases. It has no account system and no analytics. This page says exactly what leaves your Mac, and when.

What the app stores

• Connections — names, hosts, ports, databases, usernames and options — in a JSON file under your Application Support folder.
• Passwords, SSH passwords and API keys — in your macOS Keychain, and nowhere else. A connection saved with Save Password off keeps no password at all: the app asks when you connect and forgets the answer when it quits.
• Saved queries, folders and preferences — on your Mac, in Application Support and the app's preferences. A registered licence — its email address and key — is kept in the preferences too.
• Oracle's and IBM's client libraries — only if you connect to Oracle or Db2 — under Application Support, downloaded from those companies when you say so and checked file by file against the digests the app was built with.

What leaves your Mac

• Your database servers. The app talks to the servers you configure, over the tunnels and proxies you configure. Nobody else sees that traffic. Signing in to ClickHouse Cloud through the browser happens on ClickHouse's own page; the sign-in it hands back is kept in your Keychain and used only to reach that service.
• GitHub, for updates. The app checks the published Homebrew cask to learn whether a newer release exists, and downloads the DMG from GitHub when you ask it to install one. Those requests carry no identifier beyond what any download carries.
• Our licence server, only while the app is registered. Registering a licence sends the email address it was issued to, the key, this Mac's serial number, the app's version and the macOS version to azcode.dev, which ties the key to that Mac. A registered copy then asks about once a day whether the registration still holds, sending the same things without the key. The server keeps them with the licence, and a log of those requests (the time, the IP address, the serial number and the app's version) for support and against fraud; it is visible only to us and never shared. A copy that is not registered never contacts the licence server.
• Oracle and IBM, only if you add an Oracle or Db2 connection. Those engines need their makers' client libraries, which the app does not ship. It downloads them from Oracle's and IBM's own servers when you ask, and asks those servers whether a newer client exists only when you press the button for it. Nothing about you goes along beyond what any download carries.
• An AI vendor, only if you set one up. The assistant is off until you enter your own API key. When you ask it something, your question, the schema of the connected database (names and types, never rows unless it runs a read-only query to answer you) and the conversation go to the vendor you chose, under that vendor's terms. Turn it off and nothing is sent.

That is the complete list. There is no telemetry, no crash reporting service, no usage statistics and no third-party SDK that phones home. The docs name each address and each file: What the app connects to Where things are stored

Export files

When you export connections, the file is written where you choose. It may include passwords only if you switch that on, which asks for Touch ID or your login password every time. The file is plain JSON, and the sheet says so.

This website

This site is static. It sets no cookies. It remembers your light or dark choice in your browser's local storage, and it asks GitHub's public API for the number of the latest release so the download button can show it. The pricing page asks our own store, at azcode.dev, what it sells and how it can be paid; that request says nothing about you.

Buying a licence

Buying is the one time we learn who you are. The form sends the name and the email address you type, the plan and the number of licences to our store at azcode.dev, which keeps the order, its invoice and your keys under that email address — so that you can find them again by signing in there with a link mailed to you, without a password. The payment itself happens on the page of the company you choose — Stripe, PayPal or Square — under its own privacy policy. We receive your email address and the details of the order; never your card number or your PayPal sign-in.

Renewing works the same way: the renew page sends the licence key and the email address you type to the store, which answers with that licence's end date and renewal price, and the payment happens on the payment company's page.

To have a purchase record removed, sign in at azcode.dev with that email address and open a ticket.

Questions

Open an issue on the releases repository.