Privacy

j2n reads, fixes and formats JSON on your device. Nothing you paste, type or open is uploaded, and no server receives or stores it.

Everything stays in your browser

Like any website, the host that serves j2n's files sees ordinary request details, such as your IP address and the page you asked for. It never sees your JSON.

n8n node checks

When you open n8n JSON, j2n checks GitHub for the latest n8n release, downloads that release's public list of nodes from jsDelivr, and looks up the workflow's community packages on npm by name. Only those package names are sent. Your workflow's settings and values, and its node and workflow names, never leave the browser.

These are requests for public files, so GitHub, jsDelivr and npm see the same request details any website would, like your IP address. If they can't be reached, j2n checks against the list of nodes built into the page instead.

Share links

When you share, j2n puts the JSON inside the link itself, compressed, after the #: https://j2n.dev/#d=1.…. Browsers never send the part after # to a server, so opening a link doesn't send the data anywhere. If you've set rules (a JSON Schema), they travel in the link too, compressed the same way, and the person who opens it gets them in the Rules tab. After the link opens, j2n removes that part from the address bar.

Anyone who has the link can read the data, so treat it like the file itself. The app you send it with, like email or chat, keeps a copy of the link as it would any message. If the JSON or the rules have values that look like secrets, such as API keys or passwords, j2n asks first and offers to leave them out.

What's saved on your device

Only your settings: the theme, the word mode (Simplified or Developer), the path format and the size of the two panels. They're kept in your browser's local storage under j2n.settings.v1. Your JSON and your rules (JSON Schema) are never saved, so reloading the page clears them.