AI & Data / Germany & European Union
AI contracts need to address a changing system, not merely a software licence. We structure the allocation of responsibility for training data, model updates, output quality, security and business use.
Where we can help
Buying and developing AI
We review proof-of-concept agreements, model APIs, enterprise licences, bespoke development and system integration. The contract should define the intended use, measurable evaluation criteria, dependencies and the consequences of changing a model or its data sources.
Rights and accountability
Key provisions cover inputs and outputs, training restrictions, confidentiality, third-party rights, subcontractors, audit access and assistance with regulatory duties. Contractual labels cannot displace statutory responsibilities under the AI Act or data protection law.
Failure and exit
We assess warranty promises, exclusions, liability caps, indemnities and insurance against the deployment’s risk. Exit provisions should address exportable data, documentation, continuity and deletion. A disclaimer that outputs may be inaccurate needs to be tested against the service actually promised.
From assessment to implementation
We can prepare a supplier comparison, negotiate the main agreement and schedules, or assess an existing dispute. For disputed performance, evaluation datasets, version records and agreed acceptance criteria often determine the strength of the claim.
Four practical examples
Illustrative scenarios, not reports of client mandates. The appropriate response depends on the facts and applicable law.
Hallucinated quotations
A procurement assistant invents supplier prices. We examine the agreed use and validation controls to assess contractual remedies and responsibility for losses.
Model changed without notice
An API update breaks a regulated workflow. Version-control commitments, notice periods and fallback rights become central to negotiations.
Training on customer data
A vendor reserves broad reuse rights over uploaded documents. We negotiate a defined processing purpose, restrictions on training and verifiable deletion.
Unclear development ownership
A company finances a custom model but cannot transfer it to a new operator. We clarify licence scope, access to components and practical exit deliverables.
What to send us
Please describe the product or dispute, the countries involved, your role and any deadline. Relevant contracts, technical documentation, correspondence and a short chronology help us identify the next steps. Agree a secure transfer channel before sending sensitive records.
Discuss your next step
We can define the scope of a review, identify urgent measures and agree the work and fees before proceeding. A website enquiry alone does not establish a mandate.
Related: IT & AI services · Legal updates · Our attorneys
Legal framework and further reading: German Civil Code. Content reviewed: 12 November 2026.