We Can't See What You Paste — And That Was a Design Constraint, Not a Slogan
We can't see what you paste. No logging. No uploading. Just your browser. That's not marketing copy I wrote after the fact — it's a description of how FormatStack is actually built. Every tool ( JSON formatter , regex tester , UUID generator , Base64 encoder , cron parser ) runs entirely client-side. When you paste something in, it never leaves the tab. There's no fetch(), no API route, no server…
The phrase "We can't see what you paste" isn't just marketing jargon for FormatStack. It's a genuine architectural feature. Every tool on the platform - the JSON formatter, regex tester, UUID generator, Base64 encoder, and cron parser - runs entirely in the user's browser. When you input data, it's processed in your browser's JavaScript engine, and it never leaves the tab.
There's no fetch() request, no API route, and no server that ever receives the data. This is because there simply isn't a server in the request path at all. The "we can't see what you paste" claim applies directly to the processing, parsing, formatting, and encoding of your input. It's an architectural fact, not a policy that could be quietly changed later.
There's no backend endpoint to add logging to, even if the developers wanted to. FormatStack is live at formatstack.tech.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
