Slator.com, the translation industry newsletter, reported on Thursday, 7 September 2017, that translate.com had exposed a massive amount of sensitive data via a “privacy breach” (link).
Translate.com makes use of the Microsoft Translator API, as do many other companies, including Lionbridge. However, the privacy breach has nothing to do with Microsoft or Microsoft Translator or the Microsoft Translator API but instead with the method with which translate.com makes the resulting translations available to its customers. This is not a classic data breach, in which a hacker or disgruntled employee absconds with sensitive data, but instead a breach of privacy that resulted from a poorly designed offering that leaves traces of customers’ translations online.
When Lionbridge MT calls the Microsoft Translator API, all the data is encrypted and the translations, depending on the use case, are either sent directly back to the customer via a secure connection or are brought back into Lionbridge’s highly secure technology stack, where they are saved in a TM for post-editing projects. In no case, does Lionbridge ever store customers’ source material or translations in a way that can be indexed by Google or any other search engine.
Lionbridge takes the security of customers’ data extremely seriously. We have built significant capabilities to ensure that customer data is secure both in transit and at rest. We perform third-party security audits and penetration testing of all our products and regularly participate in customer audits. In addition to baseline data security, we have a fully audited and documented access controls approach that affects everything from application roles and permissions up through physical access to our data centers. The care with which a company treats its customers’ data is indicative of its relationship towards those customers. At Lionbridge, nothing is more important than earning day after day the trust that our customers place in us.
Your content is always secure at Lionbridge.