Legal

Privacy Policy

Last updated: 12 October 2026

This policy covers the Kogent desktop app, the Kogent mobile app for iOS and Android, the hosted Kogent service both apps connect to by default, and this website.

Two ways to run Kogent

Which parts of this policy apply to you depends on which server the apps are pointed at.

• The hosted service (the default). Out of the box the apps connect to app.kogent.ai, which Kogent, Inc. ("we", "us") operates on rented infrastructure located in the United States. Everything described below applies.
• A server you run. You can point either app at your own Kogent server from the sign-in screen. In that configuration your data goes to that server and never reaches us. We operate nothing in that path, and the collection and sharing sections below do not apply. The operator of that server is the party responsible for your data, including which of the providers below it uses.

What the hosted service collects

• Your email address. Sign-in works by emailing you a one-time code, so we store your address and the codes we issue. Codes are short-lived and single-use.
• Content you create. Specifications, tasks, records, comments, chat messages and other content you create in Kogent are stored on the hosted service so they can sync between your devices and, where you have shared them, with your team.
• Documents you bring in. When you capture a knowledge bundle, the service keeps its own copy of the text of the sources you selected so the pages it writes can cite them. That copy is encrypted at rest with a key scoped to your workspace.
• Code from your repositories. When a workspace runs a build, the service clones the repository it was given access to, and stores the resulting change, its test results and the run's record.
• Keys and credentials your workspace adds. Model provider API keys, repository tokens and connection credentials are stored encrypted (AES-256-GCM) and scoped to the workspace. The desktop and mobile apps can write a key but never receive one back.
• Usage records. Each model call is metered by workspace, model and token count, so budgets and spend can be enforced and shown to you.
• A device push token. If you turn notifications on in the mobile app, it registers a push token so the service can notify you about activity: a signal arriving, a task assigned to you, a run finishing. The token is used only to deliver notifications, and is removed when you sign out or delete your account.
• Security and audit records. The service keeps an access log of significant actions, which includes the acting account's email address and IP address. This exists to detect abuse, to investigate incidents, and, for workspaces that turn on compliance mode, to provide a tamper-evident record of who changed what. See account deletion for how this interacts with erasing your account.

The desktop app

The desktop app is a client of the server you sign in to. Your workspace lives on that server, not on your computer, and the app does not fall back to a local copy of it when the server is unreachable.

What it keeps on your computer

• Your sign-in session and the organization and workspace you last had open, in a settings file in the app's data folder.
• Your Ask Kogent conversations, kept per person and per workspace, so two people who share a computer do not see each other's threads.
• A local copy of the chat channels, messages and member names you can see, so the inbox opens quickly and can be searched.
• A working folder for each workspace that holds the files of any Studio project you preview locally.
• Interface preferences such as layout, recent searches and window size.

What it sends, and where

• To the Kogent server you signed in to. Everything you do in the app. This includes every AI feature: the app holds no model provider keys and never calls a model provider directly. Model calls go through the server's model proxy, described below.
• To E2B, when you open a live preview of a Studio project that runs in a remote sandbox (see below).
• To GitHub, when the app checks for updates. The update check fetches a release manifest from majordomobuild.github.io, which sees your IP address and nothing about your workspace.
• To the public npm registry, when you preview a Studio project on your own machine and its packages need installing.

The desktop app contains no analytics, advertising or crash-reporting SDKs. When something goes wrong, the error stays on your computer.

The mobile app

The mobile app stores your sign-in in the device's secure storage (the iOS Keychain, or storage encrypted with the Android Keystore) and keeps a cache of the records and messages it has synced, so screens open quickly and changes you make offline can be sent when the connection returns. It sends your activity to the server you signed in to, and your push token to that server if you turn notifications on. Like the desktop app, it never calls a model provider directly. It contains no analytics, advertising or crash-reporting SDKs.

Who else sees it

We use a small number of service providers to run the hosted service. They process data on our instructions and for no other purpose:

• Hostinger hosts the servers and databases, in the United States. The chat service and the search index (including the embeddings used for search) run on those servers; we do not send your content to a third party to embed or index it.
• E2B supplies the isolated, single-use sandboxes that builds and live previews run in, on E2B's infrastructure. A build sandbox receives a clone of the repository, the specification and the change being made, and is used for that one run. Without E2B, builds are switched off rather than run anywhere less isolated.
• Resend delivers the email the service sends, such as sign-in codes and signature challenges. It receives your email address and the message.
• Expo, and Apple Push Notification service or Firebase Cloud Messaging deliver mobile push notifications. They receive your push token and the notification text.
• GitHub hosts this website and the desktop app's update manifest.

AI model providers

Kogent's AI features send text to a model provider: Ask Kogent, the agents in your channels, drafting and checking specifications, capturing knowledge bundles, and the coding agents inside a build. Every call goes through the model proxy on the Kogent server. The proxy can reach three providers, and which one handles a call depends on the models your workspace chooses. Claude is the default.

• Anthropic: Claude models, including Claude Code, one of the two coding agents a build can run.
• OpenAI: GPT models, including Codex, the other coding agent.
• Google: Gemini models, through the Gemini API.

A provider receives what the request contains: your messages, the specification, the documents or pages an answer draws on, and during a build the repository code the agent reads and writes. Calls are made with the API key your workspace stores in Kogent (or, for Claude, the subscription your workspace connects), so they run under your workspace's own account with that provider, and that provider's terms for API data apply to them. A workspace that has not added a key for a provider sends nothing to it.

Services your workspace connects

Some features work by connecting a service your team already uses. Nothing is sent to these until someone in your workspace connects them, and what is sent is what the feature needs:

• GitHub: builds clone your repository and open pull requests with the token your workspace provides.
• Slack: each workspace connects its own Slack app. Kogent reads the messages addressed to it and the threads it is asked to act on, replies in Slack, and keeps the messages it handles for up to seven days.
• Google Drive: read-only access, used to bring in the files you choose as sources.
• Google BigQuery: read access to the test datasets you pick, used only from the sandbox that checks a build.

What we do not do

We do not sell your data or share it with advertisers. The apps contain no third-party advertising or analytics SDKs, and we do not use your content to train machine-learning models. Whether a model provider may use API data is governed by that provider's terms for the account your workspace's key belongs to.

This website

kogent.ai is a static site hosted on GitHub Pages. It sets no cookies and runs no analytics. Its fonts load from Google Fonts, so Google receives your IP address when a page loads. The lights switch remembers your choice in your browser's local storage, and that value never leaves your browser.

Retention and deletion

Your data is kept for as long as your account exists. You can delete your account from inside the mobile app at any time, or by writing to us, and doing so erases your identity and personal data. The account deletion page sets out exactly what is erased, what is anonymised, and the one case in which a record is retained. Deleting a workspace deletes its bundle archive along with everything else in it. What the desktop app keeps on your computer stays there until you remove it or uninstall the app.

Children

Kogent is not directed at children under 13, and we do not knowingly collect data from them.

Changes to this policy

If this policy changes we will update the date at the top of this page.