This Annex 1 (Anlage 1) describes which services Klate Technology UG (haftungsbeschränkt) (“Klate”, “we”) provides under the General Terms and Conditions (Allgemeine Geschäftsbedingungen, AGB). It forms part of the AGB. The prices are set out in Annex 2. The processing of personal data on your behalf is governed by Annex 4. This Annex describes the scope of functions owed; what is expressly not included is set out in Clause 12 of this Annex.
Terms defined in the AGB have the same meaning here. The object that you create in the application for a brand or a client is called a customer record (Kundeneintrag) in this Annex (Clause 2 of this Annex); “customer” without any addition also refers here to you as the contracting party. You are addressed throughout as “you” (German „Sie“).
1. Subject matter
1.1 What Klate is
Klate is a web application at app.klate.ai for designing and reviewing conversation designs. A conversation design describes how a conversation between a person and an AI assistant is intended to proceed: which sentences are said, which systems the assistant would query at which point, which cards or forms it would show, and how the conversation continues if something goes wrong. You write this design as a sequence of example turns, share it with contributors, collect comments and obtain an approval.
Klate is aimed at people who plan and coordinate such conversations before technical implementation, such as solution architects, product managers and consultants.
1.2 A design is never executed
A design is a specification. It is a document, not a program. Klate does not execute the conversation described, neither in whole nor in part. In detail:
- Widgets (cards with buttons, lists or input fields) are displayed but do not trigger any action. Clicking a button in the design has no effect.
- Forms are displayed but are not submitted anywhere. There is no recipient.
- A tool call contains example values written by you for arguments and result. It does not call any system.
- Klate does not establish any connection to a third-party system named in the design. The catalogue of known systems (for example CRM or ticketing systems) serves solely for naming purposes. It contains no connection, no sign-in and no data flow.
- No end consumer comes into contact with a design. Klate is not a channel to your end customers and does not operate an assistant that talks to them.
1.3 Provision
Klate is provided as software as a service in the browser. The application is operated jointly for all users (multi-tenant); your content is thereby assigned to your workspace and is not visible to other workspaces. The application, the database and the accounts are operated in Frankfurt am Main. The uploaded files are held in the object storage of a provider to which we have specified Western Europe as the storage location; that provider does not guarantee any particular storage location. Which guarantees apply to the storage location is described in Annex 4. There is no local or self-operated edition of the software.
1.4 Technical requirements
To use the service you need a device with a current browser and an internet connection. Chrome, Edge and Firefox from version 111 as well as Safari from version 16.4 are supported, in each case with JavaScript enabled and with acceptance of the strictly necessary cookies named in the Datenschutzerklärung (privacy notice) in the section „Cookies und Zugriff auf Ihr Endgerät“ (Cookies and access to your device); enlarging the chat view (zoom) is available in Firefox from version 126. The application is designed for work at a desk: it requires a browser window of at least 1,024 pixels in width. In a narrower window, for example on a smartphone, it displays only a notice and cannot be used. The user interface is available in German and in English; you choose the language in the application. No installation is required; we deploy updates on the server side without any action on your part. We do not support other environments.
2. Object model
Your content is arranged hierarchically in Klate. Every object belongs to exactly one workspace.
Workspace. The self-contained environment in which your content is held. Every account receives a personal workspace on first sign-in. With the Team plan (Tarif Team) a team workspace is created in addition, in which several people work as members. Plan, seats and quotas apply per workspace. Each person may be the owner of at most one team workspace.
Customer record (“Customer” in the interface, “Kunde” in the German version). A folder for a brand or a client for which you design. A customer record carries a name, a brand colour and a logo. For a customer record you can specify that only people with e-mail addresses from certain domains may be invited.
Project. A group of designs within a customer record, for example for an undertaking or a product. The project holds the Brief and the guidelines and determines the presentation of the conversation (chat title, subtitle, persona, colours, background).
Design. The actual work piece: a conversation design with one or more paths. A design has a title, a description, tags, a phase (draft, in review, approval requested, approved) and belongs to exactly one project.
Path. A named, ordered sequence of turns. Every design has exactly one main path, which cannot be deleted, and any number of branches. A branch begins at a turn of the parent path and can rejoin at a later turn. Paths carry a kind: regular case, edge case, error case or adversarial case.
Turn. A single conversation contribution, either from the user side or from the assistant side. A turn consists of blocks: text, image, video, audio, code, tool call, source, form, widget, follow-up question and file. For each turn you can record an intent and an “avoid” as a note for implementation, and mark a turn as a handover to a human.
Brief. A structured document per project against which every design is reviewed. It describes objective, scope (what the assistant does and what it does not do), target group, channels, handover to humans as well as the voice and character of the assistant. You can add your own fields. The Brief has its own phase, its own approval and its own version history.
Guideline. A behavioural rule of the project in the form “If, Then, Why”. Guidelines can be linked to turns in order to show that a turn complies with or breaches a rule. Klate does not check compliance with a guideline automatically.
Tool. The reusable description of a system call that the assistant would make at a point in the conversation: name, description, parameters, example arguments and example result, behaviour (reading, writing, deleting; confirmation; error case; time limit) as well as details of connection and responsibility. A tool can be assigned to a tool provider, the system to which it belongs. A tool is a description; it is not called.
Widget. A card that the assistant would show in the conversation, for example a selection, a list or a confirmation. A widget is described as structured data and rendered by Klate. It does not react to input.
Form. The reusable description of a structured input with fields of the types text, date, selection and checkbox. A form is displayed in a turn but is not submitted anywhere.
Subagent. A named assistant persona that speaks turns in the design, for example where a conversation switches between several specialised assistants. A subagent belongs to a customer record and optionally to a project.
Media. Images, videos and audio recordings uploaded by you. They belong to the workspace and are stored only once within the workspace, even if you upload the same file several times. Instead of uploading a file you can also enter a public internet address in a block; Klate then stores only the address, not the file.
3. Scope of functions
3.1 Designing
The editor displays a design as a chat history. You create paths, insert turns, edit blocks, link tools, forms, widgets, subagents and guidelines, and play back the sequence. A map view (Design Map) shows all paths of a design as a branching graph, into which you can zoom and from which you can jump to a turn. A search across all objects of the workspace is reachable from every page. Designs, tools, forms, widgets and subagents can be duplicated within the same workspace or copied into another customer record or another project.
3.2 Roles and collaboration
Access to customer records, projects and designs is controlled through three roles:
| Role | May |
|---|---|
| Viewer (Betrachter) | read content, comments and the history of the phases; write comments |
| Editor (Bearbeiter) | change content; invite further viewers and editors; withdraw their own invitations |
| Admin (Administrator) | fully manage access on the object, including granting the admin role |
A role on a customer record applies to all of its projects and designs; a role on a project to all of its designs; a role on a design only to that design. The admin role cannot be granted on an individual design. The role that a person has in the workspace acts as a lower limit for everything in the workspace. An invitation grants access only once the invited person has accepted it.
Several people can have the same design open at the same time. Klate shows who is currently present and locks a turn for a short time while it is being edited by another person. Simultaneous editing of the same turn by several people in real time is not part of the service. If two changes are irreconcilable, the rejected change is withdrawn in the editor and the current state is loaded.
Comments can be attached to a turn, to a design as a whole, to a part of the Brief, to a guideline and to a project. Comments are organised as a conversation with one reply level. Anyone mentioned in a comment with “@” receives a notification in the application, not an e-mail.
3.3 Approvals
Designs and Briefs pass through phases and can be submitted for approval, including to people without a Klate account. Details are set out in Clause 6 of this Annex. Approvals are available in the Pro and Team plans.
3.4 Version history
In the Pro and Team plans Klate maintains a version history for every design. A version comes about in three ways: you set a checkpoint yourself; Klate saves at every phase change; and Klate saves ongoing changes automatically at regular intervals. You can restore an earlier version or branch it off as a new design. Automatically created versions are removed after 30 days; checkpoints set by you and versions from phase changes are retained. In the Free plan no version history is maintained.
3.5 Automatic saving
The editor saves your entries continuously, as a rule within a few seconds of the last change. If a save operation fails, the editor tries again and displays the state. Automatic saving serves to secure the current state; it does not replace the version history.
3.6 First design at setup
On first sign-in a setup assistant conducts a short interview with four questions. From the answers an AI function generates a complete first design with customer record, project, Brief, paths, turns, tools, forms, widgets and guidelines. This happens once per account and is also available in the Free plan. Details are set out in Clause 4 of this Annex.
3.7 Media
You can upload images, videos and audio recordings into a workspace. The browser transfers the file directly into the private object storage; the file does not pass through any application server. Uploaded files are reachable only via short-lived, signed retrieval links which Klate generates only after an access check. There is no public access to the storage. Permitted file types and sizes are set out in Clause 7.4 of this Annex. Larger media can be embedded via a public internet address; the file is then loaded directly from there by the browser of the person viewing and is not stored by Klate.
3.8 Account, sign-in and team
Sign-in is by e-mail address and password. On registration the e-mail address must be confirmed with a one-time code. The password must be at least twelve characters long, contain upper- and lower-case letters, at least one digit and at least one special character, and must not be a common or easily guessed password; a forgotten password can be reset via a link sent by e-mail. Sign-in via third-party providers (social login), single sign-on and two-factor authentication are not part of the service.
In the Team plan, admins of the team workspace manage the members: they invite people by e-mail, assign roles and remove members. An invitation by e-mail is valid for 14 days. If a member is removed, the content created by them remains in the workspace; it belongs to the workspace, not to the person. The owner of the team workspace cannot be removed.
Klate sends e-mails in particular for confirmation of the address, resetting the password, invitations, approval requests as well as for billing and plan changes.
3.9 Deletion
Customer records, projects and designs are, on deletion, first marked as deleted and permanently removed from the database after 30 days. Within these 30 days we can restore a deleted object at your request to support@klate.ai; there is no restoration by you yourself in the application. All other objects (paths, turns, comments, tools, tool providers, forms, widgets, subagents, guidelines and memory entries) are deleted immediately and permanently.
You should be aware of two characteristics. First: in the Pro and Team plans the content of a deleted turn can live on in a version that still contains that turn, for as long as the version exists. Second: deleting a design, project or customer record does not delete the uploaded files used in it. They remain in the media library of the workspace and continue to be retrievable for the members of the workspace. There is no automatic deletion of files from the object storage. Deletion under data protection law after the end of the contract is governed by Annex 4.
4. AI functions
4.1 Which functions exist
Klate contains four functions that use a language model. None of them runs in the background; each is triggered by an action on your part.
Assistant (“Ask Klate”). An assistant that is reachable from every page of the application and that, on your instruction, creates, changes, searches and reviews designs, paths, turns, Briefs, guidelines, tools, forms, widgets and subagents. It works exclusively on your own content with your own rights and is limited to the designing of conversations; it refuses other concerns. The assistant is available to people with their own Pro plan or as a member of a team workspace; it is bound to the person, not to the workspace. If you work in a team workspace, the consumption is charged to the team's AI quota (KI-Kontingent); in any other workspace to the AI quota of your personal workspace. In the Free plan the assistant is not included.
Writing proposals of the assistant are, by default, presented to you for confirmation before they are executed. Reading steps run without a query. You can switch a conversation to automatic execution.
First design at setup. The one-time generation of a first design from your four interview answers. It is available in all plans and does not draw on any quota. If the generation does not succeed, you receive a prepared example design. The description of the generated design contains a note that it was created by AI.
Titling. A new conversation with the assistant automatically receives a title from your first message.
Memory. On request the assistant remembers preferences and details about you so that you do not have to repeat them. Memory is switched off by default. If it is switched on, the assistant proposes after a message that a detail be stored; without your confirmation nothing is stored. You can delete each entry individually or all entries. Switching memory off does not delete stored entries.
4.2 Models and providers
All requests to language models run via the AI gateway of Vercel Inc. (Vercel AI Gateway). The computation itself is carried out exclusively by the model providers OpenAI and Anthropic, in each case in the USA. Other operators are excluded by the setting of the gateway. We do not use any access credentials of our own to OpenAI or Anthropic; the route leads via the gateway in every case.
Every request carries the instruction that your inputs may not be used for the training of models. If no provider is available that gives this undertaking contractually, the request fails; it is not forwarded to another provider. There is no agreement that the model providers do not store your inputs at all (zero data retention). The providers may retain inputs and outputs for a short time for abuse monitoring.
As at the date of this Annex, the following are used in production operation:
| Purpose | Model | Provider |
|---|---|---|
| Assistant (default and currently the only selectable model) | GPT-5.6 | OpenAI |
| First design at setup | GPT-5.6 | OpenAI |
| Fallback model where the running model aborts without a result (one single retry) | Claude Sonnet 4.6 | Anthropic |
| Titling and checking for details worth remembering for the memory | Claude Haiku 4.5 | Anthropic |
Klate notifies you of the switch to the fallback model in the conversation; the switch is additionally logged internally.
Klate may exchange, add or remove models, as long as the computation remains with OpenAI or Anthropic. For the assistant, alongside GPT-5.6 the models Claude Sonnet 5 (Anthropic) and GPT-5.4 mini (OpenAI) are approved for production operation and may be offered for selection. We will announce an extension to further providers in accordance with Clause 7.7 of the AGB; your right of objection and termination is also set out there.
4.3 What is transmitted on a call
If you trigger an AI function, Klate transmits to the model provider: your input and the previous course of the conversation; the instructions to the model including your name, the page currently open and details of which workspace, customer record, project or design is open; the content that the assistant reads in order to carry out the work, in particular the Brief, guidelines, paths and turns of the design concerned as well as linked tools and widgets; content that you expressly include with “@”; the definitions and results of the tools that the assistant calls in the course of the work; attached images; and, if memory is switched on, your stored memory entries. For the titling, your first message is transmitted; for the memory check, your message, the answer and the existing entries. Content from workspaces that are not open for the request is not transmitted. Further details on the data processing are set out in the Datenschutzerklärung (privacy notice) and in Annex 4.
4.4 What the AI functions deliver
The AI functions generate proposals and drafts which you review: a draft for a turn, a path, a Brief, a guideline, a tool, a form or a widget; an answer to a question about your content; a title for a conversation; a proposal for a memory entry. What is owed is that, on your instruction, the function generates such a proposal from your input and the content included and presents it to you for acceptance, modification or rejection. The assistant carries out writing proposals only if you have confirmed them or have switched the conversation to automatic execution. A proposal is a basis for your decision, not a finished result.
Proposals come about in a language model that works statistically. That determines their nature: the same request can lead to different proposals. A proposal can be incomplete, unsuitable or wrong, an undertaking can break off abruptly, or it can contain values that do not exist. The assistant is instructed not to report any success that a tool has not confirmed; it can be mistaken about that too. A proposal therefore becomes part of your design only by your reviewing and adopting it. In the assistant and in the setup assistant, Klate displays a permanent notice that you are working with an AI and should review the results. Which obligations apply to you when using proposals, in particular the checking of statements of fact, is governed by Clause 7.4 of the AGB.
4.5 Technical limits of a call
A message to the assistant may contain at most 8,000 characters and up to four images (PNG, JPEG, GIF or WebP, about 5 MB each). A call of the assistant ends at the latest after 24 tool steps or 300 seconds. A conversation has an upper limit for the amount of history that the model can process; once it is reached, the conversation is concluded and you begin a new one. The proportion of the history consumed is displayed to you in the input field. In the event of a targeted attempt to circumvent the protective rules of the assistant, the assistant ends the conversation; it cannot then be continued.
5. Interfaces
5.1 The MCP server
Klate provides a server according to the Model Context Protocol (MCP) at app.klate.ai/api/mcp. Through it, an AI agent operated or used by you, for example a coding assistant, can work with your content in Klate. MCP access belongs to the scope of the service of the Pro and Team plans. On the Free plan it is not available. It is not a pre-release feature within the meaning of Clause 20 of the AGB; the general provisions apply to it.
5.2 Connection and access
An agent connects via OAuth 2.1 with PKCE. Registration of a client is open; the callback address must, however, be either https://claude.ai/api/mcp/auth_callback or a local loopback address with the path /callback. In practice, Claude products from Anthropic and locally running agents can currently connect in this way. On connecting, Klate displays a consent page on which you select the workspaces that the agent may access. If you make no selection, the connection applies to all of your workspaces on the Pro and Team plans. The consent page also names the permission level the agent requests and describes what it allows: "read" (klate.read) or "read and write" (klate.write, which includes reading). If the agent requests no level, "read and write" applies. Klate rejects a request for any level other than these two. The agent determines the level with its request; the consent page only offers to grant or refuse it. The level granted applies to the connection even when the agent renews its token; a different level must be requested by the agent when it connects again. An access token is valid for one hour, a refresh token for 30 days. You can view and revoke existing connections in your account under Connections; revocation is always possible, independently of MCP access.
5.3 What an agent can do
The server provides tools with which an agent can read, create and change customer records, projects, designs, paths, turns, Briefs, guidelines, tools, tool providers, forms, widgets and subagents; can generate a whole design in one step; can write and delete comments; can request and grant approvals; and can grant, change and withdraw the access of other people. It can permanently delete paths, turns, widgets, tools, tool providers, forms, subagents and guidelines. It cannot delete customer records, projects or designs and cannot upload files.
Two tools trigger the sending of an e-mail to an address specified by the agent: the invitation of a person and the approval request. An invitation as editor occupies a seat in the Team plan. No other tool sends e-mails, calls a third-party system or triggers a payment.
The agent acts with your rights and can never do more than you yourself are permitted to do. With the permission level "read and write", it can do everything in the released workspaces that you yourself are permitted to do there, including changes and permanent deletions. With the permission level "read", the server provides it only with the reading tools: it can read customer records, projects, designs with their paths and turns, Briefs, guidelines, tools, tool providers, forms, widgets, subagents and the media library, and see who has access. It can then create, change or delete nothing, write no comments, neither request nor grant approvals, neither grant, change nor withdraw access, and trigger no e-mail. Every changing action of an agent is recorded in an internal audit log with your account, the tool and the object concerned.
5.4 Responsibility
You are responsible for the actions of an agent that you connect to Klate as if you had acted yourself. This applies in particular to deletions, to e-mails to third parties and to access that the agent grants to other people. Details are governed by Clause 8 of the AGB.
5.5 Distinction from the assistant
The assistant in the application uses the same tools as the MCP server, but within the application, without a connection and without a token. It is part of the Pro and Team plans and does not require MCP access.
6. Approvals and share links
6.1 Phases
A design is in one of four phases: draft, in review, approval requested, approved (“Draft”, “In Review”, “Pending Approval” and “Approved” in the interface). Klate sets the phase “approval requested” itself when an approval has been requested. An approved design is locked against changes; every write attempt is rejected until the design is reset to an earlier phase. Every phase change is recorded with the point in time and the acting person. The Brief of a project passes through the same phases independently of the design.
6.2 Approval request by link
You can request the approval of a design or Brief from a person of your choice by specifying their e-mail address and optionally a message. Klate sends that person an e-mail with an approval link. The link contains a random key, is valid for 14 days and is consumed with the decision. The person can approve the design or refuse the approval. Whoever requests an approval cannot grant it themselves. If the receiving person has a Klate account, the link is bound to that account.
6.3 What the receiving person sees
The approval link is the only place at which content is visible without a Klate account. Whoever opens the link sees the complete design in read-only form: all paths and turns including the example arguments and example results of tool calls, the linked tools, tool providers, forms, widgets, subagents and guidelines as well as the Brief of the project. Uploaded files are not displayed to that person; media embedded via an internet address are displayed. Any person in possession of the link can open it within the 14 days and take the decision, provided the link is not bound to an account. Choose the recipient with care, therefore, and do not include in a design that you submit for approval any content that the recipient is not to see.
6.4 No electronic signature
An approval is a record in Klate with the point in time, the e-mail address of the approving person and the decision. It is not an electronic signature within the meaning of Regulation (EU) No 910/2014 (eIDAS Regulation) and does not in itself establish any legally binding declaration between you and the approving person.
6.5 Share links and invitations
Alongside the approval, in the Pro and Team plans you can invite people and generate share links. An invitation is addressed to a particular person or e-mail address and grants the role of viewer or editor. A share link is an unlisted link to a design, a project or a customer record. Whoever opens it must sign in to or register with Klate and then receives the viewer role on the linked object. A share link always grants read access only. It expires only if you set an expiry date when generating it; otherwise it applies until you withdraw it. Invitations and share links are subject to the limit for viewers per workspace and to the domain restriction of a customer record. In the Free plan there are neither invitations nor share links.
7. Limits and quotas
7.1 Plans
Klate is offered in the Free, Pro and Team plans (Tarife). The prices are set out in Annex 2. Pro and Team contain the same functions; they differ in the number of seats and in the way in which editors are added. An Enterprise plan is currently not offered.
A seat (Clause 5 of the Preisliste, price list) is the entitlement of a person to work as editor or admin. Viewers do not occupy a seat. In the Pro plan there is exactly one seat; a further one cannot be acquired. A second person can only work as editor in a Pro workspace if they themselves have a paid plan; otherwise they can only be a viewer. In the Team plan three seats are included; further seats up to a total of 50 can be purchased in addition and assigned to people without a plan of their own. If a seat is withdrawn, the person loses only the write rights; their access is retained in read-only form.
Whoever is the owner of an active team workspace receives, for the duration of the Team plan, the scope of functions of the Pro plan in their personal workspace as well (Clause 1.6 of the Preisliste).
7.2 Quotas per plan
| Free | Pro | Team | |
|---|---|---|---|
| Designs | 5 | unlimited | unlimited |
| Customer records | 1 | unlimited | unlimited |
| Projects | 1 | unlimited | unlimited |
| Seats (editors and admins) | 1 | 1 | 3 included, up to 50 in total |
| Viewers per workspace | none (no invitations, share links or approvals) | up to 50 | up to 50 |
| Storage for uploaded media | 250 MB | 5 GB | 5 GB |
| Size of a single uploaded file | 10 MB | 25 MB | 25 MB |
| Version history | not included | included | included |
| Invitations, share links, phase changes and approvals | not included | included | included |
| Widgets | not included | included | included |
| Assistant (“Ask Klate”) | not included | included | included |
| First design at setup | once per account | once per account | once per account |
| Monthly AI quota | none | 1 quota unit | 3 quota units, plus 1 quota unit per seat purchased in addition |
| AI Boost | not available | up to 50 AI Boost units | up to 50 AI Boost units |
| MCP access | not available | included | included |
In this Annex, MB denotes 1,024 × 1,024 bytes and GB denotes 1,024 MB.
Quotas limit the creation of new objects; they delete nothing. If a workspace falls below its quotas through a change to the Free plan, all content is retained and remains editable for seven days at first. After that, a project chosen by you remains editable; all other projects and designs are read-only, but can still be deleted and exported, until the workspace is again within the quotas or you order a paid plan again. If the change follows a failed payment, the seven days do not begin only with the change, but already with the first failed payment. The editable time after the change can then be shorter or absent entirely. Details are governed by Clause 11.4 of the AGB.
7.3 Content limits
The following limits protect operations against abuse and oversized states. They lie far above what typically arises when designing.
| Free | Pro | Team | |
|---|---|---|---|
| Size of a single turn | 256 KB | 512 KB | 512 KB |
| Blocks per turn | 100 | 200 | 200 |
Irrespective of the plan, the following apply: 20 tags per design with 40 characters each; 800 characters for the intent and for the “avoid” of a turn; 100 guidelines per project with 300 characters for “If”, 500 characters for “Then” and 300 characters for “Why”; 4,000 characters per comment; 65,536 characters for the definition of a widget or form. The fields of the Brief are individually limited to a fixed number of characters.
7.4 Media: permitted file types
Only files of the following ten types can be uploaded:
| Kind | Types |
|---|---|
| Images | PNG, JPEG, GIF, WebP |
| Video | MP4, WebM |
| Audio | MPEG (MP3), WAV, OGG, WebM |
In particular, SVG graphics, PDF files, Office documents and archives cannot be uploaded. SVG is excluded because the format can contain executable code. The size per file depends on the plan. The check relies on the file type stated by the browser and on the size actually transferred; Klate does not check the content of the file. A file of an impermissible type or with a stated size above the limit is rejected before the transfer. If the file actually transferred exceeds the limit, Klate rejects it after the transfer and deletes it again from the object storage; it is not taken into your media library. Media that you embed via an internet address are not subject to any of these limits and are not counted against the storage.
The storage consumption of a workspace is the sum of the sizes of all uploaded files. A file that is uploaded several times within a workspace counts only once.
7.5 AI quota
Every paid plan contains a monthly AI quota for the assistant, measured in quota units (Kontingenteinheiten) (Clause 4 of the Preisliste). The Pro plan contains one quota unit; the Team plan contains three quota units and one further unit per seat purchased in addition. With the AI Boost you can purchase up to 50 further quota units per billing period (Clause 4.4 of the Preisliste).
How much work one quota unit permits depends on the model used, on the length of the conversation, on the extent of the content read and on the number of tool steps. Klate measures the consumption of a request by the number of tokens processed and generated by the model, valued at the rate stored for the respective model; a more expensive model therefore consumes more of the quota per token. Klate displays the consumption as a proportion of the quota. The quota is newly provided at the beginning of every billing period; quota units not consumed lapse at the end of the period and are not carried over. If the quota is used up, the assistant accepts no new requests until the next billing period. Klate completes a request already begun, even if the quota is used up in the meantime; the excess consumption of that one request is not charged, but is set off against the quota of the following billing period. There is no subsequent billing by consumption, and individual quota packages cannot be purchased. For as long as a due payment is outstanding, Klate suspends the AI functions; all other functions remain usable (Clause 10.5 of the AGB). The contractual treatment of the quota is governed by Clause 10.3 of the AGB.
The first design at setup does not draw on the quota.
7.6 Request limits
Klate limits the number of requests per person and minute in order to protect operations for everyone. If exceeded, the request is rejected and can be repeated after a short wait; no content is lost in the process. The most important limits:
| Operation | Limit per person and minute |
|---|---|
| All requests of a signed-in person (per route) | 600 |
| Messages to the assistant | 12 |
| Operations that trigger an e-mail (invitations, approval requests) | 15 |
| Create a design | 30 |
| Create a customer record or project | 20 |
| Upload a file | 30 |
| Write a comment | 60 |
| First design at setup | 5 |
| Calls of the MCP server with a valid token | 600 |
| Calls of the MCP server without a valid token (per IP address) | 120 |
7.7 What happens when a limit is reached
When a quota or a content limit is reached, Klate rejects the operation concerned and states the reason. Existing content is not altered by this. Quotas can be extended by deleting objects or by a change of plan.
8. Availability and maintenance
We operate Klate with the care of a proper provider and endeavour to achieve operations that are as free from interruption as possible. We do not owe any particular availability expressed as a percentage, and we grant no credits for downtime. The handover point of the service is the transition from the network of our hosting provider into the public internet. The connection from there to your device lies outside the service.
The application and the database run in a single region (Frankfurt am Main). There is no automatic takeover by a second region. Where the uploaded files are held is described in Clause 1.3 of this Annex.
We may carry out maintenance work at any time. We announce planned maintenance work that is likely to interrupt the service in advance at status.klate.ai, to the extent that this is possible. We carry out maintenance work to avert a security risk or to remedy a fault without prior announcement. The application itself displays no maintenance notice; the status page is the channel.
At status.klate.ai we display the reachability of the application. External monitoring checks the application at short intervals from several regions; detected faults appear on the status page automatically. The status page serves the purpose of transparency. It is not an assurance of availability and its information is not a basis of measurement for claims.
The AI functions depend on the model providers and the AI gateway, whose availability we do not influence. If a model is temporarily unreachable, all other functions remain usable. The legal consequences of a fault are governed by Clauses 13 and 15 of the AGB.
9. Support
We provide support by e-mail to support@klate.ai on working days (Monday to Friday with the exception of the statutory public holidays in Frankfurt am Main). We do not owe any particular response time or resolution time. Support covers questions on operation and on the scope of functions as well as the reporting of faults. It does not cover advice on the content of your designs.
In the application you can report a fault or a wish via the Feedback function. Technical details about your session (browser, operating system, window size, version of the application and language setting) are transmitted only if you consent to this in the form. You receive a confirmation of receipt and a message once the report has been processed.
There is no support by telephone, no ticket system, no fixed support hours and no preferential handling in any particular plan.
10. Data backup and restoration
The database in which your content and your account are held is operated by our database provider in Frankfurt am Main. The provider retains the change history of the database for seven days. Within this window we can reset the data stock to an earlier point in time in order to restore operations after an outage or an error on our side. Such a restoration affects the entire data stock, not an individual workspace, and is an emergency tool for outages. It is not a means by which you can undo a deletion or change of your own.
There is no backup outside the database provider (offsite backup) and no copy in a second region. For the uploaded files in the object storage there is no backup and no change history. We do not owe any particular restoration time.
Within the application, the restoration of deleted customer records, projects and designs within 30 days on request, as well as, in the Pro and Team plans, the version history, are available to you as protection against your own errors.
Back up content whose loss you cannot accept yourself outside Klate; the export under Clause 11 of this Annex is available to you for this purpose at any time (Clauses 5 and 16.4 of the AGB).
11. Data export
You can export the content of your workspace yourself from the application at any time, without a request to us and without additional charge. The export contains the content of the workspace (customer records, projects, designs with all paths and turns, Briefs, guidelines, tools, tool providers, forms, widgets, subagents, comments, the version history and the history of your conversations with the assistant) in a structured, machine-readable format (JSON) as well as the media files uploaded by you in their original file format. Not included are our internal audit and security logs and, for as long as the block lasts, a file we have blocked under Clause 21 of the AGB. Media that are embedded via an internet address are output as an address; the file itself is not held with us.
The export is an output of your content. Klate does not owe any importation into another product and no import into Klate.
Independently of the export in the application, you can, via the MCP server, to the extent that it is available on your plan, read out your content in structured form with an agent of your own. A structured export on request under Annex 4 remains unaffected.
After the end of the contract and after the discontinuation of a service, the export remains available to you for the periods stated in Clauses 14.2 and 23 of the AGB. You can delete your account yourself in the application; the consequences are governed by Clause 23 of the AGB.
12. Services not included
The following services are not part of the contract. The list clarifies what cannot be derived from the scope of functions:
- The execution of a design. Klate does not operate a conversation, does not execute a turn and does not react to input in a design.
- A runtime environment for assistants, chatbots or voice assistants.
- A connection to third-party systems named in tools, tool providers or designs. There is no interface, no sign-in with a third-party system and no data exchange with such a system.
- The hosting or operation of an assistant that you build on the basis of a design.
- A channel to your end customers or end consumers. No person outside your workspace, your invitations and your approval requests comes into contact with a design.
- The import of content from other products or files into Klate.
- An automatic check of designs for compliance with the Brief or the guidelines. The assignment of guidelines to turns is a labelling by you.
- A proposal of the AI functions that would be usable without your review. What the AI functions deliver is described in Clause 4.4 of this Annex.
- Support by telephone, a ticket system, fixed support hours, response times or preferential handling.
- An agreement on a particular availability (SLA), credits in the event of an outage or a particular restoration time.
- An installation on your own servers (on-premise) or in a cloud chosen by you, provision at a location chosen by you, as well as a dedicated instance.
- A backup of your data outside the change history described in Clause 10 of this Annex.
- Single sign-on, two-factor authentication and sign-in via third-party providers.
- Simultaneous editing of the same turn by several people in real time.
- An electronic signature or evidence with probative value within the meaning of Regulation (EU) No 910/2014 (eIDAS Regulation).
- Certifications or audit reports of third parties, for example under SOC 2 or ISO 27001.
- Advice on the content of your designs as well as training.
As at: 8 October 2026 · Version 1.5