Effective date: 2026-03-16
Web to File is a Chrome extension that helps users export webpage content into local files such as PDF and Markdown using article, full-page, and custom export workflows.
We are committed to protecting user privacy and limiting data processing to the extension's single purpose: helping users export webpage content they choose to save.
Web to File may process the following data only when the user explicitly starts an export, capture, preview, or selection workflow:
Web to File does not collect or process data for unrelated purposes such as:
Web to File uses webpage content only to provide user-requested export features, including:
This processing is limited to the extension's single purpose and is performed only in response to direct user action.
Web to File processes webpage content locally on the user's device.
Generated files are saved directly to the user's device through Chrome's download flow. Some exported files may also be stored locally in browser-managed local storage areas solely to support in-extension viewing initiated by the user.
Local storage used by the extension may include:
The local export history maintained by Web to File relates only to actions created through the extension. It is not used to collect, reconstruct, or analyze a user's general browsing behavior.
We do not sell user data.
We do not transfer webpage content, exported files, or browsing data to our servers.
We do not use or transfer user data for purposes unrelated to the extension's single purpose.
We do not use or transfer user data to determine creditworthiness or for lending purposes.
Web to File may provide links to optional support or feedback forms. If a user chooses to open and submit a support or feedback form, any information the user submits is provided voluntarily by the user and is governed by the policies of the applicable form or hosting provider.
activeTab: used only after the user explicitly invokes the extension on the current page. This permission allows Web to File to access the user-selected active tab and start article, full-page, or custom export workflows for that page.scripting: used to inject packaged local scripts into the user-selected page when the user starts an extraction, export, or custom selection workflow. This is required for local content extraction, custom selection, and preparing page content for export.tabs: used to identify the active tab selected by the user and to manage extension-created tabs used for export, preview, or viewer flows. This ensures the extension attaches to the correct page and can open local result views when needed.downloads: used to save user-requested export files, such as PDF and Markdown, directly to the user's device after the user completes an export action.debugger: used only during explicit user-initiated export or capture actions that require Chrome's rendering pipeline for high-fidelity PDF generation or rendered page capture. It is not used for background monitoring, browsing inspection unrelated to export, or persistent attachment outside the export process.storage: used to store local preferences, selected export settings, recent export history, and temporary workflow state needed for export, preview, and viewer features. This data is stored locally on the user's device.sidePanel: used to provide the extension's main workflow interface in Chrome's side panel, including export mode selection, preview, settings, and custom export editing alongside the current page.<all_urls> host access: required so the extension can work on webpages the user explicitly chooses to export. Web to File reads and processes page content only when the user starts an article, full-page, or custom export workflow. It does not automatically process pages in the background without user action.Web to File does not use remote code.
All executable logic required for extraction, selection, export, preview, and side panel workflows is packaged within the extension itself. The extension does not load external scripts, remote modules, remote WebAssembly, or executable code from evaluated strings.
Because processing is performed locally and exported files are saved directly to the user's device, exposure of webpage content is minimized. We do not include analytics SDKs, advertising SDKs, or remote execution mechanisms.
We may update this Privacy Policy from time to time to reflect product, legal, or operational changes. When we do, we will update the effective date shown above.
If you have questions about this Privacy Policy, please contact us through the support channel listed on the Chrome Web Store page or the official website associated with Web to File.