API and Hub: Confidentiality

Microsoft Translator API:
Microsoft does not share the data you submit for translation with anybody. Any sampling taken will be used exclusively to improve Microsoft Translator, or deleted within 30 days. Microsoft Translator takes a sampling of at most 10% of unrelated, non-consecutive sentences. If you are concerned about the potential of samples being stored, and you are subscribed to the Microsoft Translator Text API with a monthly volume of 250M characters or more, you can opt out of any sampling. Just let us know the resource ID of your subscription by submitting a request using the process detailed at www.microsoft.com/translator/notrace.aspx , and we'll exclude the content of your requests from ever being written to non-volatile storage.

Microsoft Translator Hub:
The material you use for training on the 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 API 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, unless you have a paid API account, and check the "Keep data private" box in the Settings tab on the Hub.

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

Last update: June 28, 2017


  1. Announcements: Microsoft Translator Moves to the Azure portal
  2. API - Translator Text: How to report an issue with the API
  3. API and Hub: Confidentiality
  4. API - Translator Speech: Microsoft Translator Speech API references
  5. API - Translator Text / Speech: Get a report of your consumption
  6. API - Translator Text / Speech: Why are there two keys for my API subscription?
  7. API - Translator Text: My CAT tool isn't working and is asking for the Client ID and Client Secret
  8. API - Translator Text: Limits
  9. API - Translator Text: How Microsoft Translator counts characters
  10. API - Translator Text: Gender selection in the Speak() method
  11. API - Translator Text: Trados plugin for Microsoft Translator
  12. API - Translator Text: Java- Using SSL with the Microsoft Translator API
  13. API - Translator Text: European datacenter
  14. API - Translator Text: Languages detected by the Detect() method
  15. API - Translator Text: First few Microsoft Translator API requests succeed, then the calls fail
  16. API - Translator Text: Microsoft Translator with IP filtered firewalls
  17. API - Translator Text: Profanity filtering in the TranslateArray() method
  18. Hub: API Preview released
  19. Hub: Translator Hub Resource Guide
  20. Hub: August 2016 Release notes
  21. Hub: Deployment of a custom system requires a Microsoft Translator Text API subscription in the Azure portal
  22. Hub: Capacity of custom Microsoft Translator Hub systems
  23. Hub: Building a custom system using a dictionary only
  24. Hub: Deployment of a custom system requires a Microsoft Translator subscription in the Azure portal

Feedback and Knowledge Base