--- title: Klex Cloud EU Data Act switching addendum changeSummary: Statutory switching, retrieval and exit conditions for covered business services --- This addendum forms part of the [Klex Cloud Terms of Service](/legal/terms/2026-11-04) only for Customers established or located in the European Union and only where Chapter VI of the EU Data Act applies to the contracted service. The relevant Customer is the contracting Customer for the organization, not an individual User merely accessing Cloud from the EU. This addendum does not contractually grant its switching rights to Customers outside the EU. Any rights that apply under mandatory law remain unaffected. It prevails over conflicting general provisions for that switching subject. It does not extend the Data Act's scope to unrelated services or restrict other mandatory retrieval, portability or deletion rights. Changes to this addendum follow the Terms' amendment rules and applicable law. Assistance under this addendum is limited to applicable Data Act duties. Binding data-processing duties remain unaffected; no voluntary general export service is promised. ## 1. Scope and requests For a covered service, you may request a switch to another provider, transfer to your own on-premises infrastructure, or erasure as permitted by the Data Act. Send your request to [support@klex.bot](mailto:support@klex.bot), identifying the affected service and your chosen destination or erasure instruction. We may verify authority and coordinate a secure transfer but must not impose unnecessary obstacles. The export categories for a Bot are all Customer Content and other customer-provided or customer-generated data stored for that Bot, all persistent Bot state, and the associated metadata and digital assets. These categories include instructions, files, memory, skills, configuration, inputs and outputs. Except for the credentials identified below, the export covers the complete stored Bot so that it can be replicated and re-hosted. Personal data remains subject to applicable data-protection duties. The Bot export is a ZIP archive. Export formats and data structures may vary between Klex Bot versions. For current technical information about supported export methods, version-specific formats and known limitations, consult the Klex Bot Documentation. Klex Bot exports can be imported into compatible versions of the open-source Klex Bot software, subject to the limitations described there. For Klex Machines, the documentation describes the export methods actually supported. Model-access credentials and private identity keys used to register the Bot with Cloud are omitted for security. You must configure model access and establish any required new identity or connections at the destination. These omissions do not exclude any data return required by mandatory law; where such a duty applies, we must arrange a lawful, secure method of return. For a Klex Machine, export categories are all Customer Content and other customer-provided or customer-generated data stored on that Machine, with associated metadata and digital assets. Machine data requires a separate export and is not included in the Bot ZIP. We identify the applicable Machine export method and format, and known technical limitations, when coordinating the request. Provider-internal data categories excluded from the customer export are our operational and security records used to administer Cloud rather than form part of the Customer's Bot or Machine, and our proprietary platform software and internal infrastructure configuration. These exclusions apply only to the extent permitted by law and must not obstruct a legally required switch. They do not exclude Customer Content or customer-generated data merely because it is stored in our infrastructure. This addendum does not transfer a third-party licence or promise compatibility with every destination, model or external service beyond applicable legal duties. ## 2. Assistance and continuity We provide reasonable switching assistance to you and your authorized destination provider and support your exit strategy for the contracted service. During the applicable transition, including a duly justified extension, we continue the contracted functions and act with due care to maintain business continuity. We explain known continuity risks and maintain the legally required high level of security during transfer and retrieval. Both parties must cooperate in good faith. ## 3. Timelines and termination No additional minimum switching notice applies under these Terms. If an individually agreed contract contains an initiation notice period, it must not exceed two months. The transition begins after any applicable notice period and must be completed without undue delay within a maximum of 30 calendar days. If completion within that period is technically unfeasible, we notify you within 14 working days after the switching request, give the technical justification and state an alternative transition period that must not exceed seven months. You may extend the transition once for a period appropriate for your own purposes, as provided by the Data Act. After the transition, you have a retrieval period of at least 30 calendar days for covered exportable data and digital assets. We maintain the legally required access during that period. For a Bot-specific switch, successful completion of the switching export ends that Bot's Cloud hosting and removes the running Bot from Cloud. The export remains available for the required retrieval period under this addendum. A Machine-specific switch ends only the affected Machine service. A service-specific switch terminates the corresponding service obligations, not the organization's Cloud agreement or its other Bots, Machines or services. Switching all existing resources does not itself close the organization. If your request covers switching away from the organization's Cloud services as a whole, the organization's Cloud agreement terminates on successful completion of that switch. We notify you of the affected service termination or organization-agreement termination, as applicable. Mandatory termination rights remain unaffected. If you choose erasure without switching, the affected service obligations, or the organization's Cloud agreement if your request covers the organization as a whole, terminate at the end of any applicable initiation notice period. We notify you and carry out the lawful erasure instruction. We may verify it and coordinate required protection but must not force a transfer to another provider. ## 4. Deletion and charges After successful switching and the applicable retrieval period, we erase covered exportable data and digital assets unless a lawfully agreed later erasure date or legally required storage applies. Required retained copies are restricted to their legal purpose. Suspension, depleted balance or ordinary termination notice must not shorten mandatory switching or retrieval protection. These conditional statutory periods do not establish a general post-termination recovery entitlement outside their scope. These Terms introduce no switching charge or early-termination penalty. Any separately and lawfully agreed reduced switching charge before 12 January 2027 must be disclosed before the contract and must not exceed directly linked switching costs. From 12 January 2027 no switching charges, including covered data-egress charges, may be imposed. Ordinary disclosed service charges remain payable only to the extent lawfully due.