General Terms and Conditions for Learn Battle Studio
Last updated: 10 September 2026
These Terms govern the use of Learn Battle Studio by teachers and educational institutions, the purchase of institutional licenses, and access for the institution admin. The data processing agreement in Part B forms part of these Terms; it also contains the agreement on data processing on behalf of the controller for the expressly described content-processing activities.
The Provider is Lioverse UG (haftungsbeschränkt), Karl-Arnold-Straße 31, 52525 Heinsberg, Germany, represented by Annika Latz and Dennis Koob. Contact: info@lioverse.de, phone: 015789660196. Studio can be accessed at app.learn-battle.de.
The Customer is the natural person or educational institution named in the order process or the accepted license offer. A teacher who orders their own subscription is themselves a party to the contract. In the case of an institutional license purchase, the institution is the contracting party for the licenses; teachers are authorized users. Activation of a funded license does not create any payment obligation for the teacher.
Anyone who enters into contracts or accepts the data protection agreement on behalf of an institution must be authorized to represent it. The mere role of teacher or institution admin does not by itself confer authority to represent the institution. A teacher who accepts only the usage rules for their own access does not thereby automatically bind their institution.
Consumer rights apply where a natural person acts for purposes that are predominantly outside their trade, business or profession. Employment as a teacher alone does not exclude consumer status. Individual agreements take precedence; in the event of conflicts on data protection matters, Part B prevails within its scope of application.
In the case of online registration or an order, the Customer submits an offer to contract by completing the process while agreeing to the Terms, which are made available for storage beforehand. The contract is concluded upon our confirmation or upon activation expressly designated as acceptance in the order process. For paid orders, the payment obligation is expressly disclosed. Entries can be corrected before submission. The language of the contract is German.
Institutional licenses are acquired on the basis of our individual offer. The number and type of licenses, scope of services, term, prices, payment method and any renewal follow from the accepted offer. Self-registration is not possible for the institution dashboard. After the licenses are purchased, we set up access for an institution admin named by the institution.
These Terms, including Part B, are provided before the contract is concluded and are included in the contract confirmation or attached to it as an annex available for storage. The Customer's name and address, their contact person, and the agreed version are documented in the order or license offer. Where a contract already exists, including the new Terms requires an effective agreement; amending a privacy page alone is not sufficient.
Within the agreed scope, Studio enables the creation and management of modules, courses, learning packages and learning questions, the provision of documents, and use of the "AI Assistant" and "AI Course Creation" features. For institutionally funded accounts, the respective agreed administration and dashboard functions are available. Booking-related quotas and technical limits are set out in the service description.
Teachers and admins use personal accounts. They protect their login credentials, keep required information up to date, and report suspected misuse. The institution names the authorized institution admin and promptly reports any change to, or loss of, that person's authorization. Lioverse withdraws or changes access after verifying authorization. Transfer of licenses to other teachers is permitted only within the scope of the booked offer.
The technical equipment and suitable internet access are the Customer's responsibility. We provide required compatibility information before the contract is concluded. We owe the legally required updates, including security updates. A specific minimum availability or particular response time is owed only if expressly agreed.
For a Studio subscription paid for by a teacher themselves, the prices and billing periods stated in the order process apply. Consumer prices include applicable VAT. Payment processing for these subscriptions is handled via Stripe. Payment information is collected within the payment process provided for this purpose.
For institutional licenses, the accepted offer and the payment terms set out therein apply. Stripe is not used for this. Use of an institutional license does not create a separate paid subscription for the teacher. Switching to a self-paid subscription requires a separate, express order.
Default in payment and its consequences are governed by law. A suspension due to non-payment generally requires an unsuccessful reminder with a reasonable deadline and prior notice. It must be proportionate and must not disregard legitimate objections to the claim. Customers' mandatory rights remain unaffected.
The term and billing period follow from the order or the license offer. A self-paid subscription can be terminated at any time, effective at the end of the current agreed billing period. After an agreed initial term, a consumer subscription renews only for an indefinite period and can then be terminated at any time with a notice period of at most one month. More favorable agreed terms remain unaffected.
For institutions, the terms, renewals and notice periods expressly agreed in the offer apply. If no renewal is agreed, the fixed-term license ends upon expiry of the term. A renewal status shown in the dashboard reflects the contractual agreement and does not replace it.
Notices of termination to us may be given in text form, for example by email to info@lioverse.de. Where legally required, we provide a directly and easily accessible termination button pursuant to Section 312k of the German Civil Code (BGB) and confirm electronic terminations in accordance with legal requirements. The right to extraordinary termination for good cause remains unaffected.
The end of an institutional license does not create any payment obligation for the teacher using it. The functions funded through it and institution-admin access end together with the authorization. Other validly existing accounts remain usable under their respective contracts. The mere deletion of a personal teacher account does not end an institution's license contract.
Within the scope of their authorization, teachers can attach documents to courses or modules. Files are stored on our server infrastructure at netcup. In the available settings, the teacher determines whether a document is visible only to themselves or also to authorized app users of the relevant course or module. They review the release before activating it.
The Customer, or the respective rights holder, retains their rights to uploaded and created content. They grant Lioverse a simple, royalty-free right of use limited spatially to what is necessary for service operation and temporally to the agreed purpose of use. It covers storage, necessary technical processing and reproduction, as well as provision in line with the granted releases. Technically integrated service providers receive only the powers necessary for this purpose.
This does not include use of the content for general advertising or for training AI models. The Customer may grant only such rights as they themselves hold. In particular, publishing third-party teaching materials, non-public examination materials and personal data requires corresponding authorization. Funding by an institution alone does not give it copyright in a teacher's works.
For personal document content concerning third parties, Part B, Section 2 applies. Special categories of personal data under Art. 9 GDPR, criminal-law data under Art. 10 GDPR, individual grade lists and unnecessary identification data may not be uploaded to Studio or used in AI inputs. Extending this scope requires a separate, effective agreement including suitable protective measures.
Releases may only be granted within the scope of existing rights. If a teacher's access ends, an institution's materials may only continue to be made available if a continuing engagement exists together with the necessary usage rights and data protection requirements. An orphaned technical document association alone does not justify further storage. For Client Data, the deletion and return rules in Part B take precedence.
Mistral AI is used exclusively via its API within the two Studio features "AI Assistant" and "AI Course Creation" for creating learning questions. In terms of content, only the texts and documents provided by the teacher within the respective feature are processed, including the sections extracted for that specific task. This is supplemented by necessary technical work instructions and API metadata. Where embeddings are required to process document input, this is likewise limited to that input.
Merely attaching or releasing course documents does not trigger any transmission to Mistral. App responses, individual learning progress, institutional analytics and other account content are not automatically transmitted to Mistral. Documents outside the expressly started AI task may also not be sent to Mistral through background or migration processes.
Use of the inputs and outputs transmitted via our API access for training Mistral models is disabled. No separate feedback channels that would release this content for training are used. This does not automatically mean that any temporary storage at the provider is excluded. Further data processing, recipients and retention rules are explained in the privacy policy and, for Client Data, additionally in Part B.
Remove personal or confidential information from AI inputs that is not required for creating questions. Submitting an input does not substitute for a legal basis regarding third-party data. AI results may be factually inaccurate, incomplete or unsuitable. The teacher reviews learning questions before release for accuracy, didactic suitability and third-party rights. No exclusivity or copyright protectability of the results is promised. Statutory rights in the event of defects in our service remain unaffected.
By using these integrated features, the teacher does not enter into a separate contract with Mistral. Lioverse remains the contracting party for the agreed Studio service. A direct, additional Mistral account is not required for this.
The institution acquires usage authorizations for Studio. Lioverse operates its own platform and is responsible for the account, learning and usage processing described in the privacy policy, as well as for providing the standard dashboard. The license purchase alone does not create an engagement for instructed processing of all platform data. The actual role for separate content-processing activities is governed by Part B.
The named institution admin sees only the assigned institution area. Visible information includes license counts and status, term and renewal status, as well as activation, content, usage and support metrics. The dashboard shows, for each assigned teacher, name, email address, role, account status, number of modules, learning packages and questions, last activity, and a support status. For each module, the responsible teacher is shown by name.
Student values are shown only in aggregated form: registered and active students, questions answered, game-mode usage and average learning time, each also broken down by module; further, knowledge level, repetition, battle engagement, trends, question texts with error rates, frequently used learning packages, and activity patterns by proximity to exams, day of week and semester. A named list of students or an individual student view is not part of the institution-admin role.
The evaluations serve to administer funded licenses, support the learning offering, and identify support needs. Automatically derived activity and support notices are not a professional assessment of teaching quality. The institution may not use this information for automated decisions about employees or learners, nor for personnel, performance or conduct monitoring beyond that. Any such use would require separate, permissible and transparently regulated processing.
Document content, AI inputs and complete prompts are not disclosed as dashboard usage metrics. Question texts and learning package names within learning metrics are to be distinguished from this; they must not contain unnecessary personal information. Further obligations regarding data exchange are set out in Part B, Section 1.
Prohibited are unlawful content, infringement of third-party rights, malware, unauthorized access, circumvention of license or access restrictions, and actions that materially impair the service. Rights infringements can be reported, with a precise description of the content and reasoning, via available reporting functions or to info@lioverse.de. We review sufficiently specific reports carefully and impartially.
In the event of violations, we may issue warnings, set remediation deadlines, restrict affected content or features, and impose a temporary suspension. We select the appropriate measure taking into account severity, repetition, affected rights and interests, and explain the essential reasons for it to the extent legally permissible. Before serious measures, we generally provide an opportunity to comment and remedy the situation. Urgent security measures and statutory obligations remain reserved.
A permanent suspension or extraordinary termination requires good cause. A review by a responsible person can be requested at info@lioverse.de. Statutory complaint and legal remedies remain available. A blanket, no-fault indemnification against third-party claims is not agreed.
We provide the agreed service with reasonable care. Necessary maintenance and security measures may temporarily limit availability; we announce significant, plannable restrictions in good time where possible. Statutory warranty rights remain unaffected. A beta designation does not constitute a blanket exclusion of warranty.
For consumers, where the requirements are met, Sections 327 et seq. of the German Civil Code (BGB) on digital products apply in particular. Further changes to an ongoing digital service require a valid reason, such as a changed technical environment or new security requirements, must not cause additional costs, and are clearly explained. Material agreed services may not be withdrawn arbitrarily.
In the event of more than a minor impairment of access or usability, we inform consumers in advance and in good time, on a durable medium, of the change and of the free right of termination within 30 days pursuant to Section 327r BGB. Its exceptions, in particular where an unchanged, contractually compliant version remains available without additional cost, remain unaffected.
We are liable without limitation for intent and gross negligence, for culpable injury to life, body or health, and to the extent of any guarantee assumed. Mandatory liability, in particular under the Product Liability Act and Art. 82 GDPR, remains unaffected.
In the event of slightly negligent breach of material contractual obligations, liability is limited to the foreseeable damage typical for the type of contract at the time of conclusion. Material contractual obligations are those whose fulfillment makes proper performance of the contract possible in the first place and on whose observance you may regularly rely. Otherwise, liability for slightly negligent damage is excluded. These provisions also apply to our statutory representatives and vicarious agents. Statutory warranty rights remain unaffected.
Amendments to these Terms and to agreed prices require an effective agreement or a statutory authorization. Silence or continued use does not constitute consent. Changes to sub-processors are subject to the separately agreed procedure set out in Part B.
German law applies. For consumers, mandatory protective provisions of their habitual place of residence and statutory venues remain unaffected. An exclusive venue at our registered office is agreed only for merchants, legal entities under public law, and special funds under public law. Mandatory jurisdictions take precedence.
We are not willing and not obliged to participate in proceedings before a consumer arbitration board; mandatory statutory procedures remain unaffected. Invalid provisions are replaced by the statutory provisions; otherwise, the statutory consequences of invalidity apply.
For its own platform operation, account administration, its own learning and game features, and the generation and disclosure of the standard evaluations described, Lioverse decides on the purposes and essential means of processing. The institution is responsible for retrieving and subsequently using the personal dashboard data it receives. Before retrieval, the institution ensures the legal basis required for this and that affected teachers are informed. Lioverse is responsible for the lawfulness and transparency of its own processing, including disclosure.
The data may only be used for license administration, administering the funded learning offering, and providing targeted support to assigned teachers. The admin may only retrieve it within the scope of this authorization. The institution limits any internal sharing to authorized persons with a specific need, obligates them to confidentiality, and terminates access when their task ends. Publication, sale or combination for cross-institution identification is not permitted.
Lioverse technically restricts access by institution and role. The institution must neither circumvent protective measures nor identify individuals from aggregated student values, nor create individual profiles using additional knowledge. Lioverse limits or suppresses evaluations where, given group size, filtering options or other available information, there is an unacceptable risk of inference. The mere absence of name display is not proof of anonymization.
Individual learning analytics for teachers are separate from the institution dashboard and require the separate, active opt-in described in the privacy policy. Neither the institution nor the teacher may replace this by merely accepting a license or these Terms. Any consent given must be voluntary and revocable.
The institution observes, in particular, the rules applicable to it on employee data protection and staff representation. Public institutions review the legal bases applicable to their tasks; Art. 6(1)(f) GDPR is not generally available to public authorities in performing their tasks. These contractual provisions do not, by themselves, constitute a data protection permission.
Both parties review data subject requests within their respective area of responsibility, forward misdirected requests to the responsible party without undue delay, and support each other in correcting or deleting transmitted data. Data subjects may contact Lioverse at datenschutz@learn-battle.de and the institution directly. Each party fulfills its own reporting and notification obligations in the event of data breaches and promptly informs the other of incidents affecting that party's data or obligations.
The institution deletes or anonymizes received personal evaluations as soon as the specified purpose no longer applies, unless a lawful retention obligation precludes this. Institution-admin access ends together with the corresponding authorization. Permanent institutional copies of personal activity data are not permitted merely by the purchase of licenses.
This role description applies only insofar as it corresponds to the actual processing. Any additionally commissioned, instructed administration or analysis process must be specifically captured contractually before it begins. Where purposes and essential means are actually determined jointly, the requirements of Art. 26 GDPR must be separately fulfilled. Designation as a license purchase does not exclude either.
The following provisions constitute the agreement pursuant to Art. 28(3) GDPR for the content specifically described in Section 2.2. They form a binding part of the Studio or license contract and do not require a separately signed DPA document. Effective inclusion vis-à-vis the person or institution actually responsible, and documentation of electronic acceptance, remain required.
The controller and client for the Client Data is the Customer named in the order, to the extent they determine the purposes of the relevant content processing. Where a teacher acts under the responsibility of their institution, the institution is the client; the teacher is merely an authorized user acting within their powers. Lioverse is the processor for this Client Data. The names, addresses and contact details of the parties follow from the contract confirmation or the accepted license offer; Lioverse can be reached at datenschutz@learn-battle.de.
This agreement covers personal data of third parties that the client lawfully provides for its own teaching purposes in course documents or AI inputs, as well as personal processing results derived from it. It does not cover Lioverse's own account, billing, security and standard-dashboard processing under Section 1, which is distinguishable from this. Data relating to the same person may fall under different responsibilities depending on the processing.
Before the first upload of such Client Data, the party actually responsible must be established and Part B must be effectively agreed. An account holder acting for themselves cannot conclude a data protection agreement on behalf of another institution without authority to represent it. Where content is effectively anonymized and contains no personal data, its processing does not require a data processing agreement.
The subject matter is the technical processing, in Studio, of learning materials selected by the client for its teaching purposes. It comprises receipt, storage, association with courses or modules, provision to persons released by the client, correction and deletion. Only where the "AI Assistant" or "AI Course Creation" feature is expressly selected does this additionally include text extraction (including OCR where applicable), segmentation, embedding creation where applicable, transmission of the selected input to Mistral, and the creation and storage of learning questions.
Data subjects include, in particular, teachers, authors, other persons named in permissible teaching materials, and, insofar as necessary and permissible for the teaching purpose, learners including minors. Categories of data include names, professional contact details, authorship and source information, other ordinary personal text information necessary for the learning material, as well as file metadata and texts, vectors and learning questions derived from it. Personal learning and performance profiles from the app are not fed into this process as Client Data.
Processing of special categories of data under Art. 9 GDPR, criminal-law data under Art. 10 GDPR, and individual grade lists is not the subject of this engagement. Scope and frequency depend on uploads and AI tasks initiated by the client; storage takes place for the duration of the agreed purpose of use and until return or deletion under Section 2.8. Lioverse does not use Client Data for its own advertising, model training, cross-institution analytics or other purposes of its own.
The client is responsible for the lawfulness of collection, the purpose of processing, the permissible content and recipients, and informing data subjects. The operating actions of authorized users — in particular upload, choice of visibility, starting an AI creation task, and deletion — specify the documented instruction within the agreed scope. Further instructions are given in text form to datenschutz@learn-battle.de. The respectively authorized contact persons can be identified from the contract and authorization data.
Lioverse processes Client Data exclusively on documented instructions, including with regard to transfers to third countries, unless required to do otherwise by Union or Member State law. Lioverse informs the client of any such requirement before processing, insofar as this is legally permitted. Where Lioverse considers an instruction to violate data protection law, the client is informed without delay and the affected processing is suspended until the matter is clarified. Any expansion of the engagement is agreed before it is implemented.
Lioverse deploys only persons who are bound to confidentiality or subject to a corresponding statutory obligation. Access authorizations are granted according to tasks and necessity and withdrawn when no longer needed. Lioverse implements the protective measures required under Art. 32 GDPR and maintains at least the measures agreed in Section 2.10. Technical improvements are permitted as long as the level of protection is not reduced.
Lioverse documents the security of the processing and reviews the effectiveness of its measures regularly and on an ad hoc basis following material changes or incidents. Changes materially affecting the security of Client Data are communicated to the client. Confidentiality interests limit disclosure to the extent necessary, but must not defeat the evidence legally owed.
The client approves the sub-processors named in Section 2.11 for the services specifically named there. Lioverse contractually imposes on them data protection obligations at least equivalent to Art. 28 GDPR and remains responsible to the client for their compliance. Further levels of the processing chain are subject to the same requirements.
Before adding or replacing a sub-processor, Lioverse informs the client in text form of the identity, location, activity, place of processing and, where applicable, transfer safeguards. This information is generally provided at least 30 days before the intended deployment. The client may object within this period on verifiable data protection grounds. Lioverse examines remedies or a reasonable alternative. Pending clarification, the affected Client Data is not transmitted to the objected-to new provider. If no permissible solution is possible, the affected part of the service may be terminated without further obligation; prepaid fees for services not rendered are refunded on a pro-rata basis.
Client Data is generally processed within the European Economic Area. Any transfer to, or access from, a third country requires a documented instruction, the necessary information to the client, and compliance with Art. 44 et seq. GDPR. Lioverse evidences the relevant recipients, countries, adequacy decisions or suitable safeguards, including any necessary supplementary measures. An EU establishment of a provider alone is not sufficient for this.
Insofar as Mistral carries out individual processing activities under its own responsibility — in particular an abuse-prevention check provided for the API access actually used — this role is to be distinguished from the sub-processing arrangement. Before any such disclosure of Client Data, Lioverse provides the client with the specific scope, purpose, recipient and storage conditions and obtains the documented instruction for this. Without this basis, personal Client Data is not fed into the affected AI processing path. No general training authorization is granted.
Taking into account the nature of the processing and the information available, Lioverse supports the client in fulfilling data subject rights, in the security of processing, in data protection impact assessments, and, where applicable, prior consultations under Art. 32 to 36 GDPR. For this purpose, Lioverse provides the necessary information and in particular enables the identification, disclosure, correction, restriction, provision and deletion of affected Client Data. Data subject requests addressed to Lioverse are forwarded without delay; a substantive response is generally provided only on instruction, unless the law requires otherwise.
Lioverse reports breaches of the protection of Client Data without delay after becoming aware of them to the client's designated contact person. The report includes, where available, the nature and extent of the incident, the categories and approximate number of data subjects and records affected, likely consequences, measures taken or proposed to address it, and a contact person. Missing information is provided without undue delay afterward. Lioverse does not wait for a complete investigation before making an initial report.
The client decides on its statutory notifications to supervisory authorities and notifications to data subjects. Lioverse supports compliance with statutory deadlines and promptly takes necessary measures to contain the incident and preserve evidence. Lioverse's own directly applicable statutory obligations remain unaffected.
Lioverse provides the client with all information necessary to demonstrate compliance with the obligations under Art. 28 GDPR and enables and supports audits, including inspections, by the client or an independent auditor engaged by it. For this purpose, suitable documentation and evidence may initially be used, provided they allow a sufficient review. The right to a necessary inspection remains unaffected.
Audits are generally carried out with reasonable advance notice and with protection of third-party data and trade secrets. In the case of specific incidents, reasonable suspicion, or regulatory requirements, they are enabled at short notice. Blanket annual limits, consent requirements or disproportionate costs must not restrict statutory audit and support rights.
After the engagement ends, at the client's choice, Lioverse returns the Client Data in a common electronic format or deletes it, and deletes existing copies, unless a statutory retention obligation precludes this. Lioverse requests this choice in good time before the intended end. If no instruction is given, Lioverse requests a decision and holds the data only to a limited extent for wind-down purposes; it is not used for new purposes.
Return or deletion in the production system takes place without delay following the corresponding instruction, and no later than within 30 days. Deletion covers raw documents, extracted texts, chunks, embeddings and associated personal work products. For pure technical backup copies, final removal takes place no later than within 90 days; until then, they remain blocked for ongoing operations and are used exclusively for necessary restoration. In the event of a restoration, deletion instructions already given are re-implemented before the data is used again for regular purposes.
Lioverse arranges for corresponding return or deletion with its sub-processors and confirms this upon request. Deviating statutory retention obligations are communicated; affected data is blocked and not further used for other purposes. Any independent retention by a recipient under its own responsibility is subject to that recipient's statutory obligations and the previously disclosed terms; it is not represented as deletion under the sub-processing arrangement.
The end of a personal teacher account does not automatically end a continuing engagement of the institution. However, continued storage requires the continuing instruction of the institution actually responsible and the necessary rights. This provision does not permit blanket, unlimited retention after account deletion.
This agreement applies from the point of effective contractual inclusion for the described processing on behalf, until its complete wind-down. Confidentiality and any protective obligations that remain necessary continue beyond that. Each party fulfills its own directly applicable statutory obligations. The rights of data subjects and statutory liability, in particular under Art. 82 GDPR, are not limited by this agreement.
Access and authorizations. Personal accounts, secure password hashes, role-based authorizations, and checks on course, module and institution assignment limit access. Administrative access to the infrastructure is restricted to authorized personnel. Authorizations are reviewed and withdrawn upon role changes and departures.
Transmission and storage. Connections to the app, Studio and API services are protected via TLS. Documents are held on the netcup server infrastructure operated by Lioverse; file access takes into account the stored visibility and user authorizations. Files, extracted sections and embeddings must not be retrievable via unprotected public storage access.
Separation and purpose limitation. Access is limited to the respective released institution, course or user area. Content data is not transferred into third-party dashboards or personal comparison profiles. Only inputs expressly provided within the two AI features are sent to Mistral. The training opt-out remains active; feedback channels granting training authorization are not used for Client Data.
Logging and error handling. Security-relevant administrative actions are documented in a traceable manner. Technical metrics are limited to necessary metadata. Raw documents, complete prompts, and personal provider error texts must not be included in generally accessible logs or metric labels. Necessary diagnostic access is limited and time-restricted.
Availability and recovery. Lioverse maintains a documented backup and recovery procedure, restricts access to backups, and regularly reviews recoverability. Security updates and vulnerability handling are carried out in a risk-appropriate manner. Recoveries must not permanently reintroduce deleted data into active processing.
Deletion and control. A confirmed file-deletion process is coordinated with the removal of associated database, text and embedding data. Failed deletions are detected and reprocessed. Compliance with authorizations, separation, AI purpose limitation and deletion procedures is reviewed regularly and after material changes. Staff are required to maintain confidentiality and handle the data securely.
netcup GmbH, Emmy-Noether-Straße 10, 76131 Karlsruhe, Germany. Service: hosting and infrastructure for storing and processing course documents and related data on servers operated by Lioverse. Place of processing of the commissioned servers: Germany. Affected: the Client Data stored as described in Section 2.2.
Mistral AI, 15 rue des Halles, 75001 Paris, France. Service: API processing exclusively of the inputs selected within "AI Assistant" and "AI Course Creation", including necessary text, OCR and embedding processing for the respective task. The default hosting region is the EU. Use for personal Client Data requires the information, instructions and safeguards named in Section 2.5. Training on these inputs and outputs remains disabled.
The specific further processing chain, including sub-providers and processing locations actually deployed, is provided to the client before first use for its Client Data as a storable sub-processor overview; changes are made in accordance with Section 2.5. Provider information regarding Mistral is available at https://legal.mistral.ai/terms/data-processing-addendum/ and https://trust.mistral.ai/subprocessors. A merely dynamic reference does not replace concrete information about the parties actually deployed.
Stripe is not a sub-processor for course documents and AI inputs. Payment processing for self-paid Studio subscriptions takes place outside this content-processing engagement.
This Part applies to consumers where a statutory right of withdrawal exists vis-à-vis Lioverse. Institutions and independently acting business customers do not thereby receive any additional contractual right of withdrawal. The notice concerns the ongoing Studio service.
You have the right to withdraw from this contract within fourteen days without giving any reason. The withdrawal period is fourteen days from the day the contract was concluded.
To exercise your right of withdrawal, you must inform us, Lioverse UG (haftungsbeschränkt), Karl-Arnold-Straße 31, 52525 Heinsberg, Germany, email: info@lioverse.de, phone: 015789660196, by means of a clear statement (e.g. a letter sent by post or an email) of your decision to withdraw from this contract. You may use the model withdrawal form below, although this is not mandatory.
To meet the withdrawal deadline, it is sufficient for you to send your communication concerning your exercise of the right of withdrawal before the withdrawal period has expired.
If you withdraw from this contract, we will reimburse all payments we have received from you, including delivery costs (with the exception of additional costs resulting from your choice of a delivery method other than the cheapest standard delivery offered by us), without undue delay and, in any event, no later than fourteen days from the day on which we received notice of your withdrawal from this contract. For this repayment, we will use the same means of payment you used for the original transaction, unless expressly agreed otherwise with you; in no event will you be charged fees as a result of this repayment.
If you requested that the services should begin during the withdrawal period, you must pay us a reasonable amount corresponding to the proportion of services already provided up to the point at which you notify us of your exercise of the right of withdrawal from this contract, compared to the total scope of services provided for in the contract.
Compensation for value regarding services is due only under the statutory requirements, in particular where you were duly informed and expressly requested early commencement of performance. No compensation for value is due for free-of-charge use. Merely logging in or agreeing to these Terms is not a statement regarding early expiry of your right of withdrawal. For an ongoing digital service, a statutory right of withdrawal does not expire solely because the account is activated.
For distance contracts concluded via our online interface, you can additionally use the easily accessible "Cancel contract" function available there during the withdrawal period and submit your statement via "Confirm withdrawal". You will promptly receive an acknowledgment of receipt on a durable medium. Other permissible means of withdrawal remain available.
If you wish to withdraw from the contract, you may complete and return this form.
To Lioverse UG (haftungsbeschränkt), Karl-Arnold-Straße 31, 52525 Heinsberg, Germany, email: info@lioverse.de
I/we (*) hereby give notice that I/we (*) withdraw from my/our (*) contract for the purchase of the following goods (*) / the provision of the following service (*):
____________________________________________________
Ordered on (*) / received on (*): _________________________
Name of consumer(s): ____________________________
Address of consumer(s): _________________________
Signature of consumer(s) (only for notification on paper): ____________________________________________________
Date: __________________
(*) Delete as applicable.
