Microsoft

API and Hub: Confidentiality

Microsoft Translator Text API:
Microsoft does not share the data you submit for translation with anybody. Microsoft does not take any samples of any text submitted for translation using the Translator Text API. More information is outlined in the No-Trace webpage.

Microsoft Translator Hub:
The material you use for training on the Translator Hub is stored encrypted in your workspace. You may invite whoever you like into the workspace, identified by an email address and authenticated with a Microsoft Account. The people you designate as co-owner have access to your training material and training runs the same way you have. Microsoft will not share the data with anyone else. You can delete the data in your workspace at any time, as long as it is not used in any training. Microsoft will use the data that you include in a training to build the custom translation system for you. The custom translation system will be deployed on Microsoft's servers, and are then usable via the Microsoft Translator API. Anyone who knows the category ID of your custom system can use it using their own Microsoft Translator Text API subscription account. There is no method allowing you or anyone else to generate the original training material out of the trained system. Microsoft may use the data in your workspace to improve Microsoft Translator only if the "Keep data private" box in the Settings tab on the Translator Hub is unchecked.

Copyright and Intellectual Property:
Translation, or use of a document for training on the Microsoft Translator Hub, does not alter the ownership of the intellectual property contained therein. 

Last update: March 9, 2017

Translator

  1. Announcement: Changes to the Collaborative Translation functions
  2. Translator Hub replaces the Collaborative Translation Framework (CTF)
  3. Microsoft Translator Moves to the Azure portal
  4. API - Translator datacenters
  5. API and Hub: Confidentiality
  6. API - Translator Speech: Microsoft Translator Speech API references
  7. API - Translator Text: How to report an issue with the API
  8. API - Translator Text / Speech: Microsoft Translator with IP filtered firewalls
  9. API - Translator Text / Speech: Get a report of your consumption
  10. API - Translator Text / Speech: Using the API key directly in the call. No more token.
  11. API - Translator Text / Speech: Why are there two keys for my API subscription?
  12. API - Translator Text: Hybrid Neural Machine Translation
  13. API - Translator Text: Using Neural MT Systems
  14. API- Translator Text: Standard category languages
  15. API - Translator Text: My CAT tool isn't working and is asking for the Client ID and Client Secret
  16. API - Translator Text: Limits
  17. API - Translator Text: How Microsoft Translator counts characters
  18. API - Translator Text: Gender selection in the Speak() method
  19. API - Translator Text: Trados plugin for Microsoft Translator
  20. API - Translator Text: Java- Using SSL with the Microsoft Translator API
  21. API - Translator Text: European datacenter
  22. API - Translator Text: Languages detected by the Detect() method
  23. API - Translator Text: First few Microsoft Translator API requests succeed, then the calls fail
  24. API - Translator Text: Profanity filtering in the TranslateArray() method
  25. API - Translator Speech: Signal the end of the utterance
  26. Hub: API available
  27. Hub: Translator Hub Resource Guide
  28. Hub: August 2016 Release notes
  29. Hub: Deployment of a custom system requires a Microsoft Translator Text API subscription in the Azure portal
  30. Hub: Capacity of custom Microsoft Translator Hub systems
  31. Hub: Building a custom system using a dictionary only
  32. Business Applications: Security and Privacy in Microsoft Office Products

Feedback and Knowledge Base