Use the tab you asked for
PageMint acts only on the page you clicked from. No background access to other sites, and no always-on monitoring.
Trust & permissions
What we ask for,
and why.
PageMint declares a small, fixed set of Chrome permissions at install time: activeTab, scripting, storage, debugger, and downloads. The default runtime path still stays on browser print unless you turn high-fidelity rendering on in Settings. The current-session viewer stays inside that same local-only boundary today; selection mode is shipped today and saves through chrome.downloads only when the user explicitly presses Save on the toolbar. Specialized surfaces and durable local history remain later local-only slices, not shipped surfaces yet.
Default path permission baseline
Three permissions power the shipped local-first path.
Prepare that one tab for export
PageMint runs a small helper in the active tab to get the page ready for export. Triggered by your click, not by a hidden crawler.
Remember your settings locally
Paper size, margins, orientation, scale, layout, and the high-fidelity preference stay in extension storage on your device.
High-fidelity rendering
`debugger` is declared up front, gated behind a toggle, and only attached on demand.
Used only for Chrome's high-fidelity rendering
Chrome does not allow the debugger permission to be optional, so PageMint declares it up front. The debugger is only attached while the high-fidelity toggle is on and an export is running — never by default, and never from the main export button.
The debugger permission is declared at install, but PageMint only attaches Chrome’s debugger while a high-fidelity export is running.
Chrome shows a “PageMint started debugging this browser” banner on the tab while a high-fidelity run is active, and the banner disappears as soon as PageMint detaches.
The high-fidelity toggle in Settings is still the runtime preference gate, but free monthly limits or a local Pro entitlement decide whether the high-fidelity path is available on that browser.
What stays local
Local-first is still the headline for both paths.
The default export path stays minimum-permission at runtime: activeTab + scripting + storage, all on the page you already opened.
The default path still hands off to Chrome's print dialog, so you stay in control of the final save step.
High-fidelity mode keeps PDF generation local too. There is no hosted fallback or remote rendering service.
If you join the launch list, buy, restore, or contact support, PageMint only sends launch, checkout, license, support, and install metadata to its site service. Page content never leaves the browser.
Specialized surfaces (clean article, durable local history) remain planned local-first follow-ups; their flow lives behind explicit toggles, not silent autosaves.
Current-session viewer applies only to PageMint-managed PDF assets. Durable local history is still a later local-only slice, not a shipped retention surface today.
Clean article also stays local. PageMint rebuilds the reading surface in the active tab instead of sending the page to a hosted readability service.
Trust guardrails
The debugger permission never blurs the default story.
No silent permission prompt from the main export button. High-fidelity rendering is turned on deliberately from Settings.
Leaving the high-fidelity toggle off keeps the debugger permission declared but unused — PageMint never attaches Chrome’s debugger.
Pricing, privacy, terms, and support stay public on the site before purchase so the debugger permission story never doubles as hidden billing fine print.
Selection-mode save uses chrome.downloads only on the user's explicit Save click on the in-page toolbar; nothing auto-downloads in the background.
Specialized surfaces are planned only for named supported surfaces — ChatGPT, Gemini, DeepSeek, Reddit, and Pikabu once that slice ships.
Browser-print handoffs stay outside the current-session viewer because Chrome owns the final file on that path.
Durable local history is not shipped yet. When it lands, it stays local-only and still excludes browser-print handoffs.
Clean article stays separate from Exact article. Cleaner output means less site fidelity, not cloud processing.
Feeds, dashboards, and multi-pane app shells stay unsupported in clean article instead of being guessed into fake reader PDFs.
You can remove PageMint at any time from chrome://extensions to revoke every declared permission in one step.
Policy links
Trust copy is not a substitute for privacy or support terms.
Privacy policy covers local processing, billing metadata, retention, and contact details.
Terms of sale cover one-time pricing, refunds, taxes, install limits, and transfer limits.
Support covers license recovery, transfer help, refunds, and billing contact paths.