Does Text Mechanic Upload or Store the Text I Paste Into Its Tools?

Updated

No. According to Text Mechanic's own site description, its tools are "100% client-side — your text never leaves your browser." The text you paste is processed by JavaScript running in your browser tab, not sent to a Text Mechanic server for processing. That said, "client-side processing" and "no storage" are not identical claims, and the site's visible materials don't spell out a retention policy for pasted content. Treat the tools as low-risk for ordinary text, and avoid pasting secrets, credentials, or regulated data you wouldn't put into any third-party web page.

What the site actually says

The homepage describes Text Mechanic as "Simple, single task, browser based, text manipulation tools," and the site's own summary states the tools are free, browser-based, and 100% client-side. The practical meaning: when you use a tool like Remove Duplicate Lines or Find and Replace Text, the transformation happens locally in your browser.

The site also lists a Privacy Policy page, but the excerpt available here doesn't include its contents. So the strongest supported statement is about where processing happens (your browser), not a blanket guarantee about every possible form of data handling.

Why client-side matters for your decision

Question What client-side processing implies
Is my text sent to a server to be transformed? No — the tool logic runs in your browser
Can the operator read my text from server logs? Not from the tool's processing step, per the site's claim
Is my text saved anywhere by the tool? Not stated in the available materials; don't assume either way
Is the page itself free of tracking? Not established by the materials here

The distinction matters because "your text never leaves your browser" is a claim about transmission during processing. It doesn't automatically cover things like browser extensions you have installed, your own clipboard history, or account features if you log in.

A practical example

Suppose you have a 2,000-line CSV export and need to pull one column. You paste it into the Delimited Column Extractor, set the delimiter, and copy the result. Under the client-side model, the column extraction runs in your tab — the pasted CSV isn't shipped to a backend to be parsed. That's the scenario the site's claim is designed to address.

Now suppose the same file contains customer email addresses or API keys. The processing may still be local, but you're relying on a third-party page's JavaScript, your browser's integrity, and whatever else is loaded on that page. For that kind of content, a local script or a desktop tool you control is the safer default.

How to reduce risk when using it

  • Paste only what the task needs. Extract or trim the relevant lines before pasting rather than dropping an entire document.
  • Strip identifiers first. Replace names, account numbers, and keys with placeholders, run the transformation, then restore them locally.
  • Check for a login prompt. The site shows Login/Signup and a "TextMechanic Pro" upsell with a free-task limit ("Limit of 4 free tasks per hour exceeded"). If you create an account, assume account-related data is handled server-side and read the Privacy Policy before signing up.
  • Verify the output. These are single-task tools; spot-check a few lines against your source before using results in anything important.
  • Prefer offline alternatives for sensitive work. A short script, a spreadsheet formula, or your editor's built-in find-and-replace keeps the data entirely on your machine.

Bottom line

For everyday text cleanup — deduplicating lines, changing case, counting words, extracting a column — Text Mechanic's client-side design is a reasonable fit, and the site explicitly says your text doesn't leave the browser during processing. For confidential or regulated content, the claim is reassuring but not a substitute for controlling the data yourself; use a local method instead.