CONFIDENTIALITY

Translating confidential documents: what to agree before sharing

Clarify access, tools, file transfer and retention from the first sample through project closure.

By LocalizeZone ·
A woman in professional attire organizing documents with folders and a calculator, sitting indoors.

The short answer

Agree confidentiality scope, authorized access, permitted tools, transfer channels and retention before sending sensitive files. An NDA should be supported by practical handling arrangements.

Start with a controlled sample

Flag contracts, personal data, financial information or unpublished product material at the enquiry stage. A redacted sample and volume description can support an initial assessment while full-sharing terms are discussed.

Distinguish redaction for quoting from omissions in the final translation. The production scope must explain which information will eventually be provided.

Make confidentiality specific

The resources accompanying ATA — Model Contract for Translators include a confidentiality agreement. For your project, translate general expectations into clear questions.

  • What is confidential, and what use is permitted?
  • Which project roles can access the files?
  • What conditions apply to subcontractor access?
  • How are working copies and terminology data handled?
  • Who must be contacted if an incident occurs?
Close-up of stacked binders filled with documents for office or educational use.

Discuss cloud and AI tools

Ask whether cloud platforms, machine translation or AI will be used. State any restrictions on submitting content to external services before files are handed over.

“Is it secure?” is too broad to settle the workflow. Ask which tools are allowed, how data is handled and what requires your approval. Use a non-sensitive sample while unresolved conditions are discussed.

Control transfers and versions

Use the agreed sharing channel, grant access to the intended recipients and avoid public file links. Label source versions and tell the team which previous file is obsolete.

An illustrative naming pattern is “Contract_A_v03_source” for the approved source and “Contract_A_v03_review” for the review copy. One owner should consolidate comments rather than circulate conflicting versions.

Plan project closure

Agree the working-file retention period and how files are returned or removed. If you want an approved glossary retained for future work but not the full contract text, record that distinction.

Ask your legal or information-security team to review requirements that arise from specific contracts or regulated content. This guide is project preparation advice rather than a determination of those obligations.

Frequently asked questions

Can I send a redacted sample for a quote?

Yes. Describe the remaining material so that scope is not underestimated.

Does an NDA authorize every translation tool?

No. Record tool, access and data-sharing restrictions separately when required.

References

Project checklists and examples are written by LocalizeZone. Linked references support the specific statements marked in the article.

Discuss your project

Describe the sensitive material and your confidentiality requirements first. We can discuss the intake process before you send the complete files.

Related guides