PRIVACY GUIDE · 4 MIN READ

What privacy-first browser tools can protect

For everyday text cleanup, a browser-based tool can be a sensible default: the input can stay in the browser on your device instead of being sent to a processing server. That is useful, but it is not the same as a guarantee that every part of a task is risk-free.

What local processing means

When a tool performs its work with browser features such as JavaScript, Canvas or Web Crypto, the conversion happens in the page running on your device. ClearText text, hashing and image workbenches are designed around that model. You can often confirm it by using the tool offline after the page has loaded.

What it does not protect automatically

Local processing does not make an unsafe output safe to share. If you paste private data into a message after processing it, the sharing step still has its own risk. A browser extension, a compromised device or an unrelated site open in another tab may have separate permissions and policies. Privacy also depends on the actual version of the site you are using, not only a label on a page.

A safer workflow for copied text

First, remove anything you do not need. Then use the Text redactor to mask common email addresses, telephone numbers and long number strings. Finally, read the output before copying it elsewhere. Automated masking is a convenience layer, not a legal or security review.

Files and images need the same care

Local image tools can resize or compress a file without an upload to a conversion service. That can be helpful for screenshots, blog graphics and drafts. Still check the image for metadata, visible private information and the final resolution before you publish it. The Image workbench keeps those changes in the browser.

Choose tools based on the task

Use a local tool when it can complete the actual task without an account or an unnecessary upload. For a password, use the local password generator and store the result in a trusted password manager. For a checksum, use the SHA-256 generator; remember that a hash verifies a value, while Base64 only represents data as text.

Read the policy for the live site

Tool behaviour and hosting configuration can change. The Privacy Policy explains the site’s stated data handling, and the Cookie Policy covers browser storage and any future advertising technologies. If something appears inconsistent, use the contact page to report it.