Privacy
Last updated 20 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 license — 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 license server. Registering a license 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 license, 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 asks the server only how many Macs a key registers, from the store's public product list, when the license sheet or Settings ▸ License opens; that request carries nothing about you or this Mac. Asking for a free trial sends the name and the email address you type and this Mac's serial number, with the app's version; the server keeps them with the trial key it issues, so that an address and a Mac get one trial each, and emails the key to that address: the app never receives the key, so entering it confirms the address is yours. A trial whose key was never entered is replaced when the address or the Mac asks again, and the earlier record is deleted. A copy that had a trial and no longer knows when it ends asks the server for the day, sending the email address and this Mac's serial number, when the app starts and when Settings ▸ License opens; the server answers from the trial it keeps and records nothing new.
- 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 the version required by your DBClient build from Oracle's and IBM's own servers when you click Download or Update in Client Setup. It does not check those servers for newer client releases. 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 or choose your own server. When you ask a question, your question, conversation, database structure and current editor text go to that provider. Database rows are sent when the assistant runs a read-only query to answer you. In a console or terminal tab, it receives the current screen, program, folder and system details instead of editor text. It can also read earlier terminal output, including any data shown there. Your provider's terms apply; with a local server, this goes only to the address you chose. Turn the assistant 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 our own server, at azcode.dev, for the list of releases so the download button can show the latest one and the releases page can keep its list current; that server reads the list from GitHub once for everyone, so your browser never contacts GitHub for it. The pricing page asks our own store, at azcode.dev, what it sells and how it can be paid; neither request says anything about you.
Buying a license
We learn who you are only when you buy a license or open a support ticket. The buying form sends the name and the email address you type, the plan and the number of licenses 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 license key and the email address you type to the store, which answers with that license'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 and support
Open a ticket at azcode.dev: sign in with your email address — a sign-in link is mailed to you, there is no password — and write to us there. That account keeps your email address and the tickets you open, with anything you attach to them, so that we can answer; a purchase made with the same address is kept there too. To have it removed, say so in a ticket.