Privacy Policy

• We collect the account details you sign in with and the work content you put into the product.
• The mobile app carries no analytics, no advertising identifier and no crash-reporting SDK. It talks to one server: the Klindi platform you sign in to.
• We do not sell, rent or share your data with advertisers, and we do not track you across other apps or sites.
• Your content is not used to train anyone's AI models.
• You can ask for a copy of your data or for your account to be deleted, at any time, by email.

Three kinds of information, and nothing else.

Account details

Your name and email address, your password (stored only as a one-way scrypt hash — we cannot read it), and, if you turn on two-factor authentication, its state and your unused recovery codes as hashes. The authenticator secret itself is stored encrypted, separately from your account record.

The work you put in

Projects, tasks and comments, uploaded files, chats and their answers, presentations, meeting recordings and their transcripts, offline notes, and metadata about the repositories a workspace connects. This is your material; we store and process it so the product can do what you asked it to.

Technical records

A signed session cookie that keeps you logged in, your IP address, ordinary server request logs, and — from the mobile app — the app version and the kind of device. We keep these to run the service and investigate faults, not to profile anyone.

When a workspace connects GitHub or Slack we store an installation or workspace identifier, which is a public number. We do not store long-lived repository credentials: access is a token minted for a single operation that expires within the hour.

• Your sign-in session for each account is stored in the iOS Keychain or the Android KeyStore, on the device, and nowhere else. Signing out removes it.
• There is no analytics SDK, no advertising identifier, no crash-reporting SDK and no third-party tracker of any kind in the app.
• The app connects to exactly one server — the Klindi platform address it was built for — plus Google Fonts, which is fetched on first launch to render the app's typefaces and reveals your device's IP address to Google in the process.
• Files you choose to upload go to Klindi's storage. The file picker only ever sees the file you pick.
• Some parts of the product open in your browser rather than in the app. Once a link opens, your browser's own privacy behaviour applies.

• We do not sell, rent or trade your personal data, and we never share it with advertisers or data brokers.
• We run no advertising, and we do not track you across other apps or websites.
• We do not use your content, your files or your conversations to train AI models — ours or anyone else's.
• We do not read your workspace content except when you ask us to help with something specific, or when we have to in order to fix a fault or meet a legal obligation.

• To provide the product to the organization you belong to — the contract we are performing.
• To keep accounts secure and to detect abuse — our legitimate interest, and yours.
• To send the notifications you or your workspace turned on.
• To record and transcribe a meeting, which we do only when someone asks for it (see below).
• To meet legal obligations, when they apply.

Several features answer questions, write code, draft boards or narrate presentations by sending the relevant material to a model provider and returning the result. What gets sent is what the feature needs — the question you asked, the items you referenced, and the repository or project content the run works on.

We use these providers under business agreements that prohibit training on the content we send. Your material is processed to produce your answer and is not added to anyone's training set.

AI work that needs a machine runs on a virtual machine we launch for that job and shut down when it is finished. The machine holds a checkout of the material it was given and is destroyed with it.

When someone asks Klindi to attend a call, a recording bot joins the meeting, records it and produces a transcript. The bot is visible to everyone in the call.

Recording a conversation requires the consent of the people in it, and the laws that govern that differ by country. The person who invites the bot is responsible for having that consent. Recordings and transcripts are kept in the project they belong to until someone deletes them.

We run on infrastructure and services from other companies. Each one sees only what its job requires.

Amazon Web Services

Hosting, file storage and the virtual machines that run background work. United States.

MongoDB Atlas

The database.

Anthropic

The Claude models behind code and task features.

OpenRouter and Google

The Gemini models behind project chat.

OpenAI

Realtime voice for the call agent.

ElevenLabs

Speech synthesis for presentation narration.

Recall.ai

Joining, recording and transcribing meetings.

Resend

Sending email notifications.

Slack

Delivering notifications to a workspace that connected it.

GitHub

Repository access for the workspaces that connected it.

Turso

Databases for small apps published from the product.

Google Fonts

Typefaces for the website and the mobile app.

Our servers and storage are in the United States, and the providers above process data there and in the regions they operate. If you are in the European Economic Area or the United Kingdom, this means your data is transferred outside it; we rely on the standard contractual clauses our providers offer for those transfers.

• Work content stays until you or your workspace deletes it, or until the organization's account is closed.
• Account records are removed when the account is deleted, as described below.
• Server and request logs are kept for a short operational window and then discarded.
• Backups are overwritten on their own cycle, so deleted material can persist in a backup for a limited period after it disappears from the product.

• Everything travels over TLS. Passwords are stored as scrypt hashes and are never recoverable, by us or by anyone who obtains the database.
• Every credential the product has to use — an access token, an SSH key, an authenticator secret — is encrypted and stored apart from the records that reference it. No account or workspace record holds a secret in readable form.
• Access to a repository is a token minted for one operation and expired within the hour, rather than a key that lives on a machine.
• Two-factor authentication is available on every account and we recommend turning it on.
• Small apps published from the product run isolated from each other, each with only its own configuration.

No system is perfectly secure. If we ever discover a breach affecting your data, we will tell you and the relevant authorities as the law requires.

Depending on where you live you may have the right to access your data, correct it, export it, have it deleted, object to how we process it, or complain to a data protection authority. We honour these requests wherever we can, regardless of where you live.

Write to hello@klindi.com and we will answer within 30 days. Because most content in Klindi belongs to the organization that owns the workspace, some requests have to be routed through it — we will tell you if that applies and who to ask.

Klindi has no public sign-up, so accounts are closed the same way they are opened — by asking. Email hello@klindi.com from the address on the account with the subject "Account deletion".

• We confirm the request with you, so that nobody else can close your account.
• Your account record, your sign-in credentials and your personal settings are deleted within 30 days.
• Content you created inside a workspace belongs to that organization and is kept or deleted on its instruction — we will tell you which applies to yours.
• Backups containing already-deleted material age out within 90 days.

Klindi is a workplace tool and is not directed at children. We do not knowingly create accounts for anyone under 18, and we delete any we learn of.

If we change how we handle your data we will update this page and the date at the top of it. When a change is significant we will also tell the workspaces it affects directly rather than relying on you to re-read this page.

Questions about this policy, requests about your data, or anything else: hello@klindi.com.