Where Does the Confidentiality Chain Break in Translation? The Subcontractor Problem

Most organisations that buy translation think of the process as a two-party relationship: themselves on one side, the translation provider on the other. In practice several links come in between, and each link produces a fresh copy of the document.

Contents

This article looks at why a translation non-disclosure agreement usually binds only the first link in the chain, at the points where the chain breaks, and at how those breaks can be closed in practice.

This is not an accusation but a structural problem. The industry’s business model is built on subcontracting; the answer is not to pretend otherwise but to make it visible and auditable.

How many hands does a translation job pass through?

In a typical corporate job the document stops at four points at the very least: the sales representative, the project manager, the translator and the reviser. To these you may add the designer who handles the typesetting before delivery, the specialist who prepares the term list and the team that carries out quality control.

The chain grows longer once it leaves the organisation. A large provider takes the job, passes part of it to another provider depending on the language pair, and that provider hands it to a freelance translator. In a sworn translation workflow an agency near the notary’s office joins in. On urgent jobs the text is split between several translators and the number of links doubles overnight.

Every link means a new copy, a new device and a new mailbox. Nobody tracks how many places the document physically sits in, because it is nobody’s job to do so.

One reason for this invisibility is that every link in the chain believes it has done its own job properly. The project manager uploads the file to the system and considers the task complete; the translator delivers and files the document away in an archive; the reviser leaves a copy on the desktop. Nobody has committed a breach, yet the document is now in four separate places.

Why is subcontracting unavoidable?

The translation industry rests structurally on freelance work. A Europe-wide study found that, on a weighted average, 78.4 per cent of translators worked freelance (Pym et al. 2012). The industry’s production capacity, in other words, largely sits outside the companies themselves.

The second reason is the range of languages. No provider can keep in-house specialists for every language pair. When a request for a Turkish–Japanese legal translation comes in, the work almost certainly goes to an outside specialist.

The third is fluctuating capacity. Corporate demand for translation does not flow evenly; tender periods, audit calendars and product launches create sudden pile-ups. Meeting those peaks with in-house staff is not economic.

Using subcontractors is therefore not a fault in itself. The fault lies in not disclosing that use and in failing to carry the obligations along the chain.

Buyer expectations are another factor that lengthens the chain. Asking a single supplier for dozens of language pairs, at short notice and at a low price, forces that supplier by definition to place work outside. The length of the chain is partly a result of your own purchasing choices; narrowing the scope also shortens the chain.

Where does the chain break?

The breaks tend to happen in the same places. The table below sets out the five points seen most often in practice, together with the symptom of each.

Break point	What happens?	Symptom
Obligations are not carried over on assignment	The subcontractor works under a lighter undertaking	The main agreement has no assignment clause
The channel is uncontrolled	The document travels by personal email or messaging	There is no defined system for file sharing
The device is uncontrolled	The document stays on a personal computer and in a cloud backup	Device and encryption requirements were never discussed
Tools connect to the outside	Sentences are sent to an external engine	There is no written machine translation policy
There is no destruction at the end of the job	Copies remain indefinitely	No retention period or destruction record was requested

These five points feed one another. If the channel is uncontrolled, controlling the device becomes meaningless; if there is no obligation to destroy, controlling the channel protects only the moment of delivery.

What the breaks have in common is that they are silent. None of them raises an alarm, none delays the delivery date, none shows up on the invoice. That is why the problem usually surfaces not through a leak but through an audit question: when nobody can answer “who has had this document?”

Does the confidentiality undertaking follow the chain?

The key idea is that the contracts mirror one another exactly. In practice this is called a back-to-back contract: the undertakings the provider gives you are passed on, with the same scope, into the contract it signs with the subcontractor. If they are not passed on, the weakest link in the chain becomes the link with the fewest obligations.

Two sentences in the contract are enough for this: if the provider intends to use a subcontractor, it notifies you in advance and seeks your approval; and it signs a written contract with that subcontractor containing obligations equivalent to those in this contract. Without the second sentence, the first is merely a notification.

A liability clause is needed as well: the provider is liable for the subcontractor’s acts as if they were its own. Without this clause, the parties point at one another when something goes wrong and it becomes unclear who your counterparty is.

These clauses have a deterrent side effect too. A provider obliged to pass the obligations on unchanged will decide against working with certain subcontractors. The contract thus becomes more than a text that resolves problems after the event: it becomes a tool that shapes supplier selection from the outset.

The freelance translator’s desk: device, licence, file

The last link in the chain is usually a one-person business. That is not a bad thing – this is the specialist who actually does the work. But the working environment lies outside corporate control.

According to the case study, 91 per cent of translators own the licence for the tool they use themselves (Pietrzak & Kornacki 2021). Tool configuration, backup settings and any machine translation connection are therefore the translator’s own choice. In the same study, 90 per cent of participants reported file compatibility problems and 70 per cent said they ran into them frequently.

Compatibility problems matter for confidentiality because the usual fix is to convert the file. Conversion is often done with free online tools. That is how a document reaches a server nobody ever planned for, not out of bad faith but in the rush to meet a deadline.

The question to ask at the end of the chain is therefore not “has a non-disclosure agreement been signed” but “which tools, which device and which channel is this person working with”.

Automated tools add a new link to the chain

In recent years another party has joined the chain, one that appears nowhere in the contract: the automated tools that translators or revisers use on their own initiative. Pasting a fragment of text into an online engine is, technically, a transfer of the document to the outside.

This use is usually a matter of habit rather than bad faith. People turn to such tools to confirm a term, to check a sentence quickly, to make sense of a long paragraph. Whoever works at the last link of the chain often does not know the confidentiality classification of the document; all that reaches them is the file and the deadline.

The classification therefore has to travel with the file. A single line in the project instructions, “no external engines or online tools are to be used on this job”, is more effective than a clause at the front of the contract once it reaches the person at the end of the chain. What carries the obligation is not the contract text but the instruction.

Promise or proof? Auditable confidentiality

A confidentiality undertaking is worth whatever can be verified of it. An undertaking that cannot be verified turns into an argument about damages once something has gone wrong, whereas the aim is that nothing goes wrong at all.

Verification does not require a heavy audit process. Access logs, destruction records and per-project team lists are enough for most organisations. If the provider can produce those three records within a reasonable time when asked, that is the best sign that the system genuinely works.

A simple test once a year may also be enough: pick a past job and ask who received the document and where it sits now. How long the answer takes to arrive tells you as much as the answer itself.

Keeping the audit light is the buyer’s responsibility too. An audit demand broader than necessary drives small providers away from bidding and narrows your supplier pool. A measured framework, three records and one test a year, is both workable and sufficient.

The Türkiye context

In Türkiye the least controlled version of the chain is found in the sworn translation market. Work changes hands frequently among the agencies clustered around notaries’ offices, and the customer assumes that the agency the document was handed to will do the work itself. Which translator the document actually goes to is usually not recorded.

The second local feature is that the business runs on an oral culture. Price, deadline and scope are agreed over the phone; often the only written document is the invoice. This creates an advantage in speed, but when a dispute arises there is no way to show who undertook what.

The third is that, for KVKK purposes, the organisation sending the document counts as the data controller. The length of the chain does not reduce your responsibility; on the contrary, supplier selection and supervision are part of your obligation as well. Not seeing the chain does not remove the legal risk.

What does this mean for you?

Shortening the chain is not always possible; making it visible is. The following six steps can be applied without adding to your costs:

Ask at the quotation stage: who will see this job, and will subcontractors be used?
Have a subcontractor notification and approval requirement added to the contract.
Get it in writing that the obligations will be passed on to the subcontractor unchanged.
Define a single channel for exchanging files and rule out email attachments.
Set written limits on the use of machine translation and file conversion tools.
Ask for a destruction record at the end of the job and keep that record.

On sensitive projects one further step is possible: a named team. The translator and reviser who will do the work are identified from the outset and any change is made subject to your approval. We explain how this approach is set up on our services page; to discuss your project, get in touch with us.

This article is for general information and is not legal advice. For your specific situation, consult your legal adviser.

Frequently asked questions

Can I find out who translates my document?

You can ask. Many providers treat the translator’s identity as a trade secret, but on sensitive projects a named team is common practice. The contract can require the list of people who will do the work to be disclosed and any change to be subject to approval.

Is using a subcontractor a problem in itself?

No. Because of language pairs and capacity, using subcontractors is normal in this industry. The problem is concealing that use, or failing to pass the same obligations on to the subcontractor unchanged.

Is signing a non-disclosure agreement enough?

It is not. The agreement closes only the legal layer. Technical and procedural measures are needed alongside it: restricted access, a single channel, a retention period, a destruction record and a right of audit.

How do I tell how many links the chain has?

Start with a single question: who will see this job? If the answer is one name, ask for confirmation. If the answer is vague, the chain is probably long. Asking for a written answer puts that information on the record.

References

Pietrzak, P. & Kornacki, M. (2021). Using CAT Tools in Freelance Translation. Routledge, pp. 78–82.
Pym, A., Grin, F., Sfreddo, C. & Chan, A. L. J. (2012). The Status of the Translation Profession in the European Union. European Commission.
Personal Data Protection Law no. 6698 – mevzuat.gov.tr