Privacy Policy

Last updated: March 2026

Our Commitment to Privacy

PureJSON is built with a privacy-first approach. All JSON processing happens entirely in your browser. No data is ever sent to, stored on, or processed by any server. Your JSON data never leaves your device.

We believe that developer tools should respect user privacy by default. PureJSON was designed from the ground up to ensure that sensitive data — such as API keys, configuration files, and production data — remains completely under your control.

Data We Do NOT Collect

PureJSON does not collect, store, or transmit any of the following:

  • JSON data you paste, upload, or process in any tool
  • Personal information such as your name, email, or IP address
  • Usage analytics or behavioral tracking data
  • Cookies for tracking purposes (only localStorage for theme/locale preferences)

Local Storage

PureJSON uses your browser's localStorage to save your theme preference (light/dark mode) and language preference. This data is stored only on your device and is never transmitted to any server.

You can clear this data at any time by clearing your browser's site data for purejson.org.

Third-Party Services

PureJSON uses Google AdSense to display advertisements. Google may use cookies to serve ads based on your prior visits to this or other websites. You can opt out of personalized advertising by visiting Google's Ads Settings.

No other third-party analytics, tracking, or data collection services are used on this site.

Progressive Web App (PWA)

PureJSON is available as a PWA that can be installed on your device. Once installed, the app works entirely offline. No network requests are made during offline use, further ensuring your data privacy.

Changes to This Policy

We may update this privacy policy from time to time. Any changes will be posted on this page with an updated revision date. Since PureJSON does not collect user data, policy changes will typically relate to third-party services.

Contact

If you have any questions about this privacy policy, please open an issue on our GitHub repository.