Review External Translation Services

Identify external services used by TranslateSense.

TranslateSense supports cloud translation through OpenAI and Google Gemini. The plugin can also use WordPress AI Connectors when compatible connector APIs and provider plugins are available, and it includes a separate browser-based on-device translation provider.

External cloud services

  • OpenAI API: the readme identifies api.openai.com/v1/chat/completions as the endpoint used for translation requests. Review the OpenAI Terms of Use and OpenAI Privacy Policy.
  • Google Gemini API: the readme identifies the Generative Language API endpoint under generativelanguage.googleapis.com/v1beta/models/. Review Google’s Terms of Service and Privacy Policy.

WordPress AI Connectors

When TranslateSense detects a compatible WordPress AI Connector for a provider, the settings interface can display its connection and activation status and a link to manage it in WordPress Connectors. In this configuration, provider credentials are managed by the connector rather than the direct API key field in TranslateSense. Connector availability depends on the installed WordPress version, APIs, and provider plugin.

Browser-based on-device service

Chrome Built-in AI uses supported on-device translation APIs in Google Chrome and Microsoft Edge. The implementation checks for a secure context and supported language pairs. Browser model or language-pack availability may affect whether a translation can run. See Use Built-in AI Translation for setup and limitations.

Identify the service in use

  1. Open the TranslateSense settings screen.
  2. Review Default Engine and the enabled provider switches.
  3. Check whether OpenAI or Gemini uses direct API credentials or a WordPress AI Connector.
  4. For browser-based translation, verify that Chrome Built-in AI is enabled and selected in the relevant translation workflow.
  5. Review the data-sharing guidance before translating sensitive content.

Screenshot to add: [External translation service options]