At Unbabel, we take your privacy very seriously, and we don’t make use of customer sensitive data of any kind. That’s why we developed an Anonymisation step which automatically removes sensitive, personally-identifiable data before it’s dispatched to our network of Unbabelers. Credit Card and Social Security numbers, URLs, dates, email addresses and others are all stripped out and replaced by an anonymised term placeholder with the type of content that it hides, giving context to our editors while ensuring that private data is never at risk.

 

While this is an automatic process, we have also developed an additional feature that allows agents to manually select portions of text that will remain untranslated, be it for security or branding reasons, or use of templates or foreign terms. This is the no-translate feature.

 

No translate will work with two variants:

 

Simply add <<<>>> around the text while writing your message in the email composer. eg:  <<<hidden text goes here>>> (note: the bold formatting doesn't need to be used).

 

This text will not be translated by our editors and your customer will receive it without the brackets. The content will still be visible to the editors, who will be fully aware of the context that excerpt adds to the message.

 

 

• You can select an excerpt of text that will be completely hidden from our editors

 In this case you will need to add <<!!>> around the text you wish to hide, directly on the internal note you are composing. eg:  <<! hidden text goes here !>>

 

In this case the excerpt will be completely removed from any interface visible to our editors, who will learn of the text missing but never have access to it.

 

Invalid usage of no-translate

 

On occasion, you may submit a message which HTML content prevents the no-translate feature from working properly, breaking the logic and, more importantly, preventing the message from reaching our pipeline and resulting in any translation.

 

Whenever the message contains invalid syntax, an error stating "The message posted contains a "no-translate" syntax error." will appear above the email composer. To work your way around it, please read this dedicated article.

 

Precautions

 

Although no-translate can prove useful in many cases, it also has the potential downside of depriving editors from information often important to provide context and information essential to determining gender, number, etc, or proving difficult to move in the sentence to ensure grammatical sense. Therefore, we recommend that whenever the feature is used, the remainder of the text is descriptive enough that important this information can be derived from it, along with all possible text. It is also a good idea to isolate the hidden terms whenever possible, as exemplified next:

 

❌ Hello again. Using code <<<1234>>> you can find your order. 

 ✔️ Hello Maria. By using the following order code

<<<1234>>>

You will be able to find your order in the website.