Privacy Policy

Last updated: July 25, 2026

Local-first processing

ArchivePack is local-first. The extension processes webpage archives entirely in the browser and downloads generated files to your device. No archived page content, screenshots, Markdown output, form values, cookies, localStorage, sessionStorage, Authorization headers, or browsing history is uploaded to developer servers.

The extension reads the active page only after you start an archive action from the popup, context menu, or keyboard shortcut.

Data processed locally

Website content

ArchivePack reads the active webpage you choose to archive in order to generate local archive files, including MHTML, full-page PNG screenshot, readable Markdown, metadata, and SHA-256 checksums. This data is processed locally and is not transmitted to developer servers.

Capture history

ArchivePack stores a local capture history in Chrome storage on your device. This history contains: page title, URL, domain, capture time, archive mode, result status, and generated filename. Archive file contents, screenshots, Markdown, and HTML content are not stored in capture history. You can clear this history at any time through the extension settings.

Task status

ArchivePack stores local task status and capture results so you can see what you archived and whether each step succeeded. This data is not sent to developer servers.

Data not collected

• Personally identifiable information — ArchivePack does not extract, upload, or build profiles from personal data. Archive files may contain information you choose to save, but the extension does not separately collect or transmit it.
• Authentication information — ArchivePack does not store cookies, passwords, authorization headers, localStorage, or sessionStorage.
• Financial, health, personal communications, or location data — The extension is not designed to collect these categories of data. If you archive a page that contains such information, it only appears in the local archive file you generate.
• Browsing history — ArchivePack does not track or record your browsing activity beyond the local capture history described above.

Data sharing

ArchivePack does not sell, share, or transfer user data to third parties.

Generated archive files

Generated archive files may contain visible page content and source metadata from the webpage you archived. Anyone who receives an archive file may be able to read its contents. Please handle archive files with the same care you would give the original webpage.

Remote code

ArchivePack does not load or execute remote code. All extension code is packaged with the extension. No external scripts, CDN resources, or remote configurations are fetched at runtime.

Permissions

ArchivePack requires the following Chrome permissions:

• activeTab — temporary access to the page you choose to archive, only after you start an archive action.
• scripting — injects page metadata, readable-content extraction, scrolling, and screenshot helper scripts after you start an archive.
• downloads — saves generated archive files to your device.
• storage — stores extension settings, temporary task status, and local capture history.
• offscreen — creates local Blob URLs, stitches screenshot segments with Canvas, and packages ZIP files in an extension document.
• contextMenus — provides page-level archive commands from the browser context menu.
• pageCapture (optional) — requested only when you choose an archive mode that includes MHTML output. Used to save the active page as a browser-generated MHTML file.

All permissions are used solely for the extension's core archiving functionality.

Access controls

ArchivePack does not bypass logins, paywalls, DRM, passwords, or technical access controls. The extension is a personal archiving tool for content you already have the right to access.

Contact

If you have questions about this privacy policy, please visit the Support page or email us at support@archivepack.app.