JSON Workbench Privacy Policy

Effective and last updated: June 19, 2026

Short version: JSON Workbench processes JSON locally in your browser. We do not upload your JSON contents to our servers. Recent JSON, saved JSON, settings, and preferences may be stored locally in your Chrome profile so the extension can provide its workbench, library, compare, and settings features.

This Privacy Policy explains how JSON Workbench ("the extension," "we," "us," or "our") handles information when you use the JSON Workbench Chrome extension.

1. What the Extension Does

JSON Workbench helps users view, format, validate, decode, compare, save, and navigate JSON directly in Chrome. It is designed for working with API responses, webhook payloads, logs, copied JSON snippets, and other JSON data.

The extension may provide features such as a side panel, a full-page JSON workbench, JSON formatting, minifying, validation, stringified JSON decoding, JSON comparison, saved JSON, recent JSON history, settings, and local data-management controls.

2. JSON Contents

JSON content that you paste, open, format, validate, decode, compare, save, or view in JSON Workbench is processed locally inside your browser. We do not upload JSON contents to a server operated by us.

If you choose to copy, export, download, or otherwise move JSON data outside the extension, that action is controlled by you and may be handled by your browser, operating system, or destination application.

3. Information Stored Locally

The extension may use browser-local storage, including Chrome extension storage and/or IndexedDB, to support its features. The following information may be stored in your Chrome profile:

recent JSON history, if enabled;
manually saved JSON items;
pinned JSON items;
JSON item titles, timestamps, source type, source URL, size, and metadata;
temporary compare state or compare history, if supported;
formatting preferences such as indentation, key sorting, and default view;
viewer preferences such as collapse depth, line numbers, and display options;
stringified JSON detection and decoding preferences;
compare preferences;
history, library, privacy, data-management, appearance, and language preferences; and
sensitive-field detection settings, including custom sensitive key names if supported.

This local information is used only to provide extension features, preserve your workspace, reopen recent or saved JSON, compare previous JSON, and remember your settings.

4. Information We Do Not Collect

JSON Workbench does not collect or transmit the following information to us:

your JSON contents;
your saved JSON library;
your recent JSON history;
your authentication tokens, API keys, passwords, or authorization headers;
your browsing history;
your personal communications;
your financial information;
your health information;
your contacts;
your camera, microphone, or location data; or
your JSON data for advertising, profiling, or AI model training.

5. Sensitive Data

JSON content may contain sensitive information such as passwords, access tokens, API keys, authorization headers, customer data, personal data, or other confidential values.

JSON Workbench may detect common sensitive field names and show warnings. These warnings are provided for convenience only and may not detect every sensitive value.

You are responsible for reviewing the JSON you choose to view, copy, save, export, compare, or share.

6. Local Data Deletion

JSON Workbench may provide settings to delete local extension data. Available controls may include:

clear recent JSON history;
clear saved JSON;
clear compare history or temporary compare session data;
reset settings to default; and
delete all local data.

The “Delete all local data” option is intended to remove local data controlled by the extension, including recent JSON history, saved JSON, pinned JSON, compare history or temporary session data, app settings, sensitive key settings, and UI preferences.

Local data may also be removed by uninstalling the extension, clearing Chrome extension data, or using Chrome profile/site-data controls, depending on your browser settings.

7. Chrome Permissions

JSON Workbench may request Chrome permissions only as needed to provide its features. Depending on the version installed, these may include:

storage: used to store extension settings, recent JSON, saved JSON, JSON metadata, and local preferences in your Chrome profile.
sidePanel: used to provide quick JSON tools in Chrome's side panel.
activeTab or tab/page access: used when needed to detect or open JSON content from the current page. JSON content is processed locally and is not uploaded to our servers.
host permissions, if used: used to detect pages that contain JSON responses and show a small JSON Workbench launcher. Page content is processed locally for this feature and is not uploaded to our servers.

JSON Workbench does not request permissions for unrelated purposes.

8. Remote Code

JSON Workbench does not use remotely hosted code. Extension code is included in the extension package.

9. Analytics, Advertising, and Tracking

JSON Workbench does not use analytics in the MVP version.

We do not use JSON contents for advertising, profiling, tracking, or training artificial-intelligence models. We do not sell personal information or JSON contents.

If analytics are added in a future version, this Privacy Policy will be updated to explain what is collected. JSON contents will not be included in analytics.

10. Data Sharing

We do not share JSON contents with external processing services.

Information may be disclosed if required by law or when necessary to protect users, rights, safety, or the security of the extension and related services.

11. Retention

Local JSON history, saved JSON, settings, and preferences remain in your Chrome profile until you delete them through the extension, clear Chrome extension data, reset your browser profile, or uninstall the extension.

Data copied, exported, downloaded, or shared outside the extension is controlled by you and remains wherever you store or send it.

12. Your Choices

Use the extension without manually saving JSON.
Disable recent history if the setting is available.
Delete individual saved or recent JSON items.
Clear recent JSON history.
Clear saved JSON.
Reset extension settings to default.
Delete all local extension data.
Uninstall the extension to remove extension storage from that Chrome profile.

13. Security

Local browser processing reduces the need to transmit JSON contents over the internet. However, no storage system is completely secure. You are responsible for protecting access to your device, Chrome profile, copied JSON, saved snippets, downloaded files, and any sensitive data you choose to process with the extension.

14. Children's Privacy

JSON Workbench is not directed to children under 13, and we do not knowingly collect personal information from children under 13.

15. Chrome Web Store Limited Use Disclosure

The extension's use and transfer of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Information is used only to provide or improve the extension's user-facing features and for permitted security, legal, and operational purposes.

16. Changes to This Policy

We may update this policy when the extension's features, service providers, or legal obligations change. The effective date at the top of this page will be updated when changes are published.

17. Contact

For privacy questions, support requests, or concerns about this policy, contact:

JSON Workbench
Email: zhang121215028@gmail.com