Privacy Policy

Effective date: March 16, 2026 · Last updated: July 19, 2026

Overview

Web to File is a Chrome extension that exports webpage content as PDF, Markdown, 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.
  • The Downloads API, to save exported files to the user’s device.
  • Local extension storage, to save user preferences, export history, and temporary export data.
  • The Chrome Debugger API, only during user-initiated PDF or screenshot operations that require Chrome’s rendering pipeline.

Content is processed only when the user initiates an export, capture, preview, or selection action.

What the extension does not collect

Web to File does not collect:

  • Personal communications
  • Health information
  • Financial data or payment information
  • Authentication credentials
  • Location data
  • General browsing history unrelated to the user’s use of the extension

Data usage and storage

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

Local storage on the device (Chrome extension storage and the browser’s Origin Private File System) 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

  • activeTab: run extraction on the page the user is working with
  • scripting: inject local extraction tools into the current page when the user starts an export or selection flow
  • tabs: manage the active tab and extension-created tabs used for export/preview
  • downloads: save generated files to the user’s device
  • debugger: generate PDFs and capture rendered page regions when Chrome’s rendering APIs are required
  • storage: persist preferences and local history
  • sidePanel: provide the extension’s main UI
  • <all_urls> host access: allow the extension to run on pages the user chooses to export

Security and remote code

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

Contact

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