JSON Schema Docs by JSONBuddy generates readable HTML documentation from a JSON Schema selected by the user. The selected schema is sent over HTTPS to the JSONBuddy Web API solely to generate that documentation.
We do not sell schema content, use it for advertising, or use it to track browsing activity.
1. Scope
This policy applies to the JSON Schema Docs by JSONBuddy Chrome extension.
2. Information processed
JSON Schema content
The extension processes a JSON Schema only after the user loads JSON from the active browser tab, pastes schema content, or selects a local .json file. Schemas are limited to 50 KB. The extension does not monitor browsing activity or read pages in the background.
Connection metadata
Standard server access logs may record operational metadata such as IP address, timestamp, requested endpoint, user agent, and response status. Request bodies containing schema content are not included in standard access logs.
3. How information is used
Schema content is used only to generate the requested HTML and SVG documentation and return it to the extension. Connection metadata may be used to operate, secure, and troubleshoot the service and to prevent abuse. It is not used to build advertising profiles or track browsing history.
4. Storage and retention
- Submitted schemas: Processed for the request and not as application data or intentionally written to application logs.
- Generated documentation: Stored by the extension only in Chrome session storage so it can be displayed, and cleared with the browser session. A downloaded HTML file is controlled by the user.
- Consent preference: A boolean recording acceptance of the privacy disclosure is stored locally in the Chrome profile. It contains no schema content.
- Server access logs: only as long as reasonably necessary for security, abuse prevention, troubleshooting, and reliable operation.
5. Sharing and disclosure
Schema content is transmitted only to the JSONBuddy Web API and infrastructure providers operating that service on our behalf. It is not sold, licensed, provided to advertising networks, or shared for unrelated purposes. Information may be disclosed if required by law or necessary to protect the security and integrity of the service.
6. Chrome permissions
activeTab- Allows the user to request JSON from the active tab.
scripting- Reads JSON text from that tab after the user selects the command.
storage- Stores the generated result for the browser session and remembers the consent preference.
api.json-buddy.com- Sends the selected schema to the documentation endpoint over HTTPS.
7. Security
Schema content is transmitted using HTTPS. Generated HTML is displayed in a sandboxed frame without script execution. The extension does not load remotely hosted executable code.
8. User choice and local processing
The extension asks for consent before sending the first schema. You can avoid transmitting schema content by not using the generation command or by removing the extension.
Use the JSONBuddy command-line tool to keep schema processing on your computer.
9. Chrome Web Store Limited Use
Information received through Chrome APIs is used only to provide the extension's disclosed documentation-generation feature. Our use of that information complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.
10. Changes to this policy
If the extension's data practices change, this policy and the extension disclosure will be updated before the new practices take effect. The revision date at the top identifies the latest version.
11. Contact
Questions about this policy or the handling of extension data can be sent to contact@xml-buddy.com.