Web Paperize

Last updated October 15, 2026

Privacy Policy

Web Paperize processes only the content needed to create the PDF or Markdown file you request. The developer operates no extension backend and receives neither the exported content nor your ChatGPT token.

Overview

Web Paperize saves webpages or user-selected web content as local PDF or Markdown documents. The extension handles page content inside your browser to perform that user-requested export. The Web Paperize developer does not operate a backend service for the extension and does not receive the content being exported.

Data handled during an export

Depending on the export mode, Web Paperize may temporarily process:

  • the content, styling, images, links, title, and URL of the active webpage;
  • the element or text selection you explicitly choose;
  • the generated export bytes and requested local filename;
  • layout measurements and export status needed to complete and restore the page; and
  • for a ChatGPT complete-conversation export, the current conversation, referenced sources, attachment metadata, and conversation image download URLs returned by ChatGPT/OpenAI.

Ordinary webpage content is processed locally in Chrome. Exported content is not sent to a Web Paperize developer server or to unrelated third parties. The webpage itself may still load images and scripts as usual. Web Paperize has no developer backend.

ChatGPT complete-conversation exports

The complete-conversation acquisition runs only when you choose to export the complete conversation currently open on chatgpt.com or chat.openai.com. PDF and Markdown obtain that complete conversation in the same way.

Web Paperize uses your existing ChatGPT login session to request the currently open conversation directly from ChatGPT/OpenAI. Images in the conversation may also require requests to ChatGPT/OpenAI for download URLs. These requests are solely for the export you have requested.

The ChatGPT access token is used transiently in browser memory. It is not logged, stored, included in the generated export file, returned to the extension's service worker, or sent to the Web Paperize developer or an unrelated third party. Conversation content is not uploaded to or retained by a Web Paperize server because no such server exists.

Web Paperize is an independent extension and is not affiliated with OpenAI.

Local storage and retention

  • Export preferences—including output format, paper, layout, margins, filename template, and interface language—are stored in chrome.storage.local. Chrome retains this extension-specific data until it is changed or the extension is removed.
  • While a Chrome download is pending, Web Paperize stores only the metadata needed to reconcile that download in chrome.storage.session, such as its Chrome download ID, filename, size, page title or URL, layout result, and a temporary blob URL when applicable. An entry is deleted after Chrome reports the download complete or interrupted. Chrome also clears session storage when the extension is disabled, reloaded, or updated, or when Chrome restarts.
  • Element pickers also keep a short-lived request ID and requested output format in chrome.storage.session. This operation state contains no exported body and is removed when consumed, cancelled, or its tab closes.
  • For each tab, chrome.storage.session retains its most recent export task so reopening the popup can show the status. Depending on the task, this can contain success or failure status, task or download identifiers, filename, size, page title or URL, layout or format/scope results, and necessary error information. Download completion leaves this latest-task record in place. A new task replaces it, and tab closure removes it. Chrome also clears this session storage when the extension is disabled, reloaded, or updated, or when the browser restarts. This is distinct from pending-download entries.
  • Page and conversation body text is not persisted in extension storage.
  • Generated export data exists transiently in browser memory and a temporary blob or data URL during export and while its download is pending. Temporary download resources are released after Chrome reports completion or interruption, when applicable.
  • The completed export file is saved through Chrome's Downloads API according to your Chrome download settings. In Web Paperize, the optional "Choose where to save each time" option is off by default; enabling it lets you choose the location in Chrome's save dialog. The file belongs to you on your computer. Web Paperize does not upload it or automatically delete it.

Removing Web Paperize clears its chrome.storage.local data according to Chrome's extension-storage behavior. Removing the extension does not delete export files you have already saved.

Collection, telemetry, sharing, and sale

Web Paperize does not collect telemetry, analytics, crash reports, browsing history, or advertising identifiers. It does not sell user data. It does not transfer exported content to the developer, advertisers, data brokers, or unrelated third parties. It does not use user data for advertising, creditworthiness, lending, or any purpose unrelated to generating the user-requested export.

The extension does not allow the developer or other humans to read exported content. If you voluntarily include content in a support request, that separate disclosure is controlled by you and is not automatic extension collection.

Permissions

  • activeTab and scripting process the active page only after you invoke an export or picker action.
  • debugger temporarily attaches to that tab only for PDF export to use Chrome DevTools Protocol print and emulation commands, including Page.printToPDF; it detaches after success or failure and is not used for background browsing monitoring. Markdown does not attach the debugger.
  • downloads saves the PDF or Markdown file and observes the status of downloads created by Web Paperize.
  • storage keeps local preferences, the latest per-tab export task, and short-lived pending-download and picker-request metadata.
  • offscreen creates and revokes a temporary export blob URL because an extension service worker cannot create one directly.
  • contextMenus provides user-initiated page, selection, and element export actions.

The manifest does not request broad host permissions such as <all_urls>.

Chrome Web Store Limited Use

Web Paperize's use and transfer of information received from websites and Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

  • Web Paperize accesses and uses user data only as necessary to provide the user-facing document export functionality you requested.
  • Web Paperize does not sell user data.
  • Web Paperize does not use or transfer user data for personalized advertising.
  • Web Paperize does not transfer user data to unrelated third parties. The direct ChatGPT/OpenAI requests described above occur only for a user-requested ChatGPT export and are necessary to provide that feature.
  • Web Paperize does not allow the developer or other humans to access user content, except when you explicitly choose to provide content for support, or when access is required for security or legal obligations.

Contact and changes

For privacy questions, email ckyueix@gmail.com.

Material privacy changes will be documented here and disclosed through the Chrome Web Store listing or extension UI when required before the changed data practice takes effect.