If you've ever pasted sensitive data into an online tool…
- pasted a JWT into a random decoder
- formatted JSON with API keys inside
- tested regex on production data
…you’ve probably thought:
“this is probably fine”
But is it?
The uncomfortable truth
Most online tools still work like this:
- You paste your data
- It gets sent to a server
- It gets processed there
And you're just… trusting it.
No idea where it goes.
No idea if it’s logged.
No idea who can access it.
The moment it hit me
I was debugging a JWT with user data inside.
Pasted it into a tool.
Then realized:
I have no idea where this just went.
That was enough.
So I built my own tools
I ended up building a set of dev tools that:
- run entirely in the browser
- don’t upload anything
- don’t track anything
Why this actually matters
This isn’t paranoia.
This is everyday dev stuff:
- tokens
- logs
- internal payloads
- user data
You don’t always control what ends up in your clipboard.
Example
Let’s say you’re:
- decoding a JWT
- formatting JSON
- testing regex
With most tools:
→ your data leaves your device
With ToolDock:
→ everything stays local
Unexpected benefit
It’s not just privacy.
It’s speed.
- no network
- no waiting
- instant feedback
Once you use client-side tools, everything else feels slow.
What’s inside
Right now there are ~90 tools:
- JSON Formatter
- Regex Tester (real-time)
- UUID Generator
- Base64 Encode / Decode
- JWT Decoder
- Timestamp Converter
- Hash Generator
Curious
Do you actually care if tools upload your data?
Or is it “meh as long as it works”?
Top comments (1)
Built this after realizing I had no idea where my data was going 😅
Curious — do you guys actually trust online tools with tokens / logs / JSON?