Privacy at Kindgi
Effective on publication; last updated October 13, 2026
This page explains what Kindgi Inc. collects on its websites, why, and what you can ask us to do with it. It covers three sites:
- kindgi.com, our website;
- docs.kindgi.com, our documentation;
- access.kindgi.com, where you sign in to get a pull credential for the Kindgi runtime image and a non-production license key.
The Kindgi SDKs, CLI and runtime you run yourself send us nothing on their own, and the runtime checks its license key offline, without contacting us. The one exception is a renewal you run: kindgi license renew asks access.kindgi.com for your deployment’s next non-production key, and its request carries only the deployment’s renewer id, the time and a one-time value, signed by the deployment (see access.kindgi.com, below). There’s no usage data.
Who we are
Kindgi Inc., a Delaware corporation, is responsible for your information. Questions, requests and complaints about privacy go to contact@kindgi.com (subject: “Privacy”). You can also write to us at Kindgi Inc., 500 Westover Dr #38104, Sanford, NC 27330, USA.
Visiting kindgi.com and docs.kindgi.com
You don’t sign in to either site, and they don’t ask you for anything.
- No cookies, no tracking. Neither site sets cookies, and there’s no tracking or advertising.
- Fonts: our pages load no fonts from other companies. The only script from outside our sites is Cloudflare’s visit counter (see Visit counts).
- Request logs: Cloudflare delivers both sites and protects them from abuse. To do that it processes each request: your IP address, your browser’s user agent, the page you asked for and the time. It keeps short technical logs under its own terms.
- Kept only in your browser: the documentation remembers your light or dark choice (in your browser’s local storage) and the state of its sidebar (in session storage, cleared when you close the tab). Neither is sent to us.
- Search in the documentation runs in your browser. What you type isn’t sent anywhere.
- “Report a problem” in the documentation opens a pre-filled issue on GitHub. Nothing is sent unless you submit it there, and then it’s a public GitHub issue under GitHub’s terms.
- Booking a call: the “Book a call” links take you to cal.com. What you enter there (your name, your email and the time) goes to Cal.com, which manages the booking for us, under its own terms. We use it to meet you.
Visit counts
We count visits to kindgi.com and docs.kindgi.com with Cloudflare Web Analytics. It tells us which pages are read, which sites visitors came from, and their browser and country, so we can improve our sites. The counter sets no cookies and stores nothing in your browser. How Cloudflare does it, and what it keeps, is on Cloudflare’s Web Analytics page. We don’t use it on access.kindgi.com.
Writing to us
When you email us, we get what you send: your address, your message and anything attached. We use it to answer you, and keep it as long as we need to for that and any follow-up. Our email is hosted by Google Workspace.
access.kindgi.com
This section applies only to access.kindgi.com.
What we collect, and why
When you sign in with GitHub, you allow us to read your GitHub profile and email addresses (the user:email permission). We use that access once, at sign-in, and don’t keep the GitHub token.
| What | Why |
|---|---|
| Your GitHub user id and login | To recognize you when you come back, and to name your credentials. |
| Your verified primary email address, and its domain | To check you qualify, to decide whether you get your own key or your company’s shared one, to tell you about your access (for example if a key is revoked or leaked), and to know who uses the program. |
The name of your pull credential (kindgi+dev_gh<your GitHub id>) | To give you the same credential when you come back. |
| Your license key’s details: who it’s for (your login, or your company’s email domain), when it was issued and when it expires | To give you the same key when you come back, and to renew it. We don’t store the key itself. |
| When you first signed in and when you last did | To renew your key on time, and to see which accounts are still in use. |
| Your renewing deployments, if you add any: each one’s name, its public key (never its private key), which key it renews, who added it and when, and when it last asked for a renewal and what came of it | To renew your key from your deployment, and to show you your deployments so you can stop one. |
| A log of what happened to your access: credential created, key issued or renewed, token regenerated, a sign-in refused and why, a deployment added, stopped or renewing, and what came of each renewal | To investigate problems and abuse. |
To qualify, your GitHub account needs a verified primary email address and must be at least 30 days old. If it doesn’t qualify, the page says why. Write to us if you think that’s wrong.
Cookies
access.kindgi.com sets one cookie, __Host-dev-access-state, for 10 minutes during sign-in. It protects the sign-in from forgery. There are no analytics, tracking or advertising cookies, and no third-party scripts.
How long we keep it
- Your account (GitHub id, login, email, domain, credential name, dates): until you ask us to delete it, or until we close the program.
- Your renewing deployments: until you ask us to delete your account. One you stop is kept as stopped, so the same one can’t be added again.
- The access log: deleted automatically about 400 days after each entry.
- A renewal request’s one-time value, and the hourly count of renewal requests (which limits them): deleted automatically within about a day after they expire, 10 minutes after the request and at the end of the next hour.
- The sign-in cookie, and its matching record on our side: 10 minutes.
- Technical request logs at our hosting providers, which can include your IP address: up to 30 days. Our own service logs record only the page, the result and the time, never your IP address, a token or a key.
- After you ask us to delete your account:
- your account, your renewing deployments and your access log are deleted;
- your pull credential is deleted, so image pulls with it stop;
- a personal key is revoked, and we keep a short record of that revocation (the key’s dates and the GitHub account it was issued to) so it isn’t issued again;
- a key shared by your company stays, because it belongs to your company, not to you alone.
- If we block an account or a domain for abuse, we keep a record of the block while it’s needed.
A key you already copied keeps working until its expiry date even after it’s revoked, because the runtime checks keys offline. Non-production keys last 45 days.
Security
- The GitHub token is discarded at sign-in.
- We never store your pull token or your license key. The token stays with Quay, and the key is re-signed from its stored details when you come back.
- For a renewing deployment, we keep only its public key. Its private key never leaves where you keep it, and every renewal request is signed with it.
- Keys are signed in Google Cloud KMS, and our service credentials are kept in Google Secret Manager.
- The page that shows your credentials is never cached or logged.
- Only Kindgi staff who run the service can see the stored information.
What we don’t do
- We don’t sell your information, or use it for advertising.
- We only email you about your access, for example if a key is revoked or leaked, never product news.
Legal basis (where the GDPR applies)
- Giving you access on access.kindgi.com (your account, your credential and your key) is necessary to provide the service you asked for (contract).
- Delivering and protecting our sites, counting visits, security and abuse prevention, answering your emails, and knowing who uses the access program rest on our legitimate interest in running and improving our sites and a free service safely. You can object (see Your rights).
Where your information is, and who processes it
Information from access.kindgi.com is stored in Canada, in Google Cloud’s Toronto region (northamerica-northeast2). These providers process information for us:
| Provider | What for |
|---|---|
| Cloudflare | Delivers and protects all three sites. It processes each request (IP address, user agent, page, time), keeps short technical logs, counts visits to kindgi.com and docs.kindgi.com (Web Analytics), and limits sign-in attempts per IP address on access.kindgi.com. Its network is global. |
| Google Cloud | Runs access.kindgi.com and stores its information (Toronto); signs keys; keeps technical logs. |
| Google Workspace | Hosts our email. |
| GitHub | Signs you in to access.kindgi.com. You authorize it on GitHub’s own page, under GitHub’s privacy terms. It also hosts the issues you file from the documentation. |
| Red Hat Quay.io | Hosts the runtime image and your pull credential, which is named after your GitHub id. Quay records image pulls under Red Hat’s terms. |
| Cal.com | Manages the calls you book with us. |
Kindgi Inc. is a US company, and it stores access.kindgi.com’s information in Canada. Our providers may process information in other countries under their data processing terms. Those terms include safeguards for international transfers, such as the EU Standard Contractual Clauses.
Everything on our sites travels over HTTPS. No system is perfectly secure. If a breach puts your information at real risk, we’ll tell you and the authorities as the law requires.
Your rights
You can ask us to:
- give you a copy of your information;
- correct it;
- delete it;
- stop using it for a purpose you object to.
Where the GDPR applies, you can also ask to move it elsewhere, and to restrict how we use it. Write to contact@kindgi.com. For access.kindgi.com, write from the email address you signed in with, or tell us your GitHub login. We may ask you to confirm it’s you, and we’ll answer within 30 days.
To correct your email on access.kindgi.com, change your primary email on GitHub and sign in again.
If you’re not satisfied with our answer, you can complain to your data protection authority. In the EU or the UK that’s your country’s authority; in Canada, it’s the Office of the Privacy Commissioner (priv.gc.ca).
US state privacy laws. We don’t sell your personal information or share it for targeted advertising, as laws such as California’s define those terms, and we don’t use it to profile you. Wherever you live, you can use the rights above, and we won’t treat you differently for using them.
Children
Our sites and services are for developers. They’re not meant for anyone under 16.
Changes
When we change this page, we update its date at the top. If a change is material, or affects how we use information we already have, we’ll email people who have an access.kindgi.com account at least 30 days before it takes effect.