Free online tools: which ones keep your data in your browser?
Most of us use small free web tools without thinking twice. We convert a unit, count some words, generate a password or decode a string, then close the tab. But every time you paste text into a web page, it's fair to ask: where does that text actually go?
The honest answer is that it depends on how the tool was built. This guide explains the two main kinds of browser tool, how to tell which one you're using, and some sensible habits for deciding what to paste where. We'll use the free Pocket apps from Transcom as examples, because each one is open about what it does.
Two kinds of web tool
Tools that run in your browser
Modern browsers can do a surprising amount of work on their own. A page loads some code, and from then on the calculations happen on your phone or computer. Your text is processed locally and never needs to travel to anyone else's server. This is often called client-side processing.
It's ideal for jobs like encoding, hashing, converting and generating random values. None of these need outside data, so there's no reason for your input to leave the page.
Tools that need a server
Other jobs can't be done locally. If a tool has to fetch live information, such as weather or prices, or has to store something so you can share it or come back to it later, a server has to be involved. That isn't a bad thing; it's simply how those features work. It does mean you should think a little more carefully about what you put in.
How to tell which kind you're using
You don't need to be a developer to get a good idea. A few practical checks:
- Read the page. Well-made tools tell you plainly. Look for wording such as "runs in your browser" or "nothing is sent anywhere".
- Ask what the tool must do. If it gives you a shareable link, saves something for later or shows live data from elsewhere, it needs a server for at least part of the job.
- Try it offline. Load the page, switch off your connection, then use the tool. If it keeps working, the processing is almost certainly happening locally.
- Peek at the network activity. Most desktop browsers have developer tools with a Network tab. If nothing new appears when you press the button, nothing is being sent.
Pocket apps that say they work in your browser
Several Pocket apps state on the page itself that your input stays on your device. Here's what each one says:
| App | What it does | What the page says |
|---|---|---|
| Cipher | Password and passphrase generator | Nothing is generated on a server, sent anywhere, logged or stored |
| Hash | SHA-1, SHA-256, SHA-384 and SHA-512 fingerprints | Computed with the Web Crypto API; your text never leaves the device |
| Base64 | Base64 encoder and decoder with full Unicode | Everything happens in your browser |
| Convert | Metric, imperial and other unit conversions | Runs entirely in your browser |
| Hue | Colour palette matcher | All maths, no storage; colours never leave the page |
| Ident | Version-4 UUID generator | Made right here in your browser |
These are the tools to reach for when your input is something you'd rather keep to yourself, such as a draft password or a string you're decoding from a work system.
Pocket apps that need a server, and why
Some apps can only do their job by talking to the outside world. That's by design, and the pages are upfront about it.
Apps that fetch live information
- Brolly looks up the weather for a place you type in, asking a Norwegian weather service on your behalf.
- Coin shows live crypto prices from CoinGecko, refreshing about once a minute.
- Daylight gives sunrise and sunset times for a town you search for.
Here, what you send is usually just a place name, which is rarely sensitive.
Apps that store or share things
- Blurt is a pastebin. You paste text and get a link back, kept for one day, one week or with no expiry.
- Done creates a shared checklist. Anyone with the link ticks the same boxes.
- Jot is a private notepad locked with a 6-digit PIN, with a one-time recovery code.
- Gripe is a feedback inbox, where the owner reads messages using a 6-digit PIN.
Saving and sharing are the whole point of these tools, so your content has to be held somewhere.
Sensible habits for what to paste where
A few simple rules will cover most situations:
- Match the tool to the sensitivity. For passwords, keys or anything confidential, use tools that process locally.
- Treat shareable links as public. If a tool gives you a link, assume anyone who gets hold of that link can see the content. Don't put secrets in a pastebin.
- Choose the shortest sensible expiry. If you only need a paste for an afternoon, pick one day rather than never.
- Keep recovery codes safe. PIN-locked tools such as Jot give you a one-time recovery code. Store it somewhere you'll find it later, like a password manager.
- Strip out what you don't need. Sharing a log file? Remove names, email addresses and tokens first. A text diff checker can help you confirm exactly what you changed.
Is in-browser always safe?
Local processing removes one big risk, which is your data sitting on someone else's server. It doesn't make your device itself secure. Browser extensions can sometimes read page content, shared computers can be seen over your shoulder, and anything you copy sits on your clipboard until you copy something else. Keep your browser up to date, be choosy about extensions, and clear the clipboard after handling anything sensitive.
Rule of thumb: if a tool doesn't need to remember or share your text, it shouldn't need to send it anywhere.
Try a tool that stays on your device
If you've landed here because you need a strong password and would rather it never touched a server, Cipher is the place to start. It creates passwords or passphrases from your browser's cryptographic randomness, lets you set the length and character types, and forgets everything when you close the tab.