Privacy
This page is about this website and its demo. An instance you install is yours: you hold the data, you decide what it is for, and your organisation’s own notice is the one that applies — not this one.
Last updated 25 October 2026
In short
- This site collects nothing. No analytics, no advertising, no tracking scripts, no cookies.
- The demo runs in your browser. Its board lives in this browser’s storage and is never sent anywhere.
- There is no account here. You cannot sign in to this site, and there is no server-side copy of what you do in the demo.
- An instance you run is your own. This project has no access to it, no copy of it, and no way to read it.
- The only thing that sees a visit is the host serving these pages, which keeps request logs the way any web server does.
What this site is
Two things: a handful of static pages like this one, and a demo at /app that is the
whole application running with no server at all. The pages are plain HTML and one stylesheet; the
demo is the same build a team installs, reading and writing only this browser’s storage. Neither
has an account system, because neither has a database.
What is collected
Nothing about you. There is no analytics service, no advertising pixel, no session cookie, no font requested from somebody else’s server, and no third-party script of any kind. Opening these pages makes requests to this domain and to nothing else.
That is not a promise in prose: a test records every request the public pages make and fails the build if one leaves this origin. The security page lists what is claimed there, and what is deliberately not claimed.
The demo
The demo keeps its workspace in your browser’s localStorage — boards, cards and all. It
is not transmitted, not backed up by us, and not visible to anybody but you. Clearing this site’s
data removes it, so export the workspace first if you want to keep it: the board’s own menu writes
it to a file, and that file is the data — the same file the
backup runbook restores from.
An instance you install
Kanban Toolkit is software a team runs on its own machine. When you install it, you are the controller of that data: the accounts, the boards, the audit trail and the database file all live on hardware you choose, under your policy. This project has no access to it, holds no copy of it, and cannot recover it for you — which is why the install guide puts backups first.
Some of what it does with that data is worth saying here, because it is about people rather than rows. A person is removed by an administrator: their account, their ways in and their sessions go, the work they did stays, and every place that names them reads “Former member”. A workspace is deleted by its administrator, and its accounts are deleted with it — which is the end of that instance’s data, not a copy of it somewhere here. Export anything you want to keep before either act, because neither can be undone.
What the software stores when you run it is described where a person would look for it: the documentation for the database and the audit trail, and the security page for the session and password handling. If you are responsible for an instance, your own privacy notice — for your staff, your contractors, your customers — is the one that has to be written, and no page here can stand in for it.
What the host sees
| Who | What they receive | Why |
|---|---|---|
| The host serving these pages | An address, a request, a user agent, and the time — the request log every web server keeps | To serve the page and to keep the site up |
| Nobody else | — | There is no analytics, no CDN of somebody else’s, and no form on this site to submit |
Who is behind this deployment
Rendered from this deployment’s own configuration, so it cannot quietly go stale. The fuller page — what each one is for, and what it is not — is sub-processors.
- your identity provider — identity provider, when an operator brings their own. It sees whatever the provider an operator configured sees. Kanban Toolkit asks it for an address and a name, and receives nothing else.
- the machine this runs on — hosting. It sees everything the database holds: accounts, workspaces, cards and the audit trail. On the demo instance that is a Cloudflare Worker with a D1 database; a self-hoster's is their own server.
- the error log — diagnostics. It sees a message, a stack trace, the path of the page, the build and the browser — never a query string and never an IP address, which are not collected.
An instance you install has processors of your choosing — your host, your identity provider, your mail relay — and its own list is the one you publish, because you are the controller of that instance’s data.
Your rights
Because this site holds nothing about you, there is nothing to access, correct or erase. The one exception is a message you send us: a support or security report is kept as long as it takes to answer and follow up, and you can ask for it to be deleted by writing again from the same address.
Changes
When this page changes, the date at the top changes with it, and the change is in this repository’s history — there is no separate change log. It is worth re-reading if you are relying on it for something, because nothing else records it for you.
Contact
The issue tracker is where anything about this page goes, and that includes a security problem. The same link is in security.txt, which is the machine-readable half of the security page.