Privacy education · November 6, 2026
Before You Translate a Private Page
A practical guide to browser translation, where page text is processed, selected-text choices, and automatic language preferences.
A translation button can make an unfamiliar page easier to read. Before using it on private material, check what the feature translates, where that processing happens, and whether a saved preference will apply to later pages. Those choices deserve the same attention as the words you want to understand.
The important distinction is the particular translation feature you are using. A browser's built-in page translator, a separate website, and an installed extension should each be reviewed through their own current documentation.
Find out where the text is processed
Mozilla's Firefox translation guide says its built-in translations happen on the device rather than sending the text to cloud servers. Required language files can download as needed. After the necessary files are installed, supported content can also be translated without an internet connection.
Keep that statement tied to the documented translation feature. It should not become a conclusion about every other action a page or browser performs. Check whether your language combination and current browser version are supported before relying on a particular workflow.
For a different example, Microsoft's webpage-translation privacy documentation says Edge sends the text to be translated, the source and destination languages, and a service token to Microsoft Translator over HTTPS. It also describes storing text for service improvement after removing identifiers. The documentation links to its privacy statement. Read those terms when deciding whether the feature fits the material.
Choose the content deliberately
Before translating, identify what you need to understand. Is it a word, a paragraph, or the page as a whole? Review the material in that scope, including any private information about other people. Being able to read a page does not by itself settle whether sending its contents to another service is appropriate.
Where a tool supports translating selected text, consider whether that is enough for the task. Inspect the selection before invoking the command and check the tool's explanation of how it handles the content. A smaller visible selection should not substitute for understanding the feature's actual behavior.
On an organizational device or with work material, use the approved translation process. If the intended handling is unclear, ask the responsible person before experimenting with a private page. Public, nonsensitive text is a more suitable starting point for learning the interface.
Review automatic language choices
Google's desktop Chrome instructions place translation controls in Settings under Languages. They describe a list of automatically translated languages and a separate list of languages for which Chrome should never offer translation. The guide also documents translating a selected section of a page.
Review existing entries as well as the current page's prompt. A language-wide choice may apply across different subjects and websites. Decide whether that convenience still matches how you use the browser, especially if the same language appears in both public reading and private work.
Record the scope of a change you make: the affected language, the relevant feature, and whether you changed an automatic preference or requested one translation. This can help you revisit the decision without preserving the private text itself.
Understand what returning to the original does
Microsoft's Edge translation instructions document Show original for returning a translated page to its original language. They also explain how an Always translate choice can apply to a source language and where translation preferences can be managed.
Treat the display action according to that description. Returning to the original wording should not be taken as evidence that a prior processing request has been recalled or that a provider's records have been deleted. Questions about data handling require the feature's privacy documentation.
Keep the review practical
Try the documented controls with a public page before using them with private material. Check the source and destination languages, the selected content, and the resulting preference. A successful translation demonstrates the interface working; it does not establish everything about the processing behind it.
Revisit the arrangement when you change tools, add an extension, or move to another device. A useful translation routine is one you can explain: what you chose to translate, which feature handled it, where processing occurs, and whether the choice continues automatically.