MTX Translator
This policy explains what MTX processes, where data goes, what stays on your device, and the choices you have when using webpage, selected-text, and subtitle translation.
Short version: MTX does not operate a backend that collects or stores your webpage content, translated text, browsing history, or provider credentials. Translation text is processed by the extension and, when you choose a remote translation provider, is sent directly to that provider to perform the translation. Provider credentials are stored locally in your browser. MTX does not sell user data, use it for advertising, create browsing profiles, or use it for credit or lending decisions.
Contents
1. Data processed by the extension
The extension processes only the data needed to provide translation and related features. The MTX developer does not operate a backend that receives or stores this translation data.
Website content
The extension reads webpage text, text you select, and supported subtitle or caption content only when needed to provide translation, bilingual display, subtitle translation, or synchronization. MTX does not send this content to an MTX-operated backend. When a remote provider is used, the required text is sent directly to that provider.
Provider credentials
If you configure a translation provider that requires an API key or similar credential, the credential is stored locally in browser extension storage and used only to authenticate requests to the provider you configured. The MTX developer does not receive or maintain a copy of your provider credentials.
Settings and preferences
The MTX extension stores your language preferences, display mode, provider settings, site/privacy preferences, and other extension configuration locally so your choices persist between browser sessions.
Data not collected by the MTX developer
The MTX developer does not operate a service designed to collect your name, postal address, health information, financial information, precise location, personal communications, or a list of websites you have visited.
2. How translation data flows
The current version of MTX is designed so translation requests are sent directly from the extension to the translation provider you choose, rather than through an MTX-operated translation backend.
- Remote provider: the text required for translation is sent to the provider endpoint used for that request.
- User-configured provider: requests are sent to the provider origin you explicitly configure and authorize.
- Local provider, where supported: translation may remain on your own device or local network, depending on how that provider is configured.
- Supported video subtitles: MTX may access subtitle/caption data needed for translation and synchronization on supported YouTube and Udemy pages.
3. Local storage and retention
The MTX extension stores settings locally in browser extension storage so your configuration persists. User-configured API keys are stored locally and are used by the extension background context only when making requests to the configured provider.
Important: local browser storage is not an encrypted password vault. You should protect your device and provider credentials accordingly.
Local settings remain until you change or clear them, clear extension storage, or uninstall MTX. The MTX developer does not maintain a separate backend or database containing your translated webpage text or provider API keys.
4. Third-party translation providers
When you choose a remote provider, that provider receives the text needed to perform the translation. A provider that requires authentication may also receive the credential necessary to authorize the request.
Third-party providers operate under their own privacy, security, logging, and retention practices. MTX does not control those practices. Before using a provider, review that provider's terms and privacy policy.
MTX does not sell your webpage content or API keys to translation providers. Any direct transfer from the extension to a provider is solely for performing the translation or authenticating the request you initiated.
5. Browser permissions
MTX requests browser permissions only to support its translation features.
storage
Saves language preferences, display settings, provider configuration, and other extension settings.
activeTab
Provides temporary access to the current tab after you invoke MTX so requested content can be translated.
scripting
Runs MTX's packaged scripts needed to detect translatable content and display translations on the page.
contextMenus & sidePanel
Provide selected-text translation entry points and display translation results and controls.
Host access
MTX uses host access for translation provider endpoints and supported subtitle features. For user-configured remote providers, optional HTTPS host access is requested for the specific provider origin you explicitly configure and authorize.
6. Your choices and deletion
- You choose when to invoke webpage or selected-text translation.
- You choose which translation provider to use.
- You can remove or change a user-configured provider and its saved credential.
- You can clear MTX settings using the extension's controls or by clearing extension storage.
- Uninstalling MTX removes the extension and its local extension storage from your browser profile.
7. Security
MTX is designed to keep provider credentials isolated from ordinary webpage scripts and to use them only from the extension context needed to make provider requests. MTX does not download and execute remote JavaScript or WebAssembly as part of its translation logic.
No software can guarantee absolute security. Keep your browser, device, and provider credentials protected, and revoke or rotate a provider key if you believe it has been exposed.
8. What MTX does not do
- MTX does not sell user data.
- MTX does not use webpage content or provider credentials for advertising.
- MTX does not create a browsing-history profile of the sites you visit.
- MTX does not use or transfer user data to determine creditworthiness or for lending purposes.
- MTX does not use user data for purposes unrelated to its translation functionality.
9. Contact and policy changes
For privacy questions, please use the developer contact or support information shown on the official Chrome Web Store listing for MTX Translator.
This policy may be updated when MTX's features, providers, or data practices change. The effective date at the top of this page will be updated when a revised policy is published.
This privacy-policy website itself is built as a static page and does not include advertising, analytics scripts, or tracking cookies.