Draft for legal review. This page describes what Kemable does today. It has not been reviewed by a lawyer yet and may change before it is final.
Privacy Policy
Last updated 18 November 2026.
In brief
- The app has no account and no telemetry. It talks only to the servers you connect to, and asks GitHub once at launch for a newer version.
- Your passwords stay in Windows Credential Manager on your computer. Your queries and data never pass through Kemable.
- The website counts where visitors come from without cookies and without anything that identifies you.
- Cookies, Google Analytics and the Meta Pixel run only if you click Allow; Cookies at the bottom of every page changes that.
- The macOS and Linux waitlist keeps the name and email you send, only to write to you once when the version is ready.
Who is responsible
Kemable and this website are made by Huỳnh Trung Đức, an individual in Vietnam, as a SoleBuilt project. He decides what is collected and why. Write to huynhtrungduc.growth@gmail.com for anything on this page.
The app
What the app sends
- One update check at launch. When Kemable opens, it asks GitHub for one file,
latest.json, from Kemable's latest release, to learn whether a newer version exists. The request carries nothing about you or your data: no version, no Windows build, no identifier. GitHub sees what any download shows it, such as your IP address. You can turn the check off in Settings › Updates. If you choose Update, the installer is downloaded from the same GitHub release. - Your connections, to where you point them. Kemable connects only to the servers you enter: a database, an SSH server, or a service's API such as Cloudflare D1 or Firebase. What you run there goes between your computer and that server, and nowhere else.
- Nothing else. No usage statistics, no crash reports, no analytics, no advertising identifiers.
What the app keeps on your computer
Everything Kemable remembers stays in its data folder on your computer: the data folder beside the app, or %APPDATA%\kemable.app when that folder cannot be written. Settings › Data shows where it is. It holds:
- your saved connections, credential profiles and saved queries, without their passwords;
- the history of the statements you ran;
- your query pages, settings and the window's place.
Passwords, API tokens and SSH passphrases are kept in Windows Credential Manager, under your Windows account, never in a file. A Firebase key file stays where you keep it; Kemable keeps only its path.
Uninstalling Kemable keeps the data folder unless you tick "Delete the application data". You can delete the folder yourself at any time, and remove the passwords in Windows Credential Manager (their names end in .Kemable).
This website
This website is served by Cloudflare. Cloudflare, as the host, processes the requests your browser makes, such as your IP address, to deliver the pages. The download links lead to GitHub. The website remembers your choice of light or dark theme in your browser's storage, which never leaves your browser.
Counting where visitors come from, without cookies
When you arrive on the website, and when you click a Download link, your browser tells Kemable's own server where you came from: the page, the link's campaign tags (such as utm_source), an ad's click id if the link had one, and the address of the site that sent you, such as a search engine, a social network or an AI assistant. The server keeps that source, what told it (the tag, the click id or the referring site), the time and your country (from Cloudflare, two letters), in a Cloudflare D1 database of Kemable's own. It keeps no IP address, no details of your browser and no identifier, and sets no cookie for it, so none of this can be tied to you. It is used only to learn which links bring people to Kemable.
Cookies, Google Analytics and the Meta Pixel, only if you allow them
The first time you visit, a notice asks whether you allow cookies. Until you choose, and if you choose No thanks, the website sets none of the cookies below except your choice, and loads nothing from Google or Meta. You can change your choice at any time from Cookies at the bottom of every page; taking it back deletes these cookies.
| Cookie | Set by | Kept for | What for |
|---|---|---|---|
kemable_consent | this website | 1 year | Your choice, so the notice is not asked again. Set either way. |
kemable_src | this website, if you allow | 90 days | The first link that brought you here, so a later download or waitlist entry is counted for it. Sent only to this website. |
_ga, _ga_* | Google Analytics, if you allow | up to 2 years | Google measures your visit, the pages you see and your downloads. |
_fbp | the Meta Pixel, if you allow | 90 days | Meta measures visits and sign-ups that came from its ads. |
Google Analytics and the Meta Pixel are loaded only once Kemable uses them, and only after you allow. With them, Kemable allows measuring ads but not personalising them: it does not build audiences from your visit to show you ads elsewhere. Kemable uses these to see which links and ads bring people, never to sell anything about you.
The waitlist for macOS and Linux
The home page has a form for people who want Kemable on macOS or Linux. Only if you send it, the website keeps the name and the email address you type, the systems you picked, the time, and where you came from (as described above), in Kemable's own D1 database. No IP address is kept with them. They are used to count how many people want each system and which links brought them, and to write to you once when each version is ready. They are never sold, shared or used for anything else, and no newsletter is sent.
Why, under data protection law
- The waitlist: your consent, given by sending the form. You can withdraw it at any time.
- Cookies, Google Analytics and the Meta Pixel: your consent, given with Allow.
- Counting where visitors come from: Kemable's legitimate interest in knowing which links bring people, which holds nothing that identifies you.
- The update check: to keep the app you installed up to date, which you can turn off.
Who receives data
| Who | What for | What they get |
|---|---|---|
| Cloudflare | Hosting the website and its database | Your requests to the website; it stores the counts and the waitlist for Kemable. |
| GitHub | Downloads and the app's update check | Your download and update requests, with your IP address. |
| Google Analytics, only if you allow | Your visit, as described above, under Google's privacy policy. | |
| Meta | The Meta Pixel, only if you allow | Your visit and sign-up, under Meta's privacy policy. |
| The servers you connect to | Your work in the app | What you run there. You choose them; Kemable never sees it. |
Where data is processed
Cloudflare serves the website from its network worldwide; Kemable's database is kept in its Asia-Pacific region. GitHub, Google and Meta process data mainly in the United States, under the safeguards their own policies describe for transfers from other countries.
How long data is kept
| Data | Kept |
|---|---|
| Visit counts | Without a time limit: they identify no one. |
| A waitlist entry | Until you have been told that the version you asked for is out, then deleted; or sooner, when you ask. |
| Cookies | As in the table above, or until you take your consent back or clear them. |
| Google Analytics | 14 months, then deleted by Google. |
| The Meta Pixel | As Meta's policy says. |
| What the app keeps | On your computer, until you delete it. |
Your choices and rights
- Turn the app's update check off in Settings › Updates; turn cookies off from Cookies at the bottom of every page.
- Ask to see, correct or delete what Kemable keeps about you, to restrict or object to its use, or to have a copy: write to huynhtrungduc.growth@gmail.com from the address concerned. You get an answer within one month.
- If you think your data was handled wrongly, you can complain to the data protection authority where you live.
Children
Kemable is a tool for working with databases, not meant for children. The app collects nothing from anyone. The waitlist and the cookies are meant for people aged 16 or over; if a child sent the form, write and the entry is deleted.
Security
The website is served only over HTTPS, and its database can be reached only with Kemable's own Cloudflare account. How the app protects your passwords and connections, and how to report a vulnerability, is on the Security page.
Changes
If what the app or the website sends or keeps changes, this page changes before it does, with the date above. Its history is public in Kemable's repository.
Contact
Questions about this policy: huynhtrungduc.growth@gmail.com.