Taking your data out

1. Open Settings → Export.
2. Choose the Project. Leave Include attached files on for the whole thing; off makes a much smaller archive that still names every file it left out.
3. Press Request export. The archive is built in the background, and you get a notification when it is ready.
4. Press Download next to it in Exports. Downloading works in the web app.

A project may be exported by its lead, by the lead of the project above it, and by the workspace’s owner and administrators. Export keeps working while the workspace is read-only.

The Export tab is shown to workspace administrators. A project lead who does not see it can ask for the same archive through the API below.

One request orders the archive:

curl -X POST https://<workspace>.kaiku.tech/api/exports \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{"projectKey": "ABC", "includeAttachments": true}'

It answers 202 with the export’s id — or, if an export of that project is already on its way, with that one. GET /api/exports lists yours with their status; when it is ready, GET /api/exports/{id}/download returns the file (409 while it is still being built, 410 once it has expired).

One zip, ABC-export-2026-09-17.zip, readable without Kaiku:

• README.md and project.json — the project, and what the archive holds.
• issues/issues.json and one Markdown file per issue: fields, labels, sprint, story points, due date, comments, logged time, links, and the wiki pages tied to it. Archived issues are included.
• wiki/pages.json and one Markdown file per page, with the stored XHTML, comments and attachments.
• The attached files, under issues/attachments/ and wiki/attachments/.

• Not in it: the values of credentials (only how many there are), the values of the project’s own columns, the history of changes, and the issues of projects under this one — export those separately.
• Up to 512 MB of attached files go into one archive. Files past that are left out, and named in the archive and on the export.
• The archive is kept for 90 days after it is ready, then deleted. Delete it earlier with Delete.

Settings → Account & sign-in → Your data → Download my data gives, at once, a JSON file with your settings, the names of your tokens and passkeys, your devices, your sign-ins and your memberships — and a list of the work records that name you (issues, comments, pages), by reference rather than copied. Credentials are never in it. The same file is at GET /api/account/personal-data.

Both are done at your request: write to hello@kaiku.tech from the address of the account. We carry it out within a month.

• An account. Everything personal is deleted — tokens, passkeys, second factor, sessions, notifications, memberships. The work stays, credited to «Former user»; mentions and email addresses in texts are rewritten. An account that still owns a workspace cannot be erased until the workspace has another owner or is erased.
• A workspace. Everything in it is deleted — projects, issues, pages, files, exports. What stays: the invoices and payments we are required to keep, and a record that the workspace existed and was erased, with no content. Members keep their accounts.

• An archived issue is only hidden. It is kept whole, still counts toward the plan, is in exports, and is restored in one action.
• A paused project can be read by everybody in it and changed by nobody, administrators included, until it is resumed.
• A deleted project is gone. Its issues, its wiki and its exports are deleted at once, and there is no bin to restore it from. Export it first.