Privacy Policy
Effective Date: May 8, 2026
This Privacy Policy describes how JSON Pretty Pro ("the Extension") handles user data. We are committed to ensuring your privacy and being transparent about how our tool operates.
The Core Principle: JSON Pretty Pro is a "local-first" developer tool. While we use anonymous analytics to improve the extension, your actual JSON data, code, and tokens never leave your browser and are never sent to our servers.
1. Data Collection and Usage
The Extension interacts with the following types of data:
- Website Content & JSON Data: To provide formatting and visualization, the Extension reads and parses text content locally. This data is never transmitted to any external server.
- Authentication Tokens (JWT): The JWT decoder works entirely client-side. Your sensitive tokens are never logged or transmitted.
- Anonymous Usage Analytics: We use Google Analytics 4 to collect non-personally identifiable information to improve the extension. This includes:
- Extension Activation Rate & Session Duration
- Feature Usage (Playground, Export, Table View, Diff, Time Machine)
- Technical performance (JSON Parse Errors, Pagination Triggers)
- User interactions (Feedback Link Clicks, JWT Decode Clicks, Enable/Disable Toggles)
2. Local Storage
The Extension uses the chrome.storage.local API for the following purposes:
- Settings: To save your theme preferences and configuration.
- Time Machine (History): To enable comparison features, a cache of your recent JSON responses is stored locally on your machine. This is never shared.
3. Permissions
The Extension requires <all_urls> access to detect JSON content across different development environments. It only activates its UI when valid JSON is detected.
4. Data Sharing and Third Parties
We do not sell or trade your information. We use Google Analytics as a third-party processor to analyze anonymous usage patterns. No personally identifiable information (PII) is shared with Google Analytics.
5. Changes to This Policy
We may update this policy from time to time. Any changes will be reflected by updating the "Effective Date" at the top of this page.
6. Contact
If you have any questions regarding this policy, you can contact the developer via the official support channels on the Chrome Web Store or GitHub.