Privacy policy
Last updated: 11 November 2026
What Kaiku collects, why, who else receives it, how long it is kept and how to have it deleted. It describes what the service actually does; when that changes, this page changes with it.
Who is responsible
Kaiku is operated by PE Stanislav Vorobev, which decides what personal data the service processes and is responsible for it. This policy covers the kaiku.tech website, every workspace on a kaiku.tech address, and the Kaiku apps for iOS and Android.
Inside a workspace, the company that owns it decides who is invited and what is written there. For that content we act on the company’s behalf: it is theirs, and we hold it to run the service for them.
Write to hello@kaiku.tech with any question or request about your data.
What we collect
Your account: email address, display name, and how you sign in — a password (stored only as a hash), a Google or Apple account identifier, or a passkey. A two-step verification secret is stored encrypted, and API tokens only as a hash.
What you put into a workspace: projects, issues, comments, wiki pages, attachments and anything else you or your colleagues write or upload. Your name appears on what you write. Colleagues in the same workspace can see whether you are online right now and when you were last active.
Sign-in records: when you signed in, how, from which IP address, and a device description such as “Chrome · macOS”. They let us warn you about a sign-in from a device you have not used before, and let you see where your account is signed in.
Signing up: the email address and the IP address the request came from and, if you arrived from this website, the button you pressed, the campaign tags in the link and the site that sent you — and, if you followed a partner’s link, that partner’s code. The partner is told only totals: how many companies came through the link, how many pay and what was credited, never who.
Signing up through an AI agent: you can also sign up by asking an AI agent connected to our MCP server. The agent sends us what you tell it for this — your email address, your name, the name and address of your company and your language — and the name of the program it runs in, such as “claude-code”, which we record as where the account came from. Your agreement to the terms of service and this policy is recorded with its time and a note that the agent passed it on; the agent is asked to show you both documents and to ask you first. The account is created only after you read the code from our email to the agent.
Payments: the invoices issued to a workspace, their amounts and what was received. A card payment is taken by Paddle on its own checkout: your card details, and the email address and country it asks for, go to Paddle and never reach us; we keep Paddle’s subscription and transaction ids, the period paid for, the amount, the tax and Paddle’s fee. A purchase in the App Store or Google Play is taken by Apple or Google, who send us its transaction id, its dates and the price in the store’s currency. For a bank transfer we record the amount and the bank’s reference against the invoice; our bank receives what your bank sends with the transfer, usually the payer’s name and account. Crypto payments are made on the payment provider’s page; we never see or hold wallet keys.
Service records: server logs (the request, its result and the account id — no IP address, no email address) and error reports, from which email addresses, IP addresses, cookies and request bodies are removed before they are stored.
Visits to this website: pages opened, the referring site or campaign, country and device type. They are counted by Vercel Web Analytics without cookies, without identifying anybody and only as totals.
The mobile apps
The apps open the same workspaces as the website, so everything above applies to them. In addition they keep:
A push token, on iPhone and iPad, if you allow notifications — it is how Apple delivers them to your device — with the device type (“iPhone” or “iPad”). The Android app does not receive push notifications yet.
A random identifier created on the device and sent with requests, so that your own devices are recognised and a sign-in from a new one can be flagged. It is not derived from anything about you or your device.
An error report when the app itself fails, sent to our own server the way the website sends its own: the error and where in the code it happened, the screen it was on, the workspace address, your account’s numeric id, and the versions of the app and of the operating system. It is cleaned and kept like the error reports above, for 30 days, and nobody outside Kaiku receives it.
The apps contain no advertising and no third-party analytics, tracking or crash-reporting code. They do not access your location or contacts. They use the camera and your photos only in a chat, when you choose to send a photo: the camera after you allow it, and your photos through the system’s own picker, which gives the app only the photos you select and not the rest of your library. A photo is uploaded as a file of that message and kept like the chat’s other files — encrypted on our servers, for as long as the company keeps its chats. It is the file as the phone hands it over, and we do not remove its metadata: it may carry what the camera wrote into it, such as when and where it was taken, and anyone in the chat can download it. Any other file is uploaded only when you pick it yourself. They use the microphone only for voice input, described under AI features below, and only after you allow it.
AI features
Some features send text to a language model provider, DeepSeek or Anthropic: translating an issue or a comment, the assistant, turning a question into a search, agents you call or hand work to, and replies suggested in the support desk. What is sent is the text the feature works on, when it works on it.
One of them runs without a click. So that search finds an issue written in another language, the title and description of new and changed issues are sent to a model in the background, which writes a short English summary for the search index.
Voice input — speaking to the assistant and dictating a wiki page, on the website and in the apps — records from the microphone only while it shows it is on. The recording goes through our server to a speech recognition service, which returns the words: OpenAI on our key or, where a company has connected its own AI provider key and that provider can recognise speech, that provider under the company’s own agreement with it. The recording is not kept; the words then go on like typed text. Our logs keep a recording’s length, language and cost, never the audio or the words.
Answers can be read aloud by your device’s own voices. That happens on the device: their text is not sent anywhere to be voiced. The speech language you choose is stored on your account and included in “Download my data”.
Search by meaning is computed on our own servers, and nothing is sent out for it.
If a company connects its own AI provider key, its text goes to that provider under the company’s own agreement with it.
We do not use your content to train models, and we do not sell personal data.
Who else receives data
We use the following services to run Kaiku. Each receives only what its job needs.
Hetzner (Germany and Finland): the servers that run the service, the database and its backups.
Cloudflare: storage of attachments and export archives, and the DNS of our domain.
Postmark: sending email — confirmations, notifications, billing reminders, and tips for a new workspace’s owner, each with its own unsubscribe link — and receiving mail sent to the support address.
Our crypto payment provider: the invoice amount and a reference to the workspace.
Paddle.com, our reseller and the Merchant of Record for card payments: what is being bought, the workspace and the account that pays, and what you type into its checkout.
Our bank, if you pay by bank transfer: the transfer and what your bank sends with it.
DeepSeek and Anthropic (language models) and OpenAI (speech recognition), as described above.
Apple: push notifications to iPhone and iPad, Sign in with Apple, and purchases in the App Store. Google: Sign in with Google and purchases in Google Play. A store purchase carries the id of your account, so that it reaches that account. Browsers’ own push services deliver notifications on the website, encrypted so that only your browser can read them.
Vercel: hosting of this website and its visit counts.
Integrations a workspace connects — GitLab, GitHub, a Jira import, an MCP connection — exchange data with those services under the workspace’s own account there.
Some of these companies are outside the European Union: Anthropic, OpenAI, Postmark, Cloudflare and Vercel are in the United States, DeepSeek is in China, Paddle is in the United Kingdom and our bank is in Armenia. What is sent to them is processed there.
How long we keep it
Workspace content: as long as the workspace exists. A workspace whose subscription has lapsed is kept read-only for 12 months and then deleted, together with its attachments and export archives.
Chats: as long as the workspace, unless the company’s owner chooses to keep them for 30, 90 or 365 days. Messages older than that are then erased, together with their files.
Your account and its sign-in records: until the account is deleted.
Sign-up requests — the address and name you typed and the IP address the request came from: 30 days after they were made, whether or not an account was created.
Server logs and error reports: 30 days.
Database backups: up to 6 months — daily copies for two weeks, weekly for two months, monthly for six. A deleted record leaves the backups when the last copy that holds it expires.
Invoices and payment records: as long as accounting rules require, including after a workspace is deleted.
Online status: only the moment you were last active, overwritten each time — there is no history of it.
Your rights
On the website, Settings → Account & sign-in → “Download my data” gives you everything we hold about you as one file. The same tab changes your password and your ways of signing in; to correct your name or email address, write to us.
Any project can be exported as a zip with structured JSON, readable Markdown and every attachment — also while a workspace is read-only.
You may ask us for access to your personal data, to correct or delete it, to restrict or object to its processing, or for a copy to take elsewhere. Write to hello@kaiku.tech; we answer within 30 days. You may also complain to a data protection authority.
Deleting your account
Yourself, at once: on the website or in the Kaiku Tasks app for iOS or Android, open Settings → Account & sign-in → “Delete my account…”, and type your email address to confirm. The account is deleted there and then.
Without the app, or if you cannot sign in: write to hello@kaiku.tech from the email address of the account with the subject “Delete my account”. We confirm the request and delete the account within 30 days.
What is deleted: your ways of signing in, tokens, sessions, devices and push tokens, notifications and subscriptions, workspace memberships and sign-in records. Your name and email address are removed from the account, and your email address and mentions of you are replaced in the texts of the workspaces you worked in.
What stays: issues, comments and pages you wrote in a workspace, and the files you attached to them, belong to the company that owns it. They remain there, shown as written by “Former user”. A name typed as a plain word inside a text is not found and replaced.
Your chat messages do not stay: every message you wrote is erased together with its files and shows in the chat only as a deleted message, so that replies to it still have something to point at. A chat with nobody else left in it — a direct chat whose other person’s account is already deleted, your own chat with an agent, a group you were the last one in — is erased whole. A project’s chat is not: it belongs to the project.
Deleting the account yourself also deletes every workspace you own that has nobody else in it, such as your personal workspace, with everything in it. A workspace you own with other people in it is not left without an owner: remove them from it first, or ask us to hand it over or to delete it. A workspace owner can ask us to delete the whole workspace at any time.
A subscription bought in the App Store or Google Play does not end with the account: it is between you and the store. Turn it off in the store’s subscription settings, or it goes on renewing.
Backups that hold the account expire within 6 months.
Children
Kaiku is a tool for work and is not meant for children. Do not use it if you are under 16.
Changes
When this policy changes, the date at the top changes. If a change affects what we collect or who receives it, we tell workspace owners by email before it takes effect.