Trust Center

Your data never leaves your browser.

All 76 jsonversal tools run entirely on your device. We have no server that receives your input and no accounts. Paste an API key, a .env file, or a production payload — it stays on your machine, and never reaches us or our ad partner.

🔒 Zero upload 👤 No account 📡 Ad partner sees no tool data

How it works

Browser-only by architecture

Your input is processed by JavaScript running in the page. The result is rendered back to you. There is no step where the data is transmitted anywhere.

Your browser

→

jsonversal engine Web Crypto · File API · pure JS

→

Output in your tab

↳ no network request is ever made with your data

Your browser

→ POST /format →

Their server + database

↳ a server-side tool transmits and often stores your input — the failure mode behind the 2025 formatter leak (read the breakdown →)

What we don't do

The things a "free" tool usually takes from you

🚫

No upload

Your text, files, and secrets are processed locally. Nothing is sent to our infrastructure.

🙅

No account

There is no sign-up, no profile, and no user ID. We cannot link activity to a person.

🍪

No analytics of our own

We run no first-party analytics and set no first-party cookies. Our ad partner uses its own cookies, opt-outable as described in the Privacy Policy.

🌐

Self-hosted assets

Fonts and libraries are served from this domain, not a public CDN. The only third-party request at runtime is the ad script — it never receives your tool input.

Prove it yourself

Verify any tool in 10 seconds

You do not have to take our word for it. This test is definitive and works on any developer tool.

Open DevTools. Press F12 (Windows/Linux) or Cmd+Option+I (macOS).
Open the Network tab and press the clear button (⊘).
Trigger the tool — paste input and click Format / Encode / Generate / etc.
Watch the requests. On a client-side tool like ours, nothing new appears. If a POST or GET carrying your input shows up, that tool sent your data to a server.

Why it matters

The data people actually paste into formatters

API keys & secrets — AWS / Stripe / GitHub tokens pasted to debug a response.
.env files — full environment configs with database URLs and passwords.
JWTs & OAuth tokens — production session credentials.
Private keys — SSH, RSA, or X.509 keys being inspected or converted.
Customer & PII data — payloads that must never leave your compliance boundary.

If a tool can persist your input on a server, your threat model has to assume it might — until proven otherwise. Client-side tools remove that risk by construction.

Read the full policy, or see the incident that proved the point.

Our privacy policy is the legal version; the 2025 formatter leak explainer shows why architecture is the only real defense.

Frequently Asked Questions

Can jsonversal see or store the data I paste into a tool?

No. Every tool runs entirely in your browser using JavaScript, the Web Crypto API, and the File API. Your input never leaves the device — there is no server round-trip, no account, and nothing is uploaded, logged, or stored by us.

How can I verify that no data leaves my browser?

Open the tool, press F12 (or Cmd+Option+I) to open DevTools, switch to the Network tab, clear it, then paste your input and run the tool. On a client-side tool like ours, no outgoing request carrying your data appears. That test is definitive and needs no trust in any privacy policy.

Do you use analytics, cookies, or third-party trackers?

We run no analytics of our own and set no first-party cookies. This site is funded by Google AdSense, so Google and its partners may use cookies and similar technologies to serve and measure ads — that is the one third party that receives a request at runtime. Your tool input is never part of it. You can opt out of personalised ads at Google Ads Settings or aboutads.info; the links are in our Privacy Policy.

If you don't collect data, what about Cloudflare / hosting and ads?

The site is served by Cloudflare Pages, so connection metadata such as your IP address is processed by the host — as it is for any website. Our ad partner likewise receives ordinary page-visit information (IP, page, device) as any ad network does. What neither ever sees is the content you submit: tool inputs are never sent to a server, so there is nothing about your payloads for us, our host, or our ad partner to collect.

Can I inspect the code that runs my data?

The tools are delivered as static pages and execute in the open inside your browser tab. You can inspect the network traffic and the page logic directly. See the /licenses/ page for the full list of open-source components we build on.

🔒

Your data never leaves your device

All processing happens in your browser. No uploads, no tracking, no servers. Your API keys, configs, and private payloads stay private — 100% client-side.