
KOZ Static Translate scans published WordPress content, stores translation segments in plugin-owned tables, processes them through Azure Translator and serves completed language routes without changing the original posts.
Azure usage stays within a monthly limit and a daily budget, is shown by source, and is never triggered by visitors or search engine crawlers. Text that Azure translated but validation rejected is not paid for twice.
The plugin preserves the proven database schema, queue, cron hooks, public URLs and stored Azure settings from the former UA FREE package. It also supports dynamic content added after page load, a floating language selector, a language sitemap and controlled cleanup of legacy translator leftovers.
The plugin was originally developed for the UA FREE charitable foundation website, which remains its primary production environment. The software is independently owned and maintained by Tony Kozyriev (ramirkz).
KOZ Static Translate is one focused module of the broader KOZ Suite, a family of independent WordPress plugins that share a common KOZ administration experience and visual identity.
Each KOZ plugin remains independently installable, so site owners can use only the modules they need or combine several modules into one toolkit.
Current public KOZ plugins:
The complete human-readable source for this plugin is included in the plugin package and is maintained publicly at:
https://github.com/ramirkoz/ua-free-plugins/tree/main/koz-static-translate
The JavaScript files in assets/ are shipped as human-readable source files. No npm, webpack or other build step is required to regenerate the distributed JavaScript.
The plugin does not add analytics or advertising telemetry. Content selected for translation is sent to the configured Azure Translator endpoint. Azure credentials are encrypted in the WordPress database using keys derived from WordPress salts.
KOZ Static Translate optionally uses Microsoft Azure Translator when the site administrator configures Azure Translator credentials and enables translation processing.
When translation processing runs, text segments selected from published WordPress content are sent to the configured Azure Translator endpoint so Microsoft can return translated text. The plugin does not send visitor analytics or advertising telemetry to the developer. Azure Translator credentials are stored in the WordPress database in encrypted form using keys derived from WordPress salts.
The external service is not required for WordPress administration, cleanup tools, translation-memory storage, language routing logic or KOZ Suite navigation, but new machine translations cannot be produced without a configured translation provider.
Service provider: Microsoft Azure Translator / Azure AI Translator.
Default API endpoint: https://api.cognitive.microsofttranslator.com
What is sent: only text segments selected for translation, together with the source and target language codes required by the Translator API. Site visitor analytics, advertising identifiers and WordPress user passwords are not sent by this plugin.
When it is sent: only when an authorized site administrator runs a queue step or the connection test, when an administrator-only dynamic translation request is made, or when the administrator has enabled the optional background worker. Page views by visitors or search engines never send text to Azure. Every request is limited by the configured daily and monthly character budget.
Why it is sent: to receive machine-translated text that is stored in the site’s translation memory and translation tables.
Azure Translator product information:
https://azure.microsoft.com/products/ai-services/ai-translator/
Azure Translator data, privacy and security information:
https://learn.microsoft.com/en-us/azure/foundry/responsible-ai/translator/data-privacy-security
Microsoft Privacy Statement:
https://privacy.microsoft.com/en-us/privacystatement
Microsoft Product Terms for Azure services:
https://www.microsoft.com/licensing/terms/productoffering/MicrosoftAzureServices/MCA