Privacy Policy

Effective date: March 16, 2026 · Last updated: August 7, 2026

Overview

Web to File is a Chrome extension that exports webpage content as PDF, Markdown, EPUB, or image files. All processing happens locally in the user’s browser. The extension does not transmit webpage content to external servers and does not share user data with third parties.

What the extension accesses

  • Page content on websites the user visits, only to extract or capture content for export.
  • The current tab and window state, so the side panel and export flow can target the active page.
  • Local extension storage, to save user preferences, export history, and temporary export data.
  • Chrome’s rendering pipeline, only during a PDF or screenshot export the user has started.

Web to File begins working on a page only when the user starts an export, capture, preview, or selection, and only on the tab the side panel is open on. It does nothing on the other pages the user visits.

Network requests

Web to File has no servers of its own and sends nothing to any. Two features request data, and both request it only from the site the user is already on:

  • EPUB export collects the article’s own images so they can be embedded in the file and stay readable offline. Those requests carry no cookies.
  • AI conversation export reads the conversation from the page the user has open, so the whole thread can be written to the file. Nothing is requested from anywhere else.

What the extension does not collect

Web to File does not gather, retain, or profile user data. Content the user points it at — including a conversation they choose to export — is converted on the device and written to the file they asked for. It is not accumulated and it is not sent anywhere.

The extension collects no health information, no financial or payment information, no location data, and no browsing history beyond the local record of the user’s own exports. There is no account and no sign-in.

Data usage and storage

Page content is used solely to support export features: article extraction, full-page capture, custom selection, and AI conversation export. Generated files are downloaded directly to the user’s device; some are stored locally for in-extension viewing.

Local storage on the device, held by the browser and never leaving it, may include:

  • Export preferences and settings
  • Temporary article data for editing/export
  • Export history
  • Exported files kept for in-extension viewing

Users can remove this data by clearing the export history in the extension’s settings, clearing extension storage, or uninstalling the extension.

Data sharing

We do not sell user data. The extension does not transfer webpage content, exported files, or browsing data to external servers, and does not use analytics, advertising, tracking pixels, or third-party telemetry.

Permissions rationale

This list is exactly what Chrome shows on the extension’s listing. Web to File requests no access to downloads and none to browsing history: files are saved through the browser’s own download flow, so the “Ask where to save each file” setting is respected rather than bypassed.

  • activeTab: run extraction on the page the user is working with
  • scripting: add the extraction tools to the current page when the user starts an export or selection
  • debugger: generate PDFs and capture rendered page regions, only during an export the user started
  • storage: keep preferences and local history
  • sidePanel: provide the extension’s main interface
  • <all_urls> host access: run on the pages the user chooses to export, and collect the article’s images for EPUB export, which are usually served from a different domain than the page

Security and remote code

All executable logic ships inside the extension package. The extension does not load external scripts or remote modules.

This website

This policy covers the Web to File extension. The website at webtofile.pandaopus.com is separate and loads no third-party analytics, advertising, or tracking scripts. Like most websites, its server keeps standard access logs (IP address, page requested, timestamp, referrer, and browser user-agent) for security and to understand which pages are useful. These logs are not shared with third parties and are retained for a short period.

Contact

For privacy questions, contact us through the support page or the support channel linked from the Chrome Web Store listing.