BPC AI Translator

BPC AI Translator helps WordPress administrators manage multilingual content from inside WordPress. It stores language settings, translation records, review status, URL mapping and language switcher configuration locally in the site database.

The plugin can work as a local multilingual management layer, and it can also request AI translations when an administrator deliberately configures a supported provider API key. Provider keys are stored in the WordPress installation and are used only for the selected provider actions.

Main features

• Manage source and target languages, including locale, URL slug, active status, source language, default language and indexable status.
• Store translations locally with source text, translated text, source locale, target locale, origin and review status.
• Review, publish, lock, import, export and filter translation records from the WordPress admin.
• Configure translated URLs with prefix, subdomain or mapped-domain strategies, depending on your hosting setup.
• Add language switchers with shortcode, widget, block, menu integration or floating frontend switcher.
• Generate hreflang metadata for active, indexable languages.
• Configure optional AI providers with your own API keys: OpenAI, Anthropic, xAI, Google Gemini and DeepL.
• Distinguish a saved provider key from a connection that has actually been tested.
• Cache translation results and keep translation logs with configurable retention.
• Exclude known bots from browser-language redirection to protect indexing behavior.

Important operating facts:

• A saved API key is stored encrypted locally when the server supports the required encryption setup.
• A provider connection is described as verified only after a real connection test succeeds.
• Translation requests can incur charges billed directly by the selected provider.
• The plugin does not provide a managed credit wallet.
• PHP extensions mbstring and openssl are required.

Privacy and data handling

The plugin stores translation data in the local WordPress database. External translation requests are not sent until an administrator configures a provider key and runs a provider test or translation action.

When an AI translation action is used, the selected provider can receive the source text, target language, optional context and model settings needed to perform the translation. Review the terms and privacy policy of each provider before enabling it.

Review-first workflow

BPC AI Translator is designed for reviewed publishing. Generated or imported translations can be kept as drafts, marked as needing review, reviewed, published, locked or marked obsolete depending on the site workflow and user permissions.

External services

This plugin can send content to third-party API services only after an administrator configures a provider key and performs a test or translation action. Depending on the action, submitted data can include source text, target language, optional translation context, and the selected model. The administrator is responsible for reviewing provider terms and privacy policies before enabling a provider.

• OpenAI API: translation requests may be sent to https://api.openai.com/. Terms: https://openai.com/policies/terms-of-use/ Privacy: https://openai.com/policies/privacy-policy/
• Anthropic API: translation requests may be sent to https://api.anthropic.com/. Terms: https://www.anthropic.com/legal/commercial-terms Privacy: https://www.anthropic.com/legal/privacy
• xAI API: translation requests may be sent to https://api.x.ai/. Terms: https://x.ai/legal/terms-of-service Privacy: https://x.ai/legal/privacy-policy
• Google Gemini API: translation requests may be sent to https://generativelanguage.googleapis.com/. Terms: https://ai.google.dev/gemini-api/terms Privacy: https://policies.google.com/privacy
• DeepL API: translation requests may be sent to https://api-free.deepl.com/ or https://api.deepl.com/, according to the configured plan. Terms: https://www.deepl.com/en/pro-license Privacy: https://www.deepl.com/en/privacy

API keys remain in the local WordPress installation and are transmitted only to the configured provider as required for authenticated requests.