Traducerea Locală vs Traducerea în Cloud pentru Documente Confidențiale

Cloud translation sends your text to a server, which returns a translation. That is the whole mechanism, and it is not sinister. It is how the best translation quality in the world is delivered.

What varies is everything around it: whether the text is retained, for how long, whether it is used to improve the service, who can access it, which jurisdiction it sits in, and whether a business agreement changes any of that. Consumer free tiers and paid enterprise tiers of the same product often differ substantially on exactly these points.

The honest summary is that reputable providers are not doing anything reckless with your paragraph. The problem is narrower and more practical: you may not have had the right to send it in the first place.

Being clear about this, because a post that says "never use the cloud" is not useful to anyone.

Published or public material. Marketing copy, a website, a press release, documentation you are about to publish anyway. The text is going public. There is nothing to protect.

Your own low-stakes text. A message to a hotel, a recipe, a menu, a forum post.

Anything where quality is the binding constraint. Idiom, humour, marketing that has to persuade, poetry, or an unusual language pair. The largest cloud systems are genuinely better here, and pretending otherwise does readers a disservice.

When you have an enterprise agreement. Many providers offer terms with no retention and no training use, backed by a contract. If your organisation has one, much of this discussion is already settled, and you should use the tool your legal team approved.

Cloud translation is not the villain. Using a consumer text box for material that belongs to somebody else is the problem, and it is a habit rather than a decision.

Yaps

Client material under a duty of confidence. Legal, medical, financial, social work, therapy, HR. If you would not forward the document to a stranger, a text box does not change that.

Anything under NDA. Unreleased products, draft agreements, acquisition documents, unpublished manuscripts.

Personal data about other people. A translated witness statement, a patient letter, or a staff grievance contains someone else's information, and they are not in the room to consent.

Anything where you would struggle to answer "where did this text go?" That is the practical test. If a regulator, a client, or your own security team asked, would you have a comfortable answer?

The difference is not that local is more secure in some abstract sense. It is that there is no transfer at all, which removes a whole category of question rather than answering it.

No processor to add to a register. No retention period to check. No jurisdiction question. No sub-processor list to review. No annual re-assessment when the provider updates its terms. Nothing to disclose to a client, because nothing was disclosed.

That is a materially simpler position than having read a privacy policy carefully and concluded it was probably fine.

Yaps translates on your own computer, in the desktop app on macOS, Windows and Linux. It is not part of the mobile app.

It translates a note, a selected paragraph, or a file, and the file types are Markdown (.md), plain text (.txt) and SRT subtitle files (.srt). Word documents, PDFs and slide decks are not accepted directly; if your source is a PDF, convert it to text first.

You download a language pack once for the pair you need, and after that it works with no connection and no cost per word. Some pairs need an additional model downloaded before they become available, so check yours before building a process around it.

The fuller picture is in our guide to offline translation, and if your job is subtitles specifically, translating an SRT without breaking the timing is its own problem worth reading about.

Rules only work if they survive being in a hurry. This one is short enough to remember.

Ask one question: is this text mine to send? If it is yours, or already public, use whatever produces the best translation. If it belongs to a client, a patient, an employer, or another person, translate it locally.

Set the default at the tool level, not the willpower level. If confidential work is common for you, having a local translator already installed is what makes the right choice the easy one at 4pm on a Friday.

Machine output is a first draft, either way. This is true of local and cloud alike. For anything being signed, filed, or published, a qualified human translator does the final work. Certified translation is a formal process that no software output satisfies.

Is it safe to translate confidential documents with Google Translate?

Pasting text into a consumer translation service is a transfer to a third party, whatever the provider's policy says. For your own low-stakes text that is fine. For client material, patient information, or anything under NDA, it is a disclosure you may not be authorised to make, and the interface gives you no signal that you just made it. Enterprise agreements with no-retention terms change this materially, so check whether your organisation has one.

What is the difference between local and cloud translation?

Cloud translation sends your text to a server and returns a result. Local translation runs the model on your own computer, so the text never leaves it. Cloud is generally better on idiom, nuance and unusual language pairs. Local removes the transfer question entirely and has no cost per word.

Does local translation mean my data is more secure?

It means there is no transfer to secure. That is a different and simpler claim than being more secure in the abstract. Your own machine still needs the usual protections, but you no longer have a third party in the chain to assess, log, or explain to a client.

Is machine translation GDPR compliant?

That depends entirely on the provider's terms, your lawful basis, and your own obligations, and it is a question for your legal team rather than a blog post. What can be said plainly is that translating locally avoids the transfer that triggers most of those questions, which is why it is a simpler position to defend.

Can I use cloud translation if I have an enterprise agreement?

Often yes, and that is usually the intended path. Enterprise tiers commonly offer no retention and no training use, backed by contract. If your organisation has negotiated terms, use the approved tool. This discussion is mainly about the consumer free tiers that people reach for out of habit.

Which is more accurate, local or cloud translation?

Cloud, generally, particularly on idiom, humour, poetry, marketing copy and unusual language pairs. Local translation is good enough for understanding a document and for working drafts. The trade is some quality on hard passages in exchange for the text never leaving your computer.

What file types can Yaps translate locally?

Markdown (.md), plain text (.txt) and SRT subtitle files (.srt), plus notes and selected passages inside the app. Word documents, PDFs, spreadsheets and slide decks are not accepted directly. Convert a PDF to text first if that is your source.

Does Yaps translation work offline?

Yes, once the language pack is downloaded. That first download needs a connection. Everything after it runs on your machine, including with no connection at all.

Does Yaps translate on iPhone or Android?

No. Translation is a desktop feature, in the Yaps app for macOS, Windows and Linux.

Should I translate a contract with software at all?

For understanding what a contract says, machine translation is genuinely useful and translating it locally avoids disclosing it. For a contract that will be signed, relied upon, or filed, you need a qualified human translator. Machine output is a first draft in both cases, and certified translation is a formal process no software satisfies.

How do I stop my team pasting client documents into web translators?

Make the right option the easy one. People reach for the text box because it is there and it is instant, not because they decided to. Installing a local translator, and giving one short rule ("if the text is not ours, translate it locally"), works better than a policy nobody reads at four in the afternoon.

Does local translation cost anything per word?

No. There is no metering, no API key and no per-character billing, which quietly changes behaviour: you translate the whole document rather than only the paragraph you decided was worth paying for.

What should I always check in any machine translation?

Proper nouns, which get translated when they should be left alone; numbers and decimal separators, since a comma becoming a full stop changes a figure enormously; and formality, because many languages distinguish formal and informal address and the machine simply picks one. For anything that matters, have someone who reads the target language look at the result.