Translation Manager
Where your content goes
Translation Manager runs inside your Umbraco site. When it translates content, the site sends it straight to the service you configured, with your account and your keys. Your content does not pass through Jumoo.
You choose the translation service and set it up with your own account, and your site talks to it directly. Jumoo never receives your content, your translations or your provider keys. Your keys, translation memory and glossary stay on your site.
Connector by connector
| Connector | Where content goes |
|---|---|
| AI | The AI provider you configure: OpenAI, Azure OpenAI, Azure AI Foundry, Anthropic Claude, Google Gemini, GitHub Models or Ollama. Ollama can run on your own server, in which case content doesn't leave your infrastructure. |
| Umbraco.AI | The connector hands the text to Umbraco.AI on your site, which sends it to the provider set in the AI profile you choose. |
| DeepL | The DeepL API, using your DeepL key. If you use the glossary, it is uploaded to your DeepL account as a DeepL glossary. |
| Google Cloud Translation | The Google Cloud Translation API, using your Google Cloud credentials. Batch jobs also use a Cloud Storage bucket in your own Google Cloud project. |
| Microsoft Translator | The Microsoft Translator endpoint you configure, using your Azure key. |
| XLIFF | Nowhere on its own. Translation Manager writes a file, and you decide who gets it. |
| Passthrough | Nowhere. It copies the source text into the target language on your site. |
Agency and platform connectors
Connectors for translation agencies and platforms, such as Crowdin, Smartcat, LanguageWire, Lionbridge, GlobalLink and Publicis, upload your content to that company's platform so their translators can work on it. That is what those services are for. Your content is then covered by your agreement with that company, not with us. It still doesn't pass through Jumoo.
What Translation Manager sends to Jumoo
Translation Manager contacts Jumoo for three things, and none of them include content:
- Licence check. It sends your licence key to check that it is still valid.
- Update check. It asks whether a newer version is available. The request includes the installed version, whether the site is licensed, and counts of translation sets, sites and languages.
- Connector list. It downloads the list of available connectors shown in the backoffice. You can turn this off by setting
Translation:AddOnPingtofalsein appsettings, and the list then comes from the installed package.
Your own connector
If you write a connector for your own service, content goes wherever your code sends it. See the connector documentation.