General terms and conditions
Last updated: November 2026
This English version is provided for convenience. In case of discrepancies, the German version prevails.
These general terms and conditions (“Terms”) apply to all advisory, analysis, development and training services provided by Alpaion LLC (“Alpaion”) to its clients (“Client”).
1. Scope
1.1 Alpaion's services are aimed exclusively at businesses, legal entities under public law and special funds under public law. No contracts are concluded with consumers.
1.2 Deviating or supplementary terms of the Client only become part of the contract if Alpaion expressly agrees to them in writing. Individual agreements (e.g. offer, statement of work, framework agreement) take precedence over these Terms.
2. Conclusion of contract
2.1 Alpaion's offers are non-binding unless expressly marked as binding. A contract is concluded by written or electronic acceptance of the offer (e.g. by email) or by the start of work with the agreement of both parties.
2.2 The scope, content and timeframe of the services are set out in the respective offer or statement of work.
3. Services
3.1 Unless expressly agreed otherwise, Alpaion provides services. Alpaion owes the professional performance of the agreed activity, not a specific economic or technical result. Work with formal acceptance is only owed if expressly agreed.
3.2 Alpaion may use qualified employees and subcontractors. Alpaion remains responsible to the Client for their work.
3.3 Recommendations, analyses and forecasts are based on the information available at the time they are prepared. The Client decides on their implementation at its own responsibility.
4. Use of artificial intelligence
4.1 Alpaion may use AI-supported tools to provide its services. Confidential Client data is only processed in systems that exclude the use of data for training AI models, or after prior agreement with the Client.
4.2 Outputs of AI systems that Alpaion develops or introduces for the Client may contain errors. The Client ensures that such outputs are reviewed by qualified people before material decisions are made. Compliance with the obligations applicable to the Client's use, in particular under the EU AI Act, rests with the Client as deployer unless expressly agreed otherwise.
5. Client cooperation
5.1 The Client provides Alpaion in good time with all information, data, access and contact persons required for the services and makes decisions within a reasonable period.
5.2 Delays or additional effort due to missing or late cooperation are not Alpaion's responsibility. Agreed dates are postponed accordingly; additional effort is charged at the agreed rates.
5.3 The Client is responsible for the lawfulness of the data it provides, in particular for being entitled to share it with Alpaion.
6. Fees and payment
6.1 Fees are charged on a time-and-materials basis at the agreed hourly or daily rates or as a fixed price. Travel time, travel and accommodation costs are charged separately as agreed.
6.2 All prices are exclusive of the applicable statutory VAT.
6.3 Time-and-materials services are invoiced monthly, fixed prices according to the payment schedule in the offer. Invoices are payable without deduction within the period stated on the invoice.
7. Dates and cancellation
7.1 Agreed dates are binding only if expressly designated as binding. Force majeure and circumstances for which the Client is responsible extend deadlines reasonably.
8. Rights of use
8.1 Upon full payment, the Client receives a non-exclusive right, unlimited in time and territory, to use the work results created specifically for it for its own purposes, unless agreed otherwise.
8.2 Alpaion's pre-existing know-how, methods, templates, tools and generally reusable software components remain Alpaion's property. Where they form part of the work results, the Client receives a non-exclusive right of use within the purpose of the contract.
8.3 Third-party software and services (e.g. cloud platforms, AI models, open-source components) are subject to the respective providers' licence terms. Licence and usage fees are borne by the Client.
9. Confidentiality and data protection
9.1 The parties treat all confidential information of the other party that becomes known to them during the collaboration as confidential and use it only to perform the contract. This obligation continues after the end of the contract.
9.2 Where Alpaion processes personal data on behalf of the Client, the parties conclude a data processing agreement under Art. 28 GDPR or the applicable data protection laws.
10. Liability
10.1 Alpaion is liable without limitation for intent and gross negligence, for injury to life, body or health and under mandatory statutory provisions.
10.2 In the event of a slightly negligent breach of essential contractual obligations, i.e. obligations whose fulfilment makes the proper performance of the contract possible in the first place and on whose fulfilment the Client may regularly rely, liability is limited to the foreseeable damage typical for the contract, but no more than the fees for the respective engagement in the preceding twelve months. Otherwise, liability for slight negligence is excluded.
10.3 Liability for loss of data is limited to the effort that would have been required to restore it had the Client made proper, regular backups.
11. Term and termination
11.1 Project contracts end once the agreed services have been provided. Retainer and framework agreements run for an indefinite period and may be terminated with the notice period agreed in the contract.
11.2 The right to terminate for good cause remains unaffected. Services provided up to termination are to be paid for.
12. Client references
Alpaion may name the Client with its name and logo as a reference during or after the engagement unless the Client objects. Content and results of the collaboration are only published with the Client's express consent.
13. Final provisions
13.1 The exclusive place of jurisdiction for all disputes arising from this contractual relationship is Alpaion's registered office, where legally permissible.
13.2 Amendments and additions must be made in text form. Should any provision be invalid, the validity of the remaining provisions is not affected.