It is just after ten in the evening. An associate is working on a brief that has to go out tomorrow. The facts are long, the other side has written thirty pages, and the summary simply will not get shorter. So he copies the opposing brief into a public chatbot and asks for an outline. A few seconds later it is there. It is even good.
Whether he has just committed a criminal offence, he does not know. And that is exactly the problem.
- § 203 of the German Criminal Code (StGB) prohibits the unauthorised disclosure of client secrets. Since 2017, law firms may involve service providers if this is necessary and the providers are bound to confidentiality.
- § 43e of the German Federal Lawyers’ Act (BRAO) sets out how: careful selection, a contract in text form with fixed minimum content, and special rules for providers abroad.
- This applies to the whole chain: cloud storage, identity provider, AI model. Every subcontractor must be bound to confidentiality and prove its data location.
- A server location in Europe alone does not protect you: if the provider belongs to a US group, the US CLOUD Act applies.
- Public chatbots generally do not meet these requirements. Client data does not belong there.
- A suitable AI tool comes with the contract under § 43e BRAO, processes data in Germany or the EU, does not train on your data and backs every answer with evidence.
What § 203 StGB covers
§ 203 of the German Criminal Code makes the violation of private secrets a criminal offence. In other words, it is the duty of professional secrecy protected by criminal law, and it applies to every professional bound by secrecy. Under paragraph 1 no. 3, lawyers belong to the group of professionals bound by secrecy. Anyone who discloses, without authorisation, a secret entrusted to them or otherwise learned in this capacity is liable to prosecution.
Professional law adds § 43a(2) BRAO: the duty of confidentiality regarding everything learned in the course of practice. Together, these form the framework against which every AI tool in a law firm has to be measured.
The 2017 reform: service providers are allowed, under conditions
For a long time it was unclear whether a law firm could use external IT service providers at all without disclosing secrets. The legislator clarified this in 2017. Since then:
Involvement is allowed
Secrets may be disclosed to other assisting persons insofar as this is necessary for their work. This can include external IT and software providers.
The provider is liable too
An assisting person who discloses a secret without authorisation is liable to prosecution themselves.
The firm must take precautions
The firm itself can also be liable if it did not ensure that the assisting person was bound to secrecy.
The most important practical consequence lies in the third point: responsibility stays with the firm. It is not enough for a provider to promise confidentiality. The firm has to actively bring about the obligation of secrecy.
§ 43e BRAO: how to involve service providers correctly
How this works under professional law is set out in § 43e BRAO. For AI tools, four points are decisive.
Careful selection
The firm must select the provider carefully and may only give it as much access to secrets as the service requires.
In practice: Check the storage location, place of AI processing, subprocessors and security measures before you decide.
Contract in text form with minimum content
The contract must be concluded in text form and bind the provider to confidentiality, with a notice of the criminal consequences. It must oblige the provider to obtain knowledge only as far as necessary for the service and specify whether, and under what conditions, further persons may be involved.
In practice: Ask to see the contract. If one of these points is missing, the tool is not suitable for client data.
Providers abroad
If the service is provided abroad, this is only permitted if the protection of secrets there is comparable to the protection in Germany.
In practice: Pay attention to where the AI request is actually processed, not just where the data is stored.
Mandate-specific services
If a service directly serves a single mandate, § 43e BRAO also requires the client’s consent. Whether a generally used AI tool falls under this has not been conclusively settled.
In practice: If in doubt, check with your bar association or professional liability insurer whether to obtain consent.
Data protection law applies alongside: personal data requires a data processing agreement under Art. 28 GDPR. It does not replace the obligation under § 43e BRAO but comes on top. Many providers combine both in one contract.
§ 203 StGB and the GDPR: two duties, two protective aims
Professional secrecy and data protection are often mentioned in the same breath. But they protect different things, and one does not replace the other.
| § 203 StGB | GDPR | |
|---|---|---|
| What is protected | Third-party secrets entrusted to or otherwise learned by a professional bound by secrecy, expressly including trade and business secrets of companies | Personal data of natural persons |
| Who is bound | Professionals bound by secrecy and the persons assisting in their work | Every controller and every processor |
| Consequence of a breach | Criminal liability, plus consequences under professional law | Fines from the supervisory authority, damages |
| Contract with the provider | Confidentiality obligation under § 43e BRAO, in text form and with instruction on the criminal consequences | Data processing agreement (DPA) under Art. 28 GDPR |
In practice this means: a DPA does not resolve professional secrecy. A provider can be fully GDPR-compliant and still be unsuitable for client data, for example because the confidentiality obligation is missing or a subcontractor in the chain is not bound.
What do the bar associations say?
The German Federal Bar (BRAK) published “Notes on the use of artificial intelligence” at the end of 2024 and updated them in 2026. They focus on three duties: checking and controlling the results of AI, maintaining confidentiality with every input and being transparent towards clients. They also address the relationship with the EU AI Act.
The notes are guidance with the character of a recommendation. They do not relieve the firm of its own assessment, but they set a clear direction: AI is allowed as long as the firm keeps control over data and results. For open individual questions, for example whether a tool requires client consent, the firm’s own regional bar is the first point of contact.
Not just the software provider: the whole chain counts
This is the point most often overlooked in practice. Modern AI software is not a single service provider but a chain: documents are stored with a cloud provider, login runs through an identity provider, answers are generated by an AI model at yet another provider, and there are often text recognition, monitoring or support on top. Each of these links comes into contact with client data, or at least can.
For the firm this means: it is not enough for the software provider to sign a confidentiality declaration. Every subcontractor that may have access to secrets must also be bound to confidentiality under § 203 StGB, and the contract under § 43e BRAO must stipulate that the software provider ensures this. And each must be able to prove where it processes the data.
Storage and hosting
Where are the documents stored, with which company, in which country?
Identity and login
Who manages accounts and login data? External identity providers often see more than you think.
AI model
Where is the request processed, is anything stored there, is there training?
Other services
Text recognition, monitoring, support: every service with access to content belongs in the review.
The US CLOUD Act: server location alone is not enough
There is another point that surprises many firms. The US CLOUD Act of 2018 allows US authorities to require US companies to hand over data in their possession or control, regardless of where the servers are located. This also covers European subsidiaries of US groups, including the large cloud platforms such as Microsoft Azure, Amazon Web Services or Google Cloud. A data centre in Frankfurt therefore offers little protection if it is owned or controlled by a US group.
Whether such access occurs in a given case is another matter. For professionals bound by secrecy, however, the legal possibility alone is reason enough to look closely. What matters, therefore, is not only where the data is stored but who owns the companies in the chain.
Why public chatbots are risky
Back to the associate at ten in the evening. The problem is not AI itself, but the framework in which he used it:
Public chatbot
- No contract under § 43e BRAO, no confidentiality obligation
- Depending on the plan, inputs are stored or used for training
- Processing often outside the EU, subprocessors unclear
- Answers not tied to sources
Suitable AI tool
- Contract with obligation under § 43e BRAO and DPA under Art. 28 GDPR
- No training, no storage at the AI provider
- Processing in Germany or the EU, providers disclosed
- Every answer with its source, verifiable against the original
For that evening, this means: a public chatbot is fine for general questions unrelated to a mandate. For briefs, contracts, correspondence and anything that allows conclusions about a mandate, it is not. Anonymising helps less than you might think: a case can often be recognised from details nobody considers identifying.
Five questions for every AI tool
- Is there a contract under § 43e BRAO?With a confidentiality obligation, a notice of the criminal consequences and rules for further persons.
- Where is the data stored, and where is the AI request processed?Both count. Storage in Germany helps little if processing happens elsewhere.
- Is the data used for training or stored?The answer should be no twice, laid down in the contract.
- Who is involved in processing?All subprocessors should be disclosed by name and location, each bound to confidentiality under § 203 StGB, none under US control.
- Can answers be checked?Every statement should come with a source. That is not a question of § 203 StGB, but of a lawyer’s due diligence.
How aiuno implements this
aiuno was developed together with German law firms and treats § 203 StGB not as a footnote but as the starting point of the architecture, for the whole chain.
| Requirement | How aiuno handles it |
|---|---|
| Contract under § 43e BRAO | Data processing agreement with confidentiality and purpose limitation clauses, aligned with the minimum content under § 43e(3) BRAO. |
| Data location and processing | Hosting with Hetzner in Falkenstein. AI processing runs at AKI.IO in Germany or Scaleway in the EU. For mandates with special requirements there is a profile in which all AI processing takes place exclusively with a German provider. |
| Training and storage | No training on your data, zero data retention at the AI provider. Only the question and the relevant excerpts go to the AI provider. |
| The whole chain | Every link is named with its location in the Trust Center: hosting with Hetzner (Falkenstein), AI processing at AKI.IO (Berlin) or Scaleway (France), text recognition with Tesseract OCR (open source, Germany/EU), operation by qunaira UG (Germany). Data processing and § 203 agreements are in place with all of them. |
| Identity and login | Self-hosted Zitadel instead of an external identity provider, two-factor login without exception. |
| US CLOUD Act | No US or non-EU processors for user content. All parties involved are European companies. |
| Access and evidence | Two-factor login for everyone, roles per workspace, audit trail. In the profile for special requirements, it is also logged who opened which document. |
| Verifiability | For every answer, aiuno names the document, the section and the exact passage, and checks before answering that the quote is really there. Final responsibility stays with the lawyer. |
An AI policy for the firm
Technology alone does not solve the problem from the beginning. The associate did not act out of carelessness, but because nobody had told him which tool he may use for what. A short internal policy creates more certainty than any ban:
- which tools are approved for client data and which are not,
- which tasks may be done with AI and who reviews the result,
- how consent is handled where it may be needed,
- who to contact when something is unclear.
What matters is that there is an approved tool. If you do not give your people a good tool, do not be surprised when they find one themselves.
Conclusion
§ 203 StGB does not prohibit the use of AI in law firms. It requires the firm to create the framework: the right provider, the right contract, the right processing. Set this up properly once and you can use AI in daily work without hesitating over every brief. And the associate can get back to his outline at ten in the evening, just in the right tool.
Frequently asked questions
May lawyers use AI?
Yes. § 203 StGB and professional law do not prohibit AI. What matters is that client secrets only go to service providers that have been carefully selected under § 43e BRAO and are contractually bound to confidentiality.
May I enter client data into ChatGPT?
Into the public version, as a rule, no. There is no contract under § 43e BRAO, and depending on the plan, inputs are stored or used for training. General questions unrelated to a mandate are a different matter.
Who is an assisting person within the meaning of § 203 StGB?
People who assist in the professional work of the firm. Since the 2017 reform, this includes external service providers such as IT and software providers, insofar as their involvement is necessary.
What must the contract with the AI provider contain?
Under § 43e(3) BRAO, among other things: a confidentiality obligation with a notice of the criminal consequences, the duty to obtain knowledge only as far as necessary, and rules on whether further persons may be involved.
What does the US CLOUD Act have to do with my firm?
It allows US authorities to demand data controlled by US companies, even if the servers are in Europe. If your AI tool uses a provider with a US parent anywhere in the chain, a European server location alone is not sufficient protection.
Do subcontractors also have to be bound to confidentiality?
Yes. Anyone who, as an assisting person, may have access to client secrets must be bound: cloud storage, identity provider, AI provider. The contract with the software provider must stipulate that it ensures this with its subcontractors.
Do I need my clients’ consent?
For services that directly serve a single mandate, § 43e BRAO requires consent. Whether a generally used AI tool falls under this has not been conclusively settled. If in doubt, obtain consent or clarify the question with your bar association.
What is a secret within the meaning of § 203 StGB?
A fact known only to a limited group of people, in whose confidentiality the person concerned has a legitimate interest. Trade and business secrets are expressly included. For a law firm, this is practically everything entrusted to it or otherwise learned in a mandate, even the fact that a mandate exists.
What are the consequences of violating § 203 StGB?
Imprisonment of up to one year or a fine. If the offender acts for payment or with the intention of enriching themselves or another person or of harming someone, up to two years. The offence is only prosecuted upon application. Consequences under professional law and civil liability come on top.
Who is covered by § 203 StGB?
Professionals bound by secrecy, among them doctors, psychotherapists, lawyers, notaries, tax advisers and auditors. Since 2017, the persons assisting in their work are covered as well, such as IT service providers.