· 5 min read
The text people clean is rarely public. It is an unpublished draft, a client email, a cover letter, a contract clause, or internal documentation. Whether pasting it somewhere is safe depends on one thing: whether the tool sends it to a server.
Both present a box, a button and a result. One posts your text to a machine you do not control; the other transforms it with JavaScript already running in your tab. Nothing on the page tells you which you are using.
A promise to delete after an hour may be entirely sincere, and it still depends on retention behaving as described, backups expiring, and request logs not capturing the body separately. A tool that never receives your text has nothing to delete and nothing to get wrong. That is a different kind of assurance rather than a stronger promise.
Every tool here runs in the browser. The text is transformed in the tab and never transmitted, which is verifiable with the offline test above rather than something you have to believe.
For published text that anyone can already read, it genuinely does not matter. For anything unpublished, confidential, or belonging to a client, use a tool that works offline and confirm once that it does.
Related: How to extract email addresses from a block of text
Load the page, go offline, and use it. If it still works, the code is in your browser. If it fails, it was sending your text somewhere.
No imposed limit. Because the work happens in memory, very long documents are bounded by your device.
No. It is never transmitted, so there is nothing on our side to keep.