ISO 17100 Certified  ·  ITI Member  ·  CIOL Listed  ·  UKVI Accepted  ·  Security-Vetted Translators Available  ·  London, UK — Est. 2011

ISO 17100 Certified  ·  ATA Member  ·  NAJIT Member  ·  USCIS Accepted  ·  Security-Cleared Translators Available  ·  Miami, FL — Est. 2011

US USA GB UK
US USA GB UK

Confidential legal translation: NDAs, GDPR and secure files

Yes, a legal document can be translated without exposing the data in it, provided the provider signs an NDA, moves the file only through an encrypted channel, limits who can open it, and deletes it on a set date. Below: what to ask for, and what the law requires.

Updated November 2026.

A confidential legal translation is a translation done under a written confidentiality obligation, with the file restricted to the people doing the work and protected in transit, in storage and at deletion. Contracts, witness statements, settlement terms, patent drafts and the medical records in an injury claim all belong in this group. The language work is the visible part; the handling around it is what keeps a leak from turning into a second lawsuit.

What makes a legal document sensitive during translation?

Most legal documents carry at least one of four kinds of protected content: personal data, trade secrets, privileged communication between a lawyer and a client, or commercial terms nobody has signed yet.

A share purchase agreement names the price before the market knows it. A witness statement lists home addresses and dates of birth. A patent description that gets out before filing can cost the applicant novelty. Translation makes the problem bigger because it multiplies copies: the source, the draft, the reviewed version, the translation memory, the email thread with the reviewer. Each copy is one more place to lose control of.

Where do leaks actually happen in a translation job?

Leaks rarely come from someone breaking into a server. They come from ordinary habits: a contract pasted into a free online translator, a file forwarded to a freelancer’s personal inbox, a draft left on a laptop for years.

Free machine translation tools are the most common slip. They usually run under consumer terms that let the operator keep what you paste, so a clause typed in for a quick check may sit on a third party’s servers indefinitely (the accuracy side of that problem is covered in why AI translation is not accepted for legal and official documents). Email is the second: an attachment lands in the sent folder, the inbox, both backups and any mailbox it was forwarded to, and none of those get cleaned up when the job ends. Subcontracting chains are the third. The agency sends the file to a translator, who quietly passes part of it to a colleague who has signed nothing. Then there is the translation memory, the database that stores every translated sentence for reuse. If the provider keeps one shared memory for all clients, sentences from your settlement agreement can resurface as suggested matches inside another company’s project.

Should you ask a translation provider to sign an NDA?

Yes. Ask for an NDA before you send anything, and ask whether every translator and reviewer who will see the file is bound by the same agreement or an equivalent one.

A useful NDA for translation work does five things. It defines confidential information to include the source, the translation, any glossaries or notes, and the fact that the matter exists at all. It bans subcontracting without your written consent. It requires return or destruction of all copies on request. It survives the end of the project (two to five years is typical for commercial terms; indefinitely for trade secrets). And it names a governing law and court you can actually use. An NDA signed by the agency alone is thin if the translator is a freelancer with no agreement of their own, so ask that question directly. A mutual NDA is fine; a provider that stalls or refuses is telling you something. Read the provider’s published confidentiality terms as well (Translation AZ sets out its handling of client files on its confidentiality page), then ask for the NDA on top of them.

What does GDPR require from a translation workflow?

If the document contains personal data about people in the EU, the GDPR treats the translation provider as a processor, and Article 28 requires a written contract between you and the provider setting out what they may do with that data.

The full text is on EUR-Lex, Regulation (EU) 2016/679. The parts that touch translation are these. Article 3 extends the regulation to organisations outside the EU when they offer goods or services to people in the EU or monitor their behaviour, which is why a US company with European customers is in scope. Article 28 is the processor contract: purpose, duration, confidentiality of staff, no sub-processors without consent, deletion or return at the end. Article 32 asks for security appropriate to the risk and names encryption and pseudonymisation as examples. Article 33 requires a processor to tell the controller about a breach without undue delay. Chapter V covers transfers outside the EU and EEA, so you need to know in which country the provider stores files. Article 83 sets the upper fine at 20 million euros or 4 percent of worldwide annual turnover, whichever is higher, and the client (the controller) stays responsible for what its processor does.

In the UK the equivalent rules are the UK GDPR and the Data Protection Act 2018, enforced by the Information Commissioner’s Office; its guidance for organisations covers processor contracts in similar terms. The United States has no single federal privacy law, but two rules do reach translation work. HIPAA requires a covered entity to sign a business associate agreement before a vendor handles protected health information (see the HHS guidance on business associates), and the California Consumer Privacy Act requires contracts with service providers that handle California residents’ personal information (California Attorney General, CCPA). A medical record translated for an injury claim can fall under the first; a customer contract with California addresses can fall under the second.

What role does encryption play in a secure translation workflow?

Encryption protects the file while it moves and while it sits on a disk. It does nothing about who is allowed to open the file, so it is one control among four, never the whole answer.

In transit, the sound options are a client portal or SFTP, both of which run over TLS, instead of a plain email attachment. If email is unavoidable, a password-protected PDF or ZIP with the password sent by phone or text is a reasonable minimum for a one-off job. At rest, the provider’s storage should be encrypted, and so should the laptops of the translators who download the file. The other three controls are access limited to the people on the job, a log of who opened what and when, and a retention rule: the file is deleted on a named date and you get written confirmation. A provider that can describe all four in plain words is usually running them. One that answers “military-grade encryption” and nothing else usually is not.

What should you ask a translation provider before sending files?

Ask these ten questions by email, so that the answers are in writing before the first file leaves your system.

  1. Will you sign our NDA, or send yours, before we transmit the document?
  2. Who will see the file: in-house staff, freelancers or another agency? Is each of them under a confidentiality agreement?
  3. How do we send it: portal, SFTP or email? Is it encrypted in transit and at rest?
  4. In which country are files stored, with which hosting provider, and are copies made on translators’ own devices?
  5. Do you run client files through machine translation or AI tools, and if so, under what terms? Does the tool retain the text?
  6. Is our text kept in a translation memory, and is that memory shared with other clients?
  7. How long do you keep source and target files after delivery? Can you delete them earlier on request and confirm it in writing?
  8. Who do we contact about a breach, and how fast would you tell us?
  9. Will you sign a data processing agreement if the document contains personal data from the EU or UK, or a business associate agreement if it contains health information?
  10. Can you work from a redacted or pseudonymised version where the names do not change the meaning?

The answers also say a great deal about the provider’s general quality; the guide on how to choose a legal translation service covers the rest of that vetting.

How do you send a confidential document for translation safely?

Reduce what you send, lock the paperwork first, then use the provider’s secure channel in both directions.

  1. Decide what the translator truly needs. Leave out schedules, exhibits and attachments that are not part of the job.
  2. Redact or replace identifiers that do not affect the translation: account numbers, social security or national insurance numbers, dates of birth where the date is irrelevant.
  3. Get the NDA signed, and the data processing or business associate agreement if the content calls for one.
  4. Upload through the provider’s portal. If you must email, encrypt the attachment and send the password by a different channel.
  5. Put a deletion date in the order confirmation.
  6. Receive the translation the same way you sent the source, then ask for written confirmation that both have been deleted.
  7. File the signed NDA and the deletion confirmation with the matter.
Handling route Who can read the text What happens to it afterwards
Free online translator The tool’s operator, under consumer terms Typically retained; no deletion on request
Freelancer by email The translator, plus anyone they forward it to Sits in inboxes and backups until both sides clean up
Agency with NDA, portal and retention rule The named project team only Deleted on the agreed date, confirmed in writing

If something still goes wrong, the question becomes who pays. The post on liability for legal translation errors works through how courts and contracts split that risk between the client, the agency and the translator.

Who translates confidential legal documents, and how fast?

Translation AZ translates contracts, court filings and official records for businesses and individuals worldwide, from offices in Miami, Fort Myers and London. The agency is ATA certified, ITI certified and ISO certified, and its certified translations carry guaranteed acceptance by USCIS, the courts and the UK Home Office. Turnaround is 1 to 2 business days for 1 to 5 pages and 2 to 3 business days for 5 to 10 pages; longer projects are quoted individually. Pricing starts at about $30 per page. Read the confidentiality page, then request a quote and ask for an NDA in the same message, or call (800) 620-4789.

Frequently asked questions

Can I translate legal documents without exposing sensitive data?

Yes. Send only the pages the translator needs, redact identifiers that do not change the meaning, get an NDA signed first, and transmit the file through the provider’s encrypted portal instead of email. Agree a deletion date in writing. Those four steps remove most of the exposure; the rest depends on the provider keeping access limited to the named project team.

Is Google Translate or ChatGPT safe for a confidential contract?

Not under the free consumer versions. Their terms generally allow the operator to store and reuse what you paste, and you have no NDA, no deletion right and no way to know who sees it. Paid enterprise versions have different terms, but they still produce no certified translation and give you no translator to hold responsible. For anything privileged or unsigned, use a human provider under an NDA.

Does GDPR apply to my translation if my company is in the United States?

It can. Under Article 3 the GDPR reaches organisations outside the EU that offer goods or services to people in the EU or monitor their behaviour. If the document contains personal data about EU residents, you need a processor contract with the translation provider under Article 28 and a lawful basis for moving the data outside the EU. A US business with no EU customers or employees in the document is usually outside its scope.

What happens to my files after the translation is delivered?

That depends on the provider’s retention rule, so ask for it in writing before you send anything. A sound provider deletes the source and target files on an agreed date, confirms the deletion in writing, and either keeps no translation memory of your text or keeps one that is never shared with other clients. If you need the translation stored for a later re-issue, say so and agree the period.

Is real-time interpreting for business calls confidential?

It can be, with the same controls as document work: an NDA with the interpreter, a call platform your own IT team has approved, no recording unless both parties agree, and no automatic AI transcription running in the background. Ask who else is on the interpreter’s side of the line and where any notes are kept. Consumer-grade AI interpreting apps usually process audio on third-party servers under terms you have not negotiated.