Pagium Web Clipper — Privacy Policy

What this policy covers

This policy applies to the Pagium Web Clipper browser extension published in the Chrome Web Store by InspireHub Labs. It does not cover the Pagium desktop application, third-party websites you visit, or the Chrome browser itself.

Single purpose

The extension exists to do one thing: save the active web page into a local Pagium vault as a single self-contained .html file. It has no analytics, telemetry, advertising SDK, A/B framework, or background sync. There is no account system because there is no backend.

Data we collect

None. The extension does not transmit any data — about you, your device, your browsing, or the pages you clip — to InspireHub Labs or any third party.

The extension processes the page content (HTML, CSS, images, fonts) on your machine to assemble the clip, then writes the resulting file to your own ~/Downloads/.pagium-clipper/ staging folder. From there, the Pagium desktop app reads the file via the pagium:// URL scheme and moves it into your vault. Both endpoints — the staging folder and your vault — are folders on your hard drive.

Data the extension reads locally

To assemble a clip, the extension reads the following from the active tab — but only at the moment you click "clip," and only for the page you are clipping:

The page's HTML document (DOM)
The page's authored CSS stylesheets and computed styles
Content images, fonts, and inline media referenced by the page
The page URL and document title, written into the saved file as pagium:source and pagium:title meta tags
The current text selection, only when you choose "Clip selection to Pagium"

This data never leaves your machine. It is processed in-memory, written into the captured .html file, and discarded.

Data the extension stores locally

The extension uses chrome.storage.local — Chrome's per-extension local storage — for your preferences only. This storage is on your disk and is never read or transmitted by us.

The list of vault names you configured in the options page
Which vault is the default for silent clips
The capture mode you last selected (Reader or Snapshot)

You can clear all of this at any time by removing the extension or by clicking "Reset" in the extension options page.

Permissions and why we ask for them

Chrome will prompt you for permissions at install time. Each one maps to a specific capture step:

activeTab

Lets the extension read the currently focused tab when you press the toolbar button, the keyboard shortcut, or pick a context-menu item. We only inspect the tab in that exact moment — never in the background.

scripting

Lets the extension inject the capture script (content/capture.bundle.js) into the active tab to walk the DOM and inline its CSS. Injection happens only at the moment of a clip.

contextMenus

Adds the "Clip page to Pagium," "Clip selection to Pagium," and "Clip with options…" items to Chrome's right-click menu.

storage

Persists your vault list and capture-mode preference in chrome.storage.local, which is local to your browser profile.

downloads

Writes the assembled .html clip to a staging folder at ~/Downloads/.pagium-clipper/. The Pagium desktop app reads the file from there, moves it into your vault, and the extension deletes the staging copy.

declarativeNetRequestWithHostAccess

Lets the extension temporarily relax referer/origin restrictions when fetching a page's own CSS bundles and content images during clipping. No requests are sent anywhere except to the same origins your browser is already loading.

host_permissions: <all_urls>

Required to fetch a page's authored stylesheets when its CDN does not return CORS headers — without this, Snapshot mode breaks on most modern sites (Vue/React/Next.js etc.). The fetches go to the same origins the page itself loaded from; the response is inlined into your saved file. Nothing is sent to any server controlled by InspireHub Labs.

Servers, cookies, accounts

There are none. The Pagium Web Clipper does not run any backend, does not set cookies, does not have an authentication system, does not embed third-party analytics, and does not contact any remote service operated by InspireHub Labs. The only network requests the extension issues are to the page you are clipping, on your behalf, the same way your browser already loads it.

Children's privacy

Because the extension collects no data of any kind, it does not knowingly or unknowingly collect data from children under 13 (or under 16, where applicable). The extension is suitable for users of any age, subject to Chrome Web Store age policies.

Compliance with the Chrome Web Store User Data Policy

InspireHub Labs adheres to the Chrome Web Store Developer Program Policies, including the Limited Use requirements. We do not transfer user data to third parties except as required to fulfil the user-requested action of saving a clip into the local Pagium vault, and we do not use, transfer, or sell user data for advertising, credit-worthiness, lending, or any unrelated purpose.

Changes to this policy

Material changes will be reflected in the "Last updated" date at the top of this page. If we ever start collecting or transmitting any data, this policy will be rewritten and announced in the extension release notes before the change ships.

Contact

Privacy questions, security disclosures, or anything else about how the clipper handles your data: [email protected].

InspireHub Labs · Operator of pagium.app.