How Your Text Is Processed

Processing happens in your browser

When you open a tool page, the server sends static files: HTML, CSS and a small JavaScript bundle. From then on, every count, conversion, sort and normalization is done by those JavaScript functions inside your browser tab. Your text is held in the page’s memory only while you use it.

No request containing your text is ever made. There is no API, no database and no server-side code that could receive it.

Copy, download and reset

The action buttons also work locally.

• Copy uses your browser’s Clipboard API to place the result on your clipboard.
• Download creates a .txt file on your device from the result using a Blob; the file is generated in the browser, not on a server.
• Reset clears the input and the result on the page.

What happens when you leave

Closing the tab or reloading the page clears your text. The site stores only your light or dark theme choice and analytics consent choice in localStorage. Google Analytics and SearchBastion load only after you consent; Google Analytics may then set cookies and SearchBastion creates a random identifier in sessionStorage.

How to verify it yourself

You do not have to take our word for it. You can check the behaviour with standard browser features.

• Open your browser’s Developer Tools, go to the Network tab, then type or paste text into a tool. No new requests are sent while you work.
• Load a tool page, disconnect from the internet, and keep using it. The tool continues to work because it does not depend on a server.