Paginaut Privacy Policy

Last updated: 2026-05-14

Overview

Paginaut is a browser extension for screenshots, OCR text extraction, QR decoding from a selected on-screen region, character/word statistics from user-provided text (including optional clipboard paste), and transliteration.
We are committed to minimizing data collection and keeping processing local.

What data Paginaut processes

Paginaut may process the following content, only when triggered by the user:

• Visible web page pixels for screenshot capture
• User-selected region pixels for OCR or QR decoding (same style of region selection; QR payload is derived locally)
• Text entered by the user in transliteration tool
• Text pasted or typed in the Character count tool (processed locally in the extension window; optional one-time clipboard read when opening that tool)

Data storage

Paginaut stores data locally in browser extension storage:

• Feature flags/settings
• Popup tool order (Favorites / Screenshot / Text columns from Options drag-and-drop; key popupToolLayout) — UI layout only, not page content
• Language preference override
• Most recent captured image / OCR source / last QR crop (temporary app state), or a small preview image when a long full-page capture produced several files saved directly to Downloads
• Optional short-lived metadata describing the last capture (for example multipart segment count and filename prefix)

No user account or identity profile is created by Paginaut.

Data sharing

Paginaut does not sell user data.

By default, Paginaut does not transmit screenshot/text content to external application servers for processing.
Operations are intended to run locally inside the extension runtime.

Offline use (extension scope)

Paginaut does not rely on an internet connection for its core processing: capture, stitching, saving to Downloads, clipboard copy, bundled OCR and QR (jsQR) libraries, local text statistics (Character count), and UI localization files shipped inside the extension all run locally.
Opening or refreshing a remote website in a tab still follows normal browser rules (that tab may need a network). Using the extension on pages that are already available offline (or local documents, where Chrome permits) does not add a separate online dependency for Paginaut itself.

Permissions usage summary

• activeTab, tabs, scripting: capture and region selection workflows (including scroll-stitch full-page helpers in the active tab when you run full-page capture)
• Host access (<all_urls>): allows the same user-triggered flows on whichever site you have open; the extension does not collect browsing history or run unattended scraping. It only acts when you use a Paginaut action on the current tab.
• debugger: optional legacy full-page screenshot capture via Chrome DevTools Protocol (when that feature is enabled in Options; default full page uses scroll-stitch without debugger)
• downloads: save generated files at user request; for very tall full-page captures, also save numbered segment files when the user runs full page capture (scroll-stitch or legacy)
• clipboardWrite: copy image/text at user request
• clipboardRead: optional one-time plain-text read when opening Character count to pre-fill the editor (user-triggered from popup; no continuous monitoring)
• storage: save settings, popup layout, and local state as described above

User control

Users can:

• Enable/disable features in Options (feature flags)
• Reorder tools and favorites in Options (stored only as layout preferences)
• Change UI language override (Auto/English/Serbian)
• Decide when to capture/copy/save content

Data retention

Stored data remains in local extension storage until:

• user overwrites it via new actions,
• user changes settings,
• user removes extension data or uninstalls the extension.

Contact

If you have privacy questions, contact the publisher via the support contact listed in Chrome Web Store.