---
title: Privacy policy
description: "No tracking, no cookies on kaeso.app, hosting in Germany, and what a Kaeso install sends to update.kaeso.app and kpmr.kaeso.app."
url: https://kaeso.app/datenschutz
markdown: https://kaeso.app/datenschutz.md
language: en
alternates:
  de: https://kaeso.app/de/datenschutz.md
  zh-CN: https://kaeso.app/zh-CN/datenschutz.md
updated: 2026-11-20
index: https://kaeso.app/llms.txt
---

# Privacy policy

No tracking, no cookies on kaeso.app, hosting in Germany, and what a Kaeso install sends to update.kaeso.app and kpmr.kaeso.app.

> Every page, article and docs page of Kaeso is listed in https://kaeso.app/llms.txt.

Last updated: 20 November 2026

This is a translation for your convenience; the [German version](https://kaeso.app/de/datenschutz.md) is binding.

## In short

This policy covers the website kaeso.app, the documentation at docs.kaeso.app, the Kaeso UI component library at ui.kaeso.app, the live demo at demo.kaeso.app, the update service update.kaeso.app, which Kaeso installs ask for new versions, and KPMR, the Kaeso Provider & Model Registry at kpmr.kaeso.app, from which Kaeso installs load their model data. It also explains what happens to your data when you use the Kaeso plugin for Claude or Cursor.

- We use no analytics, tracking or advertising tools. We set no cookies on kaeso.app, docs.kaeso.app, ui.kaeso.app and kpmr.kaeso.app; only the demo sets a cookie, for the sign-in you start there yourself.
- All six services run on our own server in Germany. Cloudflare delivers five of them for us as a reverse proxy, also through data centers outside the EU; requests to update.kaeso.app go straight to our server. Fonts, images and scripts come from our server, not from third parties.
- We delete server logs with IP addresses after 15 days at the latest.
- A Kaeso install sends update.kaeso.app only its version number and the connection data every request carries, and no data from the install. The check can be turned off.
- Likewise, when a Kaeso install loads its model data from kpmr.kaeso.app, it sends only its version number, the list of providers that version supports, and the connection data. KPMR itself keeps no statistics and stores nothing about individual installs. This sync can be turned off as well.
- The Kaeso plugin for Claude and Cursor connects your AI agent only to the Kaeso install whose address you give, and sends us nothing. What the agent reads there is processed by that install and by Anthropic, Cursor or your language model's provider, not by us.

Whoever runs Kaeso on their own servers is responsible for the data in their install. We have no access to installs, and Kaeso sends no telemetry.

## Controller

The controller within the meaning of the General Data Protection Regulation (GDPR) for the processing on these websites, in the demo, by the update service and by KPMR is the provider named in the [legal notice](https://kaeso.app/impressum). Email is the fastest way to reach us, at [mail@kaeso.app](mailto:mail@kaeso.app); please send questions about data protection there as well.

We have not appointed a data protection officer, as the conditions of Art. 37 GDPR and § 38 BDSG are not met.

## Hosting, Cloudflare and name resolution

kaeso.app, docs.kaeso.app, ui.kaeso.app, demo.kaeso.app, update.kaeso.app and kpmr.kaeso.app run on a server we operate ourselves. We rent the server and its network connection from Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany; it is located in their data center in Nuremberg. Hetzner provides the infrastructure and processes data only on our behalf; we have a data processing agreement with Hetzner under Art. 28 GDPR. The data that arises when you use our services is processed and stored on this server in Germany; what Cloudflare processes is in the next paragraph.

We deliver kaeso.app, docs.kaeso.app, ui.kaeso.app, demo.kaeso.app and kpmr.kaeso.app through the network of Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA. Cloudflare works as a reverse proxy: your encrypted connection ends at a Cloudflare server, which passes the request on to our server over a new encrypted connection and returns its answer to you. In doing so, Cloudflare processes your IP address, the URL requested, the User-Agent and the request's other headers, its content, such as a message from the contact form or a sign-in to the demo, and the response. Cloudflare keeps cached copies of static files such as images, scripts, stylesheets and fonts, but not of the pages themselves. Cloudflare tells our server your IP address and the country it assigns to it. Cloudflare also asks your browser to report failed connections to Cloudflare (Network Error Logging); successful requests are not reported. Cloudflare processes this data on our behalf under Art. 28 GDPR, on the basis of its Data Processing Addendum. Your request is processed by the Cloudflare data center nearest to you, which may be outside the EU; Cloudflare processes log data such as IP addresses in its data centers in the USA and Europe for a limited time, which Cloudflare doesn't specify. We use none of Cloudflare's analytics, advertising or script features, and Cloudflare adds nothing to our pages. The legal basis is our legitimate interest in secure, fast and reliably available services, including during attacks, under Art. 6(1)(f) GDPR. Cloudflare is certified under the EU-US Data Privacy Framework, for which the European Commission has adopted an adequacy decision (Art. 45 GDPR); for transfers to other third countries, Cloudflare's agreement contains the European Commission's standard contractual clauses (Art. 46(2)(c) GDPR).

Kaeso installs reach update.kaeso.app directly. For that address, and for name resolution (DNS) of every subdomain of kaeso.app, Cloudflare only answers at which address our server or Cloudflare can be reached. The DNS query is usually made not by your device but by the DNS server of your internet or network provider. Here too, the legal basis is our legitimate interest in reliably available services under Art. 6(1)(f) GDPR.

## Access data and server logs

With every request to one of our services, our server writes an entry to its access log:

- the IP address and port the request comes from
- the date and time of the request
- the host and address requested, including its parameters
- the HTTP method and version, HTTP status code, amount of data transferred and response time
- the TLS version and cipher of the connection
- the browser or program and operating system (User-Agent)
- the page visited before (Referrer), if your browser sends it
- for requests through Cloudflare, also the address of the Cloudflare server and the country Cloudflare assigns to your IP address

Cookies and credentials are not logged. We need this data to deliver the services, keep them stable and secure, find errors and fend off attacks. The legal basis is our legitimate interest under Art. 6(1)(f) GDPR.

The log is closed every night and kept for 14 more days; each entry is therefore deleted automatically after 15 days at the latest. We do not analyze it into statistics about visitors. We keep individual entries longer only when they are needed to investigate a specific security incident, and only until it is resolved.

A protection program on the same server reads the log. If an IP address receives the answer “not signed in” or “not allowed” (HTTP 401 or 403) five times within ten minutes, it blocks that address for two hours, longer if it happens again, at most one week. It keeps the blocked addresses in its own log for at most five weeks.

## Feeds, Markdown and crawlers

For feed readers, search engines and AI assistants, we also offer the content of kaeso.app in machine-readable form: the articles as RSS and JSON feeds, every page as Markdown (its address with `.md`), overviews at `/llms.txt` and `/llms-full.txt`, and the install script at `/install.sh`. A request to these addresses is processed like any other: it is in the server log, and we store nothing else about it.

In `robots.txt` and in the `Content-Signal` headers we state what programs may use our content for. This concerns our texts, not your data. The legal notice is excluded: it has no Markdown version, is in neither the sitemap nor `llms.txt`, is closed to crawlers and asks search engines not to index it.

The install script downloads Kaeso and, if you ask it to, Docker from GitHub and Docker, not from us. Those providers' terms apply to these connections.

## Cookies and browser storage

We set no cookies on kaeso.app, docs.kaeso.app, ui.kaeso.app and kpmr.kaeso.app. For the demo, see below.

If you explicitly choose a light or dark theme on kaeso.app, we store that setting in your browser's local storage under the name `kaeso:theme`, so it stays for your next visit. If you choose “System” again, the entry is removed. kaeso.app stores nothing else on your device. “Copy page” on an article loads its Markdown from our server and puts it on your clipboard only when you click.

On docs.kaeso.app and ui.kaeso.app we store the settings you choose there in the same way: theme, language and the state of the sidebar, and in the documentation also the variant of a code example you last chose. On kpmr.kaeso.app we store the theme you chose and the state of the sidebar in the same way.

These settings do not leave your device and are not sent to us. No consent is needed under § 25(2) no. 2 TDDDG, as storing them is strictly necessary for the function you explicitly asked for: without it, the page could not remember your choice. You can delete these entries at any time in your browser's settings.

## No analytics, no tracking, no third parties

We use no audience measurement tools, no advertising or tracking pixels and no embedded content from social networks or other providers. The only service provider between your browser and our server is Cloudflare, as described under “Hosting, Cloudflare and name resolution”.

We serve the fonts (Inter, Noto Sans SC, JetBrains Mono and Geist Mono) ourselves from our server. Visiting the websites opens no connection to Google Fonts or any other font provider, and your IP address does not reach them.

Our server fetches the changelog, the list of providers, the documentation index, the agent skills and the install script on kaeso.app from GitHub. No data about you is sent in the process; your browser does not connect to GitHub. Our server or your browser loads the pictures of the releases from update.kaeso.app, which is also our own server.

## Links to other websites

The websites link to services of other providers, above all the source code, discussions and releases on GitHub (GitHub, Inc., USA), the packages on npm and crates.io, and our profile on X. Only when you follow such a link does that provider process your data, under its own privacy terms.

On every article, “Open in Claude” and “Open in ChatGPT” open a new chat at claude.ai (Anthropic) or chatgpt.com (OpenAI) that asks to read the article's Markdown. We pass only the address of that public page; your browser sends no referrer. Only with the click does that provider process your data, under its own terms and, if you are signed in there, in your account.

## Update service update.kaeso.app

Kaeso installs ask update.kaeso.app whether there is a new version. An install's gateway does so every five minutes by default, with a random delay of up to one minute, at the earliest after 15 minutes following an error, and, when the service asks it to wait longer, after up to an hour. It also asks when an administrator of the install starts the check by hand and, when automatic updates are set up, in the update window. When there is a new version, the gateway also loads its signed release manifest (`release.json`) from update.kaeso.app.

### What is sent

- the public IP address through which the install's server reaches the internet, and the time of the request
- the address requested, such as `/v1/releases.json?per_page=50` or `/download/v<version>/release.json`
- the identifier `kaeso-gateway/<version>` in the User-Agent, that is, the gateway's version
- technical headers that are the same for every install (`Accept`, `X-GitHub-Api-Version`), and the ETag of the version list last loaded (`If-None-Match`). The ETag is a checksum of the public list, the same for every install and no feature of any install.

Not sent: the install's domain or name, any install or license identifier, data about users, organizations, projects, keys, models or requests, and usage or telemetry data. The code of the check is [public](https://github.com/logicplanes/kaeso/blob/dev/crates/kaeso-server/src/services/updates.rs).

### What we use the data for

We answer the request with the version list or the manifest. Like every request, it is in the server log (see above). We also keep statistics to understand how many installs there are and which versions they run, for example to decide how long older versions need security fixes and how changes to the update path affect running installs.

### Pseudonymous statistics

We do not store the IP address in the statistics. Instead, from the address, or for IPv6 from its /64 network, we derive a shortened cryptographic checksum (HMAC-SHA-256) with a secret random key that exists only on our server. With this pseudonym we store:

- the first and last request and the days on which requests came
- the number of requests and how many of them were answered with “not modified” (HTTP 304)
- the gateway versions reported, each with its first and last request
- whether the IP address lies in one of the published address ranges of large hosting and cloud providers, such as “Amazon Web Services” or “Hetzner”, and otherwise “other network”

Requests from GitHub Actions' address ranges, that is, automated tests, we only count, without a pseudonym. Requests that do not come from a Kaeso gateway, such as your browser loading a release's picture on kaeso.app, we count only by kind of request and kind of program (such as browser, crawler, tool or monitoring service), also without a pseudonym. We do not combine the statistics with any other data, do not try to identify installs or people, and neither share nor publish them.

We delete the per-day details after 400 days, and an install's entire entry 400 days after its last request. If it asks again after that, it counts as a new install.

### Legal basis

The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest lies in reliably informing Kaeso installs about new and security-relevant versions, running the service stably and securely, and aligning Kaeso's maintenance with the versions actually in use. A server's IP address usually allows no conclusions about a natural person. Where it does, such as for a server in a home network, the pseudonymization, the short retention of the logs and the absence of any sharing protect your interests.

### Turning it off

Kaeso does not need the check to run. Whoever runs an install turns off the regular check with `KAESO_UPDATES_CHECK=false`. After that, the gateway asks only when an administrator starts the check by hand, or when automatic updates are set up and the update window begins. Pointing the check at your own mirror with `KAESO_UPDATES_RELEASES_URL` means nothing from the install reaches us. The [documentation on updates](https://docs.kaeso.app/self-hosting/upgrades) describes both.

### Who is responsible for what

We are responsible for the data that reaches update.kaeso.app and kpmr.kaeso.app (see below). The operator of an install is responsible for all data in it; we process no data on behalf of operators. Other connections of an install, such as to GitHub for releases and container images or to the AI providers it uses, do not go to us; those providers' terms apply to them. The [system requirements](https://docs.kaeso.app/self-hosting/requirements) list every one of these connections.

## Model registry kpmr.kaeso.app

KPMR, the Kaeso Provider & Model Registry, is the directory of providers and models from which Kaeso installs load their model data, such as prices, limits and capabilities. Our server keeps KPMR current from public sources itself, without sending any data about you or about installs, and we correct, override and add to the models where needed. An install's gateway loads the model data as a signed catalogue from [kpmr.kaeso.app](https://kpmr.kaeso.app), by default about once an hour, as KPMR suggests, and as a conditional request, so unchanged data is not transferred again.

### What is sent

- the public IP address through which the install's server reaches the internet, and the time of the request
- the address requested, `/v1/catalogue`, with the list of provider ids that the gateway's version supports. This list is the same for every install of the same version and says nothing about which providers an install actually uses.
- the identifier `kaeso-gateway/<version>` in the User-Agent, that is, the gateway's version
- the technical header `Accept`, which is the same for every install, and the ETag of the model data last loaded (`If-None-Match`). The ETag is a checksum of the public document, the same for every install with the same data and no feature of any install.

No data from the install is sent: not its domain or name, nor any install or license identifier, data about users, organizations, projects, keys or requests, or usage and telemetry data.

### What we store

We answer the request with the model data. The KPMR service itself stores nothing about individual requests or installs: it keeps no statistics and no log of its own. Like every request, it is in the server log, as described under “Access data and server logs”.

### Legal basis

The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest lies in reliably supplying Kaeso installs with current model data and running the service stably and securely. A server's IP address usually allows no conclusions about a natural person. Where it does, the short retention of the logs and the absence of any statistics and sharing protect your interests.

### Turning it off

Whoever runs an install turns off the sync with `kpmr.sync = false` or points it elsewhere with `kpmr.url`; then nothing from the install reaches us this way.

### Visiting in a browser

Whoever opens kpmr.kaeso.app in a browser can browse the registry there. We set no cookies there and use no tracking. We serve fonts and scripts ourselves; your browser connects to no third party other than Cloudflare, as described under “Hosting, Cloudflare and name resolution”. The same holds for the requests of an install's gateway. The same server logs with the same retention apply as for our other websites.

## Documentation and component library

docs.kaeso.app and ui.kaeso.app are static websites that we serve from the same server as kaeso.app. This policy applies to them as well: the same server logs with the same retention, no cookies, no tracking and no third-party content; the documentation's search, too, runs in your browser, without an outside service. Their content comes from Kaeso's public source code on GitHub; our server fetches new versions itself, without sending any data about you.

## Live demo demo.kaeso.app

The live demo is a Kaeso install with sample data that we run ourselves, so you can try the console without installing it. One click signs you in as the demo user; you need no account and give no details of your own. The demo allows no changes and calls no AI providers.

- When you sign in, the demo sets the cookie `__Host-kaeso_session`, which carries your session. Without it, the sign-in you ask for is not possible; no consent is therefore needed (§ 25(2) no. 2 TDDDG).
- Like every Kaeso install, the demo stores with each session your IP address, your browser (User-Agent) and the times of sign-in and last use. Other visitors do not see these details.
- To limit abuse, the demo counts sign-ins per IP address and allows no more than 50 in 15 minutes. The count expires after 15 minutes.
- In your browser's local storage, the console remembers the organization and project you last opened and, if you change them, settings such as theme, language, sidebar and the request log's columns (§ 25(2) no. 2 TDDDG).

Every night at 3:30 (German time) we reset the demo to its sample data. This deletes all sessions with everything stored with them, and all counts; a cookie left over after that is no longer valid. The requests are in the server log, as for all our services. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest lies in showing Kaeso and running the demo securely.

## Kaeso plugin for Claude and Cursor

With the Kaeso plugin, an AI agent manages, for you, the Kaeso install whose address you give, such as its organizations, projects, keys, limits and usage. The plugin exists for Claude, in Anthropic's directory for Claude Code, Cowork and the Claude apps, and for Cursor. Its source code is [public](https://github.com/logicplanes/kaeso/tree/prod/plugins).

### What the plugin contains

- instructions for the agent (a skill) that explain the tools of Kaeso's MCP server to it and, while it isn't connected yet, how it connects to your install
- the connection to your install's MCP server at its address followed by `/mcp`: in Cursor through the plugin's setting, in Claude Code through the plugin's setting or the command `claude mcp add`, depending on the plugin's version, and in Claude on the web, in the desktop and mobile apps and in Cowork as a custom connector you add. You enter the address yourself; the plugin has none built in.
- its name, description, icon, license and links to our websites

The plugin contains no programs or hooks that run on your device by themselves, and makes no connection of its own, neither to us nor to third parties. In Claude Code, the skill can guide your agent to run the command `claude mcp add`, under the permissions you give Claude Code like any command; it only adds your install's address to Claude Code's settings. Claude and Cursor get the plugin from our public repository on GitHub or from their provider's directory, not from our servers; those providers' terms apply to that.

### Where data flows

When your agent uses the plugin, data flows only between your Kaeso install, Claude or Cursor, and the providers through which they use their language model:

- Sign-in: Claude or Cursor signs in to your install with OAuth and PKCE. This happens in your browser, in your install's console, where you choose what the agent may do. Claude or Cursor keeps the access and refresh tokens under its own rules; your install stores them only as a hash. If a client uses a public document describing it as its identifier, as claude.ai does, your install fetches it from its address at sign-in.
- Connection: Claude Code and Cursor connect to your install from the computer they run on, usually your own. Claude on the web, in the desktop and mobile apps and in Cowork connects from Anthropic's servers instead, and Claude Code and Cursor, when they run in their provider's cloud, from that provider's servers. The tokens are then kept by that provider, and your install sees its IP addresses.
- Content: What the tools return to your agent reaches Claude or Cursor and the language model your agent uses: usually Anthropic; for Cursor, Anysphere and the model providers Cursor uses; or the provider through which you use the model, such as Amazon Bedrock or Google Vertex AI. Depending on the rights you give the agent, this includes names and email addresses of members, names of organizations, projects and keys, usage, costs and request log entries, and with the right to prompts and outputs also their logged content.
- Your install's log: For each agent it records its name, its model family (such as `claude`), its rights, how you signed in, and when it was authorized and last used, along with the client's name and redirect addresses. These details remain after the agent is revoked and after your account is deleted; Kaeso doesn't delete them by itself. For each tool call it records the tool, its target, the result, the time and the IP address, and deletes the entry after 90 days. Changes made by an agent are in the install's audit log. An agent that makes no request for 90 days loses its access.

When Claude shows a usage view in a conversation, your install itself provides it; it loads nothing from elsewhere.

### What we receive

Nothing. Neither the plugin nor Kaeso's MCP server sends us any data: no content, no tool calls, no tokens, no identifier of your install and no statistics about the plugin's use. We don't learn who installs or uses the plugin; GitHub and the directories show us at most numbers that relate to no person. Only when you follow a link from the plugin, such as to the documentation at docs.kaeso.app, is that request in our server logs like any other (see “Access data and server logs”). The live demo at demo.kaeso.app accepts no agent sign-in.

### Who is responsible

The operator of a Kaeso install is the controller for the data in it, including its agents' sign-ins and logs: you, your employer or whoever else runs the install. They decide for what purpose and on which legal basis they process this data, and can turn agents off for the whole install or for single organizations.

Anthropic is the controller for the processing in Claude with a personal account: for users in the European Economic Area, the United Kingdom and Switzerland Anthropic Ireland, Limited, Dublin, Ireland, and otherwise Anthropic PBC, San Francisco, USA, under [Anthropic's privacy policy](https://www.anthropic.com/legal/privacy). For Cursor it is Anysphere, Inc., San Francisco, USA, under [Cursor's privacy policy](https://cursor.com/privacy). With a business account, such as Claude Team or Enterprise or Cursor for business, your organization is usually the controller and the provider its processor, under their contract. Both providers also process data in the USA, outside the European Economic Area; their privacy policies say on which basis they transfer data there (Art. 44 et seq. GDPR).

We ourselves are neither controller nor processor for this data: like Kaeso, we provide the plugin as open-source software and have no access to your install, to Claude or Cursor, or to your conversations. For the server logs when you visit our websites, Art. 6(1)(f) GDPR applies, as described above.

### In Anthropic's directory

There, the plugin is marked as one that collects user data. That is accurate, because it connects your agent to your Kaeso install, which processes data about you and your organizations and logs your agent's tool calls, as described above. This data stays with your install and with the providers your agent works through; it doesn't reach us.

### Turning it off

You can revoke an agent at any time in your install's console under “Account” › “Agents”; its tokens stop working at once. You remove the plugin in Claude or Cursor. The [MCP server documentation](https://docs.kaeso.app/api/mcp) describes sign-in, rights, tokens and logs in detail.

## Contact by email

When you email us, we process your email address, your name if you give it, and the content of your message to answer your request. The legal basis is Art. 6(1)(b) GDPR where your request serves the performance of a contract or steps prior to entering into one, and otherwise our legitimate interest in answering under Art. 6(1)(f) GDPR. We delete the correspondence twelve months after your request is settled, unless statutory retention obligations require otherwise.

For our mailbox we use iCloud Mail. The provider for users in the European Economic Area is Apple Distribution International Ltd., Hollyhill Industrial Estate, Hollyhill, Cork, Ireland. Your message is stored on Apple's servers. The legal basis is our legitimate interest in a reliable email service under Art. 6(1)(f) GDPR. Where Apple transfers data to Apple Inc. in the USA, it does so, according to Apple, on the basis of the European Commission's standard contractual clauses (Art. 46(2)(c) GDPR).

Emails are usually transferred encrypted between mail servers (TLS), but are not end-to-end encrypted. Please do not send us particularly sensitive data by email.

Report security vulnerabilities confidentially through GitHub (GitHub, Inc., 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107, USA). GitHub's privacy terms apply; GitHub is certified under the EU-US Data Privacy Framework (Art. 45 GDPR). We process your report to assess and fix the vulnerability (Art. 6(1)(f) GDPR).

## Contact form

When you write to us through the [contact form](https://kaeso.app/contact), we process your name, your email address, your message, the language of the page and the time it arrived, to answer your request. Every field is needed so we can reply. The legal basis is Art. 6(1)(b) GDPR where your request serves the performance of a contract or steps prior to entering into one, and otherwise our legitimate interest in answering under Art. 6(1)(f) GDPR. Your message reaches our server through Cloudflare, as described under “Hosting, Cloudflare and name resolution”.

We keep your message in a database on our server in Germany and delete it there automatically twelve months after it arrived. If it cannot be delivered by email, it stays there with a note of the error, so it is not lost, and is likewise deleted after twelve months. We also send it as an email to our mailbox, with your address as the reply address; what is said under “Contact by email” then applies to it.

To send it we use the email service Resend of Plus Five Five, Inc., 2261 Market Street #5039, San Francisco, CA 94114, USA, as our processor (Art. 28 GDPR). Resend sends the message from servers in the European Union (Ireland). Resend stores the data of the sending, that is sender, recipient, subject and content of the message, in the USA and deletes it after 30 days. Resend is certified under the EU-US Data Privacy Framework (Art. 45 GDPR); in addition, the European Commission's standard contractual clauses apply (Art. 46(2)(c) GDPR).

To prevent abuse, we accept at most five messages an hour from one IP address. This count lives only in memory and for at most an hour; the IP address is stored only in the server log, as with every request. We recognize automated submissions by a field people cannot see and by the time between loading the page and sending; they are neither stored nor sent. We use no captcha or third-party service for this.

## Former waitlist

Until October 2026 you could leave your email address on kaeso.app to be notified when Kaeso comes out. We keep these addresses on our server and use them only for that notification. The legal basis is the consent you gave when signing up (Art. 6(1)(a) GDPR). You can withdraw it at any time by emailing us; we then delete your address. We no longer accept new sign-ups.

## Recipients at a glance

We pass personal data only to these service providers, and only as described above. We sell no data and do not pass it on for advertising.

- Hetzner Online GmbH: Server and network connection, Germany; data processing agreement (Art. 28 GDPR)
- Cloudflare, Inc.: Reverse proxy and cache for kaeso.app, docs, ui, demo and kpmr, name resolution (DNS), USA and worldwide; data processing agreement (Art. 28 GDPR), EU-US Data Privacy Framework and standard contractual clauses
- Plus Five Five, Inc. (Resend): Sending the contact form's messages, sent from Ireland, stored in the USA; data processing agreement, EU-US Data Privacy Framework and standard contractual clauses
- Apple Distribution International Ltd.: Mailbox (iCloud Mail), Ireland, transfers to the USA under standard contractual clauses
- GitHub, Inc.: Confidential reports of security vulnerabilities, USA; EU-US Data Privacy Framework

Authorities receive data only where we are legally obliged to provide it.

## Retention at a glance

- Server logs: 14 days after the day of the request, at most 15 days
- Blocked IP addresses: Block at most one week, log at most five weeks
- Update statistics: Per-day details 400 days, an entry 400 days after the last request
- Demo sessions: Until the nightly reset at 3:30
- Contact form: Twelve months after it arrived; at Resend 30 days
- Contact form count: One hour, in memory only
- Emails: Twelve months after your request is settled, unless a retention obligation applies
- Waitlist: Until you withdraw your consent
- Settings in the browser: Until you change or delete them
- Kaeso plugin: Nothing with us; in your install an agent's tool calls for 90 days, the details of the agent with no time limit

## Encryption

All our services are served only over encrypted HTTPS connections (TLS), and browsers are told never to use an unencrypted connection (HSTS). So third parties cannot easily read the data transferred. For the services Cloudflare delivers, encryption ends at Cloudflare, and Cloudflare connects to our server encrypted again. The release manifests and KPMR's catalogues are also signed, so an install can check that they come from us unchanged.

## Your rights

Under Articles 15 et seq. GDPR, you have the right to:

- Art. 15 GDPR: Access to your stored data
- Art. 16 GDPR: Rectification of inaccurate data
- Art. 17 GDPR: Erasure of your data
- Art. 18 GDPR: Restriction of processing
- Art. 20 GDPR: Data portability
- Art. 7(3) GDPR: Withdrawal of consent with effect for the future

**Right to object under Art. 21 GDPR: where we process data on the basis of legitimate interests, you may object at any time on grounds relating to your particular situation.**

We store no IP addresses in the update statistics. We can therefore only match entries to an install if you tell us the public IP address of its server (Art. 11(2) GDPR); we then give you information about the entry or delete it.

An email to [mail@kaeso.app](mailto:mail@kaeso.app) is enough for any request.

## Right to lodge a complaint

You may lodge a complaint with a data protection supervisory authority, in particular in the member state of your habitual residence, your place of work or the place of the alleged infringement (Art. 77 GDPR). The authority responsible for us is:

Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Rheinland-Pfalz  
Hintere Bleiche 34  
55116 Mainz, Germany

[www.datenschutz.rlp.de](https://www.datenschutz.rlp.de)

## Obligation to provide data and automated decisions

You are under no legal or contractual obligation to provide us with personal data; without the technically necessary access data, however, our services cannot be delivered, and without your name, email address and message we cannot reply to you. There is no automated decision-making, including profiling, under Art. 22 GDPR.

## Changes and language versions

We update this policy when the services or the law change. The version published here applies. This policy is available in German, English and Chinese; the German version is binding.
