A short, honest summary of what data Big JSON Viewer touches, and what it doesn't.
Big JSON Viewer is a static web app served from https://www.bigjsonviewer.com. It runs entirely in your browser. We do not operate any backend that stores, processes, or relays the JSON you view.
The following data is processed only on your device and is never transmitted to us:
localStorage on your browser).If you choose to click Share, the app will:
drive.file scope, plus openid, email, and profile to display which account you are signed in to.Big JSON Viewer/ in your own Google Drive. The file is owned by you.The drive.file scope means this app can only see and manage files it has created on your behalf. It has no visibility into the rest of your Google Drive. You can revoke our access at any time at myaccount.google.com/permissions, and you can delete or unshare any individual file from drive.google.com.
When someone opens a share URL (/s/<fileId>#path=…), the app fetches the JSON directly from Google Drive's public read endpoint using a public API key. The recipient does not sign in. We never see the contents of the file, the recipient's identity, or which file was opened.
The production site loads two scripts from Vercel:
Both are opt-out by sending a DNT: 1 or Sec-GPC: 1 header, or via your browser's content blocker. Local tauri dev / open-source self-hosted builds load no analytics at all.
We set no cookies of our own. During the Google sign-in flow, Google sets its own cookies on its domains, which are governed by Google's privacy policy.
Big JSON Viewer is a developer tool not directed at children under 13. We do not knowingly process data from children.
If we change how the app handles data, we will update this page and bump the date below. Material changes that affect existing share links will be called out in the app's UI.
Big JSON Viewer is open source. For questions, issues, or to report a security concern, please open an issue at github.com/bigjsonviewer/bigjsonviewer/issues.