Privacy Policy
Page to JSON browser extension
Page to JSON processes the data of the page you are viewing entirely on your own device. It is never sold, retained, or sent to the developer or any third party.
What the extension accesses
When you open the extension's popup, it inspects the current tab only to identify its type (so it can label the Export button). It reads the tab's full content only when you click Export. That content is whatever the page contains — for example issue, pull request, or change-request fields, which may include names, usernames, email addresses, and other user-generated text.
The extension acts only on the tab you are actively viewing, only while the popup is open, and only after you have clicked. It does not run in the background and does not observe or collect your browsing history or activity across sites.
On-device processing only
Extraction runs locally in your browser. The resulting JSON is written only to a file you download and, if you enable it in Settings, your clipboard. Nothing is sent to the developer, to Google, to any AI/LLM service, or to any other third party.
Same-origin reads
To assemble a complete export, the extension may fetch additional data from the active tab's own website
(for example a pull request's .diff, or Jira REST data) over your existing signed-in session. These are reads of
content you can already see, returned as data and processed locally. They are never sent to the developer or anyone else,
and the extension never reads or stores your authentication cookies.
What is stored
The extension uses the browser's extension storage to keep only: your one-time consent acknowledgement and your output preferences (clipboard on/off, download on/off, pretty-print). No page content is ever stored.
What the extension does not do
- No transmission of page data anywhere.
- No retention — extracted content exists only transiently in memory and in the file/clipboard you control.
- No tracking, analytics, or browsing-activity collection.
- No advertising, no sale or transfer of data, no use of data by the developer.
- No financial data, health data, passwords, or authentication cookies are read or stored.
Report an issue & Feedback (GitHub Issues)
The popup's optional "Report an issue" and "Feedback" links open the project's public GitHub issue tracker. If you choose to file one, your submission is posted publicly on GitHub and is handled under GitHub's Privacy Statement. An issue contains only what you choose to write; the extension never automatically attaches page content or any extracted data. Because issues are public, please do not include private or sensitive information. Filing an issue is entirely optional and never required to use the extension.
Donations
The popup includes an optional "Buy me a coffee" link to a third-party donation service (Buy Me a Coffee). Donations are voluntary and never required. The developer is not the seller and collects no payment information; any payment data is handled by that third-party service under its own policy.
Permissions
activeTab— read the current tab only when you click, and make the same-origin reads described above.scripting— inject the extractor into the page on your click (no persistent scripts; nothing runs on page load).storage— persist the consent acknowledgement and your output preferences. No page content.
Limited Use. Page to JSON's use of data handled by the extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Page content is processed locally on your device to produce a JSON export, is never transmitted or sold, is not used for advertising, and is never read by us.
Contact
Questions about this policy: gfmaximo97@gmail.com, or via the Buy Me a Coffee page.
Not affiliated with, endorsed by, or sponsored by Atlassian, GitHub, ServiceNow, or Qwiet AI. Product names are used only to describe supported pages.
© 2026 Gustavo Máximo Filho. All rights reserved.
Created by Gustavo Máximo Filho.
Updated: July 15, 2026.