BACK TO EDITOR
JSONObject.OnLine

Frequently Asked Questions

Everything you need to know about security, cookies, and data

Is my JSON data sent to any server?

No. All parsing, minification, tree exploration, and validation are performed 100% locally inside your browser. We leverage standard Web APIs and client-side scripts to run all operations. Your data never leaves your computer unless you explicitly choose to generate an encrypted sharing link.

How does the encryption process for sharing work?

When you click the Share button, your JSON payload is encrypted directly in your browser using the industry-standard AES-GCM (256-bit) algorithm.

The decryption key is generated locally and appended as a URL fragment (hash) after the `#` character. Because browser URL hash fragments are never transmitted to our servers (or any database), we host a zero-knowledge repository. Only the people you share the complete URL link with can decrypt and read the contents.

Do you use cookies?

Yes, but we only use essential "cookies" in the form of local browser persistence (localStorage and sessionStorage).

These storage systems save your active JSON, format settings, editor themes, and viewport configurations locally. Without these local persistence cookies, formatting and parsing would be impossible, as your configuration state would reset on every single interaction or refresh. We never use cookies for marketing or tracking.

Where are the shared snippets stored?

When shared, the encrypted payload is stored in a secure cloud database. Since it is fully encrypted on your machine before upload and contains no unencrypted keys, the stored payload is mathematically useless to us or anyone else. It is only accessible to those holding your exact unique URL containing the decryption hash.

How can I delete my shared snippets?

When you create an encrypted snippet share link, your browser generates and saves an anonymous ownership token in its local history. You can view, search, and delete your shared snippets at any time directly through the local History explorer on the homepage.