Terms of Service

Acceptance

These Terms are an agreement between you and OWDS Inc. ("we", "us"), which operates Kairoku. They cover the hosted web app at kairoku.io and app.kairoku.io, this site, the desktop app and the kairokud daemon it installs, the kairoku CLI, the Claude Code plugin and the MCP endpoint, together "the service".

By creating an account or using the service you accept these Terms. If you do not accept them, do not use the service.

How we handle data is set out in the Privacy Policy at /privacy, which is part of this agreement.

Who may use Kairoku

You must be at least 16. The service is not directed at anyone younger and we do not knowingly allow accounts for them.

If you create or join a team workspace for a company or other organisation, you confirm you have authority to bind it to these Terms, and "you" then means both you and that organisation.

Inside a team workspace, what you create and configure belongs to the organisation rather than to you, and every member can see it: the Atlassian, GitHub and GitLab connections, the MCP access tokens, the OpenRouter key, project and organisation secrets, agent roles, the machines you register, and your chats with their message history. Values are the exception: no stored secret or token is rendered back to anyone, so a member sees the row and its name, not the value. Your own profile, email addresses and sessions are not part of that; they live in Clerk and stay yours.

What the service is

Kairoku is a workspace for planning, building and recording software releases, with AI agents as participants. It has four surfaces:

1. The hosted web app: projects, releases, plan items, documents, activity, chat and the Floor.
2. The desktop app and the kairokud daemon on your own machine: Teammates, Slack, the integration catalog, automations and playbooks, with a local vault for credentials.
3. The kairoku CLI, which installs the Claude Code plugin and runs the orchestration daemon on agent machines.
4. One MCP endpoint, exposing eleven tools (six read, five write) to any MCP client, reached by OAuth browser sign-in or a personal access token.

The docs at https://docs.kairoku.io are the reference for what a feature does today; where they and these Terms disagree on a legal question, these Terms govern.

Early access, and what that means

Kairoku is an MVP under active development. Features change, move between surfaces and are sometimes withdrawn; nothing you rely on today is frozen in place by these Terms.

We may change, suspend or withdraw any part of the service. We publish no record of those changes and run no announcement channel: there is no in-app notice surface, and the service sends no email of its own beyond the sign-in and verification codes Clerk sends. A material change to these Terms appears here, with a new effective date.

Accounts, organisations and credentials

Identity, sign-in, sessions and organisations are handled by Clerk. You are responsible for your credentials and everything done under your account.

You are equally responsible for every token you mint or paste in:

• MCP personal access tokens, which permanently carry whichever workspace was active when minted.
• Daemon tokens for the machines you register.
• Access tokens and API keys for GitHub, GitLab, Atlassian, OpenRouter, Slack and anything you install from the integration catalog.
• Project and organisation secrets you store for dispatched runs.

Tokens we issue are stored as hashes only and shown once, so keep your own copy safe. Revoke anything you think is exposed: MCP tokens in Settings, sessions in your profile. Tell us at support@owds.ca if an account may be compromised.

Share links are a deliberate exception to sign-in: anyone holding one reads without an account. A document link gives that document with its attachments; a release link gives the release record only: its scope note, and the release's plan items and documents by title with their status, but no document body and no attachments. They do not expire on their own, so treat a link as public the moment you send it.

Your content

You own everything you put into Kairoku: plans, documents, comments, briefs, agent instructions, chats, attachments, and the repository content you point us at. We claim no ownership.

You grant us a worldwide, non-exclusive, royalty-free licence to host, store, copy, transmit, display and process your content, for these purposes only:

1. Running the service for you and the workspace the content belongs to.
2. Sending content to an AI provider when you invoke an AI feature, as described below and in /privacy.
3. Sending content to a system you connected, when you or an agent on your instruction asks us to.
4. Serving a share link you created, to whoever holds it.
5. Keeping the service secure and working, including the operational copies our providers hold while running their services.

The licence lasts as long as the content does. Deleting an object ends it for that object; because closing an account removes nothing by itself, the licence over what stays runs until the content is deleted, by you or by us on the request described in /privacy. We do not use your content to train models and we do not sell it.

You are responsible for having the rights to what you upload, and for what agents write into your workspace on your instruction.

Acceptable use

Do not:

• Upload or generate unlawful content, or content that infringes someone else's rights.
• Use the AI features to produce material that breaks the AI provider's own policies, or to resell model access, benchmark providers at volume, or route other people's traffic through our provider key.
• Try to reach a workspace, project, document or run that is not yours, or use a credential you were not issued.
• Try to defeat the human-only gates. Manual test and flow test verification, the merge, the Done transition and any deletion are human acts by design. Do not work around that with a script, a forged actor, or an agent instructed to present itself as a person.
• Scrape share links at scale, enumerate tokens, or crawl the service in a way that degrades it for anyone else.
• Probe, load test or attack the service. Reporting a vulnerability in good faith to support@owds.ca is welcome, not a breach.
• Resell or sublicense the hosted service.

AI turns on our provider key are capped per workspace per UTC day. When the cap is reached the feature stops for the rest of that day and tells you to add your own OpenRouter key. Turns on your own key are not counted by us, and your limits there are OpenRouter's. Other rate limits may apply, and we may throttle, suspend, or remove content or accounts that break these rules.

Third-party services and integrations

Every integration is optional. Connecting one instructs us to act on it with the credential you supplied, for the calls that feature needs: reading repository and issue state, pushing plan structure you approve from the Sync tab, publishing a document to a page. Creating a Jira issue or a Confluence page is always your push from the Sync tab; with auto-sync on, later updates to issues and pages already linked can be sent by an agent's tool call, logged as the agent.

Your use of those systems stays governed by your agreements with them. We are not responsible for Atlassian, GitHub, GitLab, Slack, Anthropic or OpenRouter: not their uptime, pricing, API or scope changes, or the data they hold. If a provider goes down, revokes a token or removes an endpoint, the features that depend on it stop working, and that is not a breach by us.

Check that using Kairoku with a connected system is permitted by your agreement with it.

AI output

AI features produce text, plans, documents and code. Treat all of it as a draft.

• Generated content can be wrong, incomplete, out of date, or confidently invented. Review it before acting on it, and do not ship generated code or publish a generated document without reading it.
• The same prompt can produce different output on different runs, and output is not unique to you.
• Agents act under your instruction and with your credentials. What an agent writes into your workspace, or into a system you connected, is your content and responsibility.
• Over the MCP surface an agent cannot mark an item done or delete anything: the status tool refuses done and no delete tool exists. Elsewhere this is a rule we hold ourselves to rather than one the code enforces, though an agent may record a closure a human directed. Verification, the merge and the Done transition stay human acts, and yours.
• By default your prompts and the content they carry go to Anthropic, called with our key; with your workspace's own OpenRouter key they go to OpenRouter and the provider you chose there. /privacy sets out what is sent in each case.

What Anthropic does with inputs sent through its API is governed by Anthropic's own commercial terms of service at https://www.anthropic.com/legal/commercial-terms, which we do not control. For OpenRouter and the provider you select there, what applies are the terms you accepted with them. Read both yourself before sending anything sensitive.

Source code

The kairoku CLI, the orchestration daemon it runs and the Claude Code plugin are public at https://github.com/owds-inc/kairoku, along with the spec and docs that go with them. That repository carries no LICENSE file today, though its package.json declares MIT, so the position is unsettled until we publish one; if we add one, its terms govern from then on. The hosted app's source is not published, and these Terms cover the hosted service.

Fees

The service is free while Kairoku is an MVP. There is no paid plan, no subscription, and so nothing to cancel or refund.

We may introduce paid plans later. No charge can apply unless you choose a plan and enter payment details: there is no billing in the service today and no mechanism here to announce one.

Termination

You can stop at any time, and delete your account from Settings, Profile, which removes your profile, email addresses and sessions in Clerk. Nothing in our own database is removed by that: there is no purge job, so rows in your personal workspace stay until someone deletes them, and anything the organisation owns stays with it. To have everything tied to your account removed, email support@owds.ca from the address on the account; a person does it by hand, as /privacy sets out. We cannot delete what you pushed to Jira, Confluence or a repository.

There is no data export and no tooling for one, so take copies of anything you want to keep before you delete an account or a project.

We may suspend or terminate your access if you break these Terms, if your use puts the service or another user at risk, or if the law requires it. We may also discontinue the service, or part of it, and where practical we will say so on this page first.

The licences above run with the content rather than with your account, so termination does not end them by itself: each ends as its content is deleted, and we may keep what the law requires. The sections on disclaimers, limitation of liability and indemnity survive.

Disclaimers

The service is early-access software, provided "as is" and "as available", without warranties of any kind, to the maximum extent permitted by law. We disclaim the implied warranties of merchantability, fitness for a particular purpose and non-infringement.

We do not warrant that the service will be uninterrupted, timely, secure or error-free, that generated output will be accurate, or that no data will ever be lost. There is no service level agreement, no uptime commitment and no general support commitment; the deletion request in the Privacy Policy and under Termination is the one thing we undertake by hand. Keep your own backups of anything you cannot afford to lose.

Limitation of liability

To the maximum extent permitted by law, neither party is liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue or data, or the cost of substitute services, even if the possibility was known.

To the maximum extent permitted by law, our total liability arising out of or relating to the service and these Terms is limited to the greater of the amounts you paid us in the twelve months before the claim and 100 US dollars. The service is free today, so in practice the cap is 100 US dollars.

Nothing here excludes or limits liability that cannot be excluded or limited by law.

Indemnity

You will defend and indemnify us against third-party claims, and their reasonable costs, to the extent they arise from your content, your use of the service in breach of these Terms, or your use of a connected system in breach of your agreement with it.

Changes to these Terms

We may change these Terms. When we do we will update the effective date printed on this page, which is the whole notice mechanism: we publish no record of changes and send no announcement email. Continued use after a change means the new version applies. The current version is always at /terms.

Governing law

These terms are governed by the laws of the jurisdiction in which OWDS Inc. is incorporated, without regard to conflict-of-law rules.

Contact

OWDS Inc.

support@owds.ca