Privacy policy

Private by design. Local by default.

PageBrine is built for user-owned archives. It does not run analytics, remote indexing, accounts, subscriptions, or external API calls.

Effective date: May 15, 2026

No data leaves unless you export it.

Captures, URLs, screenshots, metadata, tags, notes, and indexes stay on the device and folder you choose.

  • No accounts
  • No analytics
  • No remote services

Local-first storage

PageBrine saves webpage captures to a folder selected by the user on their own device. Extension settings and the local index cache are stored in browser storage.

No remote services

PageBrine does not upload archived content, URLs, screenshots, metadata, tags, notes, or search indexes. It does not use analytics, advertising, crash reporting, remote logging, remote indexing, accounts, subscriptions, or external APIs.

Limited Use

PageBrine does not transfer user data to third parties. Data handled by the extension is used only to provide local webpage capture, archive search, comparison, settings, optional local encryption, and user-requested import/export features. PageBrine's use of user data complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

Data handled during capture

When the user saves a page, PageBrine may process the URL, title, domain, timestamp, extracted text, sanitized HTML, screenshots, thumbnails, asset references, notes, tags, collections, local indexes, integrity hashes, and an optional local encryption session passphrase when encrypted capture mode is enabled.

User responsibility

Archived pages may contain sensitive information. Users are responsible for protecting their local archive folder, backups, and exported ZIP files.

Access controls

PageBrine saves pages the user can already access in their browser. It does not bypass paywalls, logins, DRM, or technical access controls.