Privacy
A short description of what Kanboard collects and why. Last updated 17 September 2026.
What this covers
This policy applies to the Kanboard website and product. It explains the information we collect when you visit, create an account, use a workspace, connect a tool, or contact support.
Information we collect
- Account details you provide: first name, last name, email, and a password stored by our authentication provider.
- Workspace content: projects, tickets, comments, plans, invitations, activity, and files you import, such as Jira CSV exports.
- Integrations you connect: GitHub installation details, personal agent API keys for Cursor, Claude, or Codex, and MCP client connections you authorize.
- Support messages: name, email, subject, and message when you write to us.
- Technical data needed to run the service: a signed-in session cookie, and local preferences such as sidebar state stored in your browser.
How we use it
We use this information to operate Kanboard: create and sign in to accounts, run your workspaces, send confirmation emails, reply to support, complete the GitHub and agent actions you request, and keep the service secure. The support form includes a hidden field used only to ignore automated spam.
Who we share it with
We share data with the processors that run Kanboard: our database and auth host, our support email provider, and our hosting provider. When you connect GitHub or an agent provider, we send the data those tools need to complete the action you asked for. We do not sell your personal information.
Cookies and local storage
Kanboard uses an HttpOnly session cookie to keep you signed in. The board may also store sidebar and preview-workspace preferences in your browser. We do not use advertising cookies or third-party analytics.
How long we keep it
We keep account and workspace data while your account is active. Support messages are kept long enough to reply and operate the service. You can disconnect integrations at any time.
Your choices
You can update your name in account settings, revoke MCP connections and agent keys, sign out, or ask us for access or deletion through Support.
Changes
If this policy changes, we will update this page with a new date.
