Skip to main content
NexPatch
Guide5 min read

LLM Hosting and § 203 StGB: What Law Firms Must Verify in AI Providers

Section 203 of the German Criminal Code does not prohibit law firms from having language models hosted by service providers. Since 2017, professionals bound by secrecy are permitted to disclose confidential information to cooperating service providers to the extent necessary. This requires a formal duty of confidentiality, further specified for attorneys under Section 43e BRAO.

LLM Hosting and § 203 StGB: What Law Firms Must Verify in AI Providers

LLM Hosting and § 203 StGB: What Law Firms Must Verify in AI Providers

Section 203 of the German Criminal Code does not prohibit law firms from having language models hosted by service providers. Since 2017, professionals bound by secrecy are permitted to disclose confidential information to cooperating service providers to the extent necessary. This requires a formal duty of confidentiality, further specified for attorneys under Section 43e BRAO.

Why this question affects every law firm

AI has arrived in German law firms: 63.6% already use it actively, and 82.5% of users rely on public tools like ChatGPT. As soon as case file contents enter a language model, the operator becomes a party to the client secret. Whether this is permitted depends not on technology, but on whether the law firm has established the service provider's cooperation in full accordance with professional and criminal law.

What Section 203 StGB has permitted since 2017

With the 2017 legislation protecting professional secrecy when third parties cooperate in professional duties, the German legislature expressly regulated external service providers. Under Section 203 StGB:

  • Secrecy holders may disclose confidential information to persons cooperating in their professional duties to the extent required for their cooperation (Section 203 (3) StGB).

  • The cooperating person is subject to criminal penalties if they disclose such secrets without authorization (Section 203 (4) sentence 1 StGB).

  • The law firm itself may be penalized if it failed to obligate the cooperating person to confidentiality and that person discloses a secret without authorization (Section 203 (4) sentence 2 no. 1 StGB).

For LLM hosting, this means external operation is permissible if necessary and effectively bound by confidentiality obligations.

What Section 43e BRAO requires additionally

For attorneys, Section 43e BRAO specifies how this obligation must be structured:

  • Necessity: The service provider receives access only to the extent required for the service.

  • Careful selection: The law firm selects the provider carefully and terminates cooperation if requirements are no longer met.

  • Written agreement in text form: The provider is bound to secrecy and instructed on criminal penalties for violations. The contract governs whether and how subcontractors are involved.

  • Foreign services: For services performed abroad, access is permitted only if secret protection is comparable to that in Germany.

  • Individual case mandates: If the service directly serves an individual client mandate, client consent is required.

Data protection obligations continue in parallel. When a provider processes personal data, a data processing agreement under Art. 28 GDPR is additionally required.

Three hosting models compared

Public AI API. The provider processes content in its cloud data center and acts as a service provider under Section 43e BRAO. The law firm must check whether terms contain a formal secrecy obligation or whether a supplementary agreement is required.

AI API via Private Link in an EU region. Microsoft Azure, AWS, and Google Cloud offer private networking connections to AI services in European regions. Traffic does not traverse the public Internet, but the provider still processes contents and remains a service provider.

Private Operation. The language model runs on law firm servers or in a dedicated German data center. If run in-house, there is no external party. If managed by a specialist, the provider is bound under Section 43e BRAO while contents never leave the agreed infrastructure. Learn more under Private AI infrastructure.

Checklist: seven questions for every AI provider

  1. Where exactly are prompts, documents, and answers processed and stored?

  2. Who has technical access to these contents, including in support and maintenance?

  3. Is there a written secrecy agreement with instruction on criminal penalties?

  4. Which subcontractors are involved, and are they equally bound?

  5. Is content used for model training or product improvement?

  6. Does access occur from a third country, and is secrecy protection comparable?

  7. Are a data processing agreement and technical-organizational measures provided prior to contract conclusion?

Anyone unable to answer these questions clearly should not feed client data into the system. Learn more: AI vendor sovereignty check.

What this means for RAG in the law firm

A RAG system accesses your entire case file repository to deliver cited answers. The hosting question applies not to individual prompts, but to entire firm knowledge. How we implement private RAG for attorneys on dedicated infrastructure is shown on our law firms industry page.

Frequently Asked Questions

Does Section 203 StGB prohibit law firms from using cloud AI?

No. Section 203 StGB permits disclosure to cooperating service providers to the extent necessary. However, the law firm must bind the provider to confidentiality under Section 43e BRAO.

Is a GDPR data processing agreement sufficient on its own?

Not alone. The GDPR DPA covers data protection. The professional secrecy obligation in text form with instruction under Section 43e BRAO is an independent statutory requirement.

Is a self-hosted LLM automatically compliant?

It avoids transmitting data to external providers, but case-level permissions, logging, and deletion concepts must still be maintained, and operating personnel must also be bound by confidentiality.

Sources and References

  • Sections 203 StGB and 43e BRAO, gesetze-im-internet.de
  • Federal Bar Association (BRAK), Guidelines on the Use of Artificial Intelligence, December 2024
  • Wolters Kluwer Benchmark Report 2026, n = 633, survey 07 to 09/2025

Full-Stack Development

From Idea to Production in Weeks

Next.js, React, TypeScript - co-founded products with government funding support.

See Our Work

Related Articles

RETURN TO BLOG
Managed AI operations: what needs to happen after go live
Guide7 min read

Managed AI operations: what needs to happen after go live

Managed AI operations means that the ongoing tasks after launch are contractually assigned to a partner: monitoring quality, cost and availability, retraining, tested updates, access management and logging. The goal is an AI system that delivers reliably for years instead of losing its value after a few months.

October 8, 2026
How to check AI vendor sovereignty: 10 pieces of evidence you should request
Guide7 min read

How to check AI vendor sovereignty: 10 pieces of evidence you should request

Whether an AI vendor operates with sovereignty cannot be judged from claims like "GDPR compliant", only from verifiable evidence. This includes the location and operator of the hardware, the list of subprocessors, the jurisdiction of the parent company, access to logs, a binding statement on training, encryption, a data deletion policy and an arrangement for the exit.

October 8, 2026
Measure AI project success: the baseline before you start
Guide7 min read

Measure AI project success: the baseline before you start

You measure the success of an AI project by recording a baseline before you start: a business metric such as cycle time, error rate or capital tied up, measured over a representative period under documented conditions. After launch, you compare the same metric under the same conditions. Thresholds agreed in advance decide on expansion, adjustment or shutdown.

October 8, 2026
SLA for AI systems: how to agree on monitoring, retraining and response
Guide8 min read

SLA for AI systems: how to agree on monitoring, retraining and response

An SLA for AI systems defines what an operator owes you after launch. Beyond availability, it covers quality measured against a baseline set in advance, cost limits, rules for retraining and model updates, severity levels with response paths, clear reports, and the obligations your company takes on.

October 8, 2026
From pilot project into operations
Guide7 min read

From pilot project into operations

Most AI pilots don't fail on the technology. They fail on what comes after: data that isn't mature enough, no fit into daily work, and no clear ownership once the pilot wraps up. Closing those three gaps deliberately before the pilot ends is what reliably turns it into stable, monitored operations rather than an unused demo.

October 8, 2026

We use cookies and similar technologies to enhance your browsing experience, analyze site traffic, and personalize content. You can choose which categories to accept.

Learn more in our Privacy Policy and Imprint.