A 200-page draft Geschäftsbericht lands in your inbox in January. The English deadline is brutal, DeepL is one click away, and the cover email says bitte streng vertraulich behandeln. That instruction binds the human who reads it. It says nothing about the engine you paste it into—and that gap is where the real exposure lives.
I translate annual reports for a living—full-time since 2008, somewhere north of 7,000 jobs, a fair number of them DAX- and MDAX-adjacent issuers under NDA. Every January I get some version of that email. So let me walk through what your draft actually is under EU law, what a translator’s NDA has to cover, where GDPR enters, and why “the server is in Frankfurt” doesn’t close the question.
What your draft annual report actually is under EU law
Start with the category, not the confidentiality stamp. Under Article 7 of the EU Market Abuse Regulation, inside information is “information of a precise nature, which has not been made public, relating, directly or indirectly, to one or more issuers… and which, if it were made public, would be likely to have a significant effect on the prices” of the related instruments. A pre-publication earnings draft hits all four elements: it’s precise, it’s non-public, it’s issuer-related, and it’s price-sensitive. That’s not a stylistic claim. That’s the legal definition.
People assume a document only “becomes” inside information when it’s finished. MAR closes that door explicitly. Article 7 treats “intermediate steps in protracted processes” as inside information in their own right where they “independently satisfy the criteria.” A work-in-progress draft sent to a translator is exactly such an intermediate step. The half-edited version is regulated material too.
And the moment that file reaches me, I’m not just a vendor with a confidentiality clause. Under Article 8(4), a person “having access to the information through the exercise of an employment, profession or duties” is a professional insider. The insider-dealing and unlawful-disclosure prohibitions attach to me on receipt—and Article 18 says the issuer must put me on its insider list, alongside accountants and other external advisers, with a written acknowledgement that I understand the duties and the sanctions.
Now the part most people miss. Article 10 defines unlawful disclosure as passing inside information “to any other person, except where the disclosure is made in the normal exercise of an employment, a profession or duties.” There is no carve-out for automated processing. A cloud MT engine that retains your text to train its models is, functionally, another recipient. Feeding it a regulated draft is a disclosure event.
One cross-border wrinkle for clients with a London listing. Post-Brexit, UK MAR and EU MAR run in parallel. As one compliance summary puts it, a company listed on both a UK and an EEA venue “must comply with both UK MAR and EU MAR.” A draft for a Frankfurt- and London-listed issuer is inside information under two regimes at once, policed by two authorities. The translator workflow has to satisfy both—not whichever one you remembered.
What a proper translator NDA must cover
A generic freelancer NDA—“I won’t share your stuff”—is not built for this. The NDA I use for Berichtssaison assignments runs to four pages, and every section earns its place. Here’s why each exists.
- Scope that names the artefacts. Not just “the document.” The draft, every revision, translation-memory segment pairs, glossary and terminology entries, and file metadata. A confidential number can survive in a TM segment long after the PDF is deleted.
- An explicit subcontracting prohibition. No cloud MT engine, no cloud-hosted TM, no offshore reviewer—without prior written consent. This is the clause that closes the DeepL loophole. Silence here means the issuer is trusting the translator’s habits instead of a contract.
- A return-or-destruction schedule. A defined date by which all copies, working files, and TM data are deleted or returned, with confirmation in writing. “I’ll get around to it” is not a retention policy.
- A penalties clause with liquidated damages. Pre-agreed figures, so the consequence of a breach isn’t a speculative court fight after the price-sensitive harm is already done.
- Insider-list acknowledgement. The Article 18 written acknowledgement, folded in, so the regulatory obligation and the contractual one line up.
The difference between that and a one-page template is the difference between a clause that anticipates the MT problem and one that’s silent on it. Silence, in this domain, is exposure.
GDPR and the Auftragsverarbeitungsvertrag
MAR isn’t the only regime in play. The instant your draft contains natural-person data—board-member names, employee headcounts by region, individual remuneration disclosures—GDPR switches on and I become a data processor acting on your behalf. A specialist GDPR-in-translation analysis is blunt about the consequence: the translator “becomes a processor” and is “therefore prohibited from using public machine translation tools.” The same source notes that a financial report with no individual personal data sits outside GDPR—but a typical annual report is stuffed with exactly the personal data that reactivates the full chain.
That triggers Article 28(3): a written Auftragsverarbeitungsvertrag. The agreement has to specify the “subject-matter and duration of the processing, the nature and purpose of the processing, the type of personal data and categories of data subjects,” and it has to bind the processor to act only “on documented instructions from the controller,” maintain confidentiality, implement Article 32 security measures, and delete or return all personal data when the work is done. It must be “in writing, including in electronic form.” Not a handshake.
Then there’s data residency. Personal data embedded in a financial draft can’t be shipped to non-EU servers without satisfying GDPR’s Chapter V transfer rules—and for most ad-hoc MT and cloud-TM setups, those rules simply aren’t met. This is where “the server is in Frankfurt” falls down: a verbal reassurance is not a confirmation. Without it written into the AV agreement, with named processing locations, you have a claim you can’t audit and can’t defend.
CAT tools and the cloud risk
The tools translators use carry their own geography. Trados Studio running locally keeps translation memories on my machine, behind my controls. Trados GroupShare—the cloud variant—stores TM data on a server with its own access model and its own jurisdiction. Same brand, very different risk profile. The question is never “do you use Trados,” it’s “where does the TM live and who can reach it.”
DeepL deserves its own paragraph because the tiers diverge sharply. The free web translator reserves the right to “process the content you upload… to train and improve our neural networks” and states plainly that you “may not use the Free Services for processing content containing confidential or personal data of any kind.” So the free tool tells you, in its own terms, not to do the thing IR teams reach for it to do. DeepL Pro and API Pro are materially stronger: submitted texts “will not be permanently stored” and are deleted after the job—though an enterprise debug exception can retain encrypted content for up to 72 hours, which a DPA for price-sensitive work needs to address. And one trap worth flagging: the free API Developer tier “reserves the right to perpetually store any Content or Processed Content.” A workflow built on it never lets your data go.
“Opt out of AI training” helps, but know its limits. It stops your text from feeding the model. It does not, by itself, prove where the data physically sits, who can access logs, or how long debug copies persist. Those are separate contractual questions.
Secure file handoff
Now the boring part that actually matters: how the file gets to me. A password-protected ZIP over email is not adequate for a price-sensitive pre-publication draft. The password usually rides in a second email; the attachment sits on mail servers you don’t control; and the whole thing assumes email itself is a secure channel, which it isn’t.
Better options exist and they’re not exotic: SFTP, an encrypted client portal, or the client’s own virtual data room. Two of those put the issuer’s IT security team in control of the channel, which is usually right for the most sensitive drafts. What I can guarantee is the receiving end—encrypted storage, no cloud TM, no MT, deletion on schedule. What I can’t manufacture is the transport layer; that’s a shared responsibility. The risk window worth naming is the gap between file creation and translator delivery: the draft is most exposed exactly when it’s moving and least supervised. Pick the channel before that window opens, not during it.
Agency vs. freelance: the data-chain question
Here’s a question IR teams rarely ask out loud: between the CFO’s draft and the delivered English file, how many separate links are there? In a multi-vendor agency workflow, count them—each project manager, each freelance translator, each reviewer, each cloud platform is a node. Every node ideally needs its own NDA, its own AV agreement, and a known server jurisdiction. Miss one and you have a gap you can’t see.
The argument for a specialist freelancer is single-point accountability: one NDA, one AV agreement, one server location, one person on the insider list. When something has to be confirmed in writing, there’s one signature, not a subcontracting tree. I’m not pretending scale never matters—a 600-page report across five languages in ten days is an agency job, and a good agency can lock its chain down tight. The point is that scale adds links, and links are where confidential data leaks. So ask any LSP, before you hand anything over: who exactly touches this file, where do their tools store data, and can you show me every NDA and AV agreement in the chain?
A pre-briefing checklist for IR and legal teams
Run this before the first file moves, not after the deadline panic:
- NDA signed before any file is shared—drafts, TM segments, glossary, and metadata all in scope.
- AV agreement (Article 28) executed and on file, with documented-instructions and deletion clauses.
- EU server location confirmed in writing, with named processing locations.
- AI-training opt-out documented for any MT tool anywhere in the workflow.
- Secure file-transfer channel agreed and tested—SFTP, encrypted portal, or your VDR.
- Retention and certified-deletion timeline set and logged, with written confirmation on completion.
One January I won’t forget
A draft arrived one Berichtssaison containing a profit warning that had not yet been disclosed to the market. Material, precise, non-public—textbook inside information, and I knew it the moment I read the management commentary. The clause that mattered that week wasn’t the rate or the deadline. It was the subcontracting prohibition: no cloud MT, no shared TM, no exceptions. I worked it locally, delivered through the client’s portal, deleted on schedule, confirmed in writing.
Picture the same file pasted into a free web translator to “save a day.” That number is now on a third-party server with training rights over the content—an Article 10 disclosure of price-sensitive information before the issuer chose to make it public. The translator made the keystroke; under MAR, the issuer carries the liability. The day you’d have saved is not worth that.
So my standing advice: ask for the standard NDA and AV agreement template before the first assignment, not after the draft is already in flight. If you’d like to see how I handle Berichtssaison work—or just pressure-test your current chain—the services and pricing page lays out the specifics, and you can request the NDA and AV templates here. Get the paperwork done in the quiet weeks. January won’t give you the time.
One honest limit, since it always comes up: I don’t offer sworn or certified translation—court-sworn colleagues handle those. What I offer is a specialist DE ↔ EN financial translation workflow built so your draft never leaves a chain you can audit.