ENRU

Security & data

Updated

What happens to the JSON you paste here, what is kept and for how long, and what the usage statistics contain. In short: the JSON tools send your text to our API, which processes it in memory and keeps nothing; Base64, the JWT decoder, Unicode Unescape and the position finder never leave your browser; only Share stores a copy, for 30 days.

What goes to our API

Formatter, Validator, JSON Viewer, Minifier, JSON to YAML, YAML to JSON, Diff and JSON to query string are computed by our API, not in your browser. Their pages send your text to jsonstatham.dev/api/v1/… — the same site, over HTTPS — and nowhere else.

Text is sent when you run a tool: the button or Ctrl/Cmd+Enter, a paste into an empty editor, a file you open or a sample. With live check on, it is also sent after each pause in typing and when a page opens with a saved draft; switch live check off in the status bar and nothing leaves until you run a tool. Diff compares only on command: Compare or Ctrl/Cmd+Enter. A shared link loads its document from the API too.

Limits: one document up to 1 MiB (in Diff, each side); up to 120 tool requests a minute from one IP address, and Diff on top of that up to 30.

What the API keeps

Nothing from the tools. Your text is processed in memory, the result goes back to your browser, and no copy is kept: no file, no database row, no log entry.

  • Each request leaves one technical log line: method, route, status, duration and the client IP address. The body and the query string are never written; for share links the log holds the route template /api/v1/shares/{id}, not the id.
  • Rate limits count requests per IP address in counters that expire with their window — a minute or a day.
  • The API also records usage facts about each run: the tool, the outcome, the error code, sizes in bytes and settings such as the indent. Never the document.

What stays in your browser

Base64 runs entirely in your browser: decoding, encoding and reading the parts of a JWT. Its page makes no requests to our API at all. The text leaves only if you press Format in Formatter: the Formatter page then sends it like any JSON tool.

The JWT decoder, Unicode Unescape and the position finder run in your browser too. The token, the escaped text, the document and the parser message never leave it, and none of these pages makes requests to our API. Unicode Unescape hands its result to the Formatter only when you press Format in Formatter, as Base64 does. The JWT decoder does not verify signatures: that takes a key, and it belongs on your server.

Local storage in your browser keeps, on this device only: the draft of the JSON tools (Diff keeps both sides; a draft above 1 MiB isn’t saved), tool settings, the theme you chose, the last share link (until the tab is closed) and the two IDs described under usage statistics. Clearing this site’s data in your browser removes all of it.

Share links

Share is the only feature that stores your document. It saves the exact text, its size, and when it was created and expires. No account, no IP address, no name.

  • A link lives 30 days. After that it can’t be opened, and the hourly cleanup deletes the copy.
  • The id is 10 characters picked at random from 62 (digits and Latin letters in both cases) by a cryptographic generator: 62^10, about 8.4 × 10^17 possible ids, 59.5 bits. Opening links is limited to 120 a minute per IP address, so guessing one is hopeless.
  • Shared pages are marked noindex, nofollow — in the page and in the X-Robots-Tag header — and are not in the sitemap. There is no list of recent links and no search: a link is found only by someone who has it.
  • Anyone with the link can read the document until it expires, and a link can’t be deleted early. Don’t share passwords, tokens or personal data.
  • Creating links is limited to 10 a minute and 100 a day per IP address, each document up to 1 MiB.

Usage statistics

We count how the site is used to see what to fix. Events go straight from your browser to our own analytics intake at x4k2m.jsonstatham.dev, not to an advertising or analytics company.

An event says what happened, not to what: the page, which tool ran and how it ended, the error code, sizes in bytes, how many characters Unicode Unescape decoded or kept, how long it took, settings (indent, sorting, live check, theme, language), page speed, and script errors with any quoted data cut out.

It never contains your document: no text, keys or values, no Diff paths, no character at an error, no Base64 or Unicode Unescape input or output, no JWT or parser message, no file names. No page address, query string or share link id; no browser identification string, screen size, browser language or time zone. Where you came from — only the origin of the referring site, on the first page of a visit.

A typical event, without the IDs and the time that every event also carries:

{
  "event_name": "tool_used",
  "page": "format",
  "locale": "en",
  "props": {
    "tool": "format",
    "trigger": "explicit",
    "outcome": "invalid",
    "error_code": "trailing_comma",
    "input_bytes": 2048,
    "duration_ms": 41,
    "indent": "2",
    "is_sorted": false
  }
}

Events are tied to a random device ID — a UUID your browser generates and keeps in local storage with no expiry — and to a visit ID that changes after 30 minutes without activity. That makes the statistics pseudonymous, not anonymous. There are no cookies. Requests to our API carry the same two IDs and a request ID in X-Visitor-Id, X-Session-Id and X-Request-Id, so the page’s record of a run can be matched with the API’s. There is no switch to turn statistics off; clearing this site’s data gives your browser a new device ID.

No third parties

Scripts, styles, fonts and images all come from jsonstatham.dev. The Content Security Policy forbids anything else, so the pages can’t load a tracker, an ad or a font from another site. The only other address they talk to is the analytics intake above.

Security and data FAQ

Is my JSON sent anywhere?

Yes: to our own API over HTTPS, when a JSON tool runs, and nowhere else. Base64, the JWT decoder, Unicode Unescape and the position finder are the exceptions: their text never leaves your browser.

Do you store or log my JSON?

No. It’s processed in memory and not kept. The only copy is the one you create with Share, for 30 days.

Can someone find my shared link?

Only if they have it. The id is random, 10 characters long; shared pages aren’t indexed or listed anywhere, and guessing is limited to 120 tries a minute per IP address.

Can I delete a shared link?

Not before it expires: it’s deleted 30 days after it was created. Remove secrets before you share.

Are the statistics anonymous?

Pseudonymous: tied to a random device ID, never to your name, email or document. Clearing this site’s data in your browser gives you a new ID.