PRIVACY

Privacy built into the workflow.

PageSnapper processes screenshots locally in your browser and does not upload captured content to PageSnapper or Mashhoori servers.

Last updated:
Device Sandbox

Local processing

Screenshot captures, vector annotations, privacy masking, and file exports execute locally inside your Chrome browser.

Zero Telemetry

No tracking

PageSnapper contains no third-party tracking scripts, analytics beacons, behavioral profiling, or advertising SDKs.

Zero Cloud Transmission

No screenshot uploads

Your captured images and edited canvas content are not sent to PageSnapper servers, Mashhoori servers, or cloud storage.

SECTION 01

Overview

PageSnapper is a local-first browser screenshot extension developed and published by Mashhoori (https://getpagesnapper.com). PageSnapper is engineered to help you capture, annotate, obscure, compose, and export screenshots directly within your Google Chrome browser without transmitting your visual data to external servers.

This Privacy Policy explains how PageSnapper handles browser interactions, processes image data, manages browser permissions, and utilizes local storage mechanisms.

SECTION 02

Information PageSnapper Processes

PageSnapper operates strictly on a user-initiated basis. The extension processes visual information from your active browser tab only when you explicitly trigger a capture action (such as selecting Full Page, Selected Area, Element, or Visible Area capture).

PageSnapper does not passively monitor, read, log, or collect your web browsing history, keystrokes, form submissions, or webpage content while you browse. Visual webpage pixels are captured only at the exact moment you request a screenshot.

SECTION 03

Screenshot Content

All screenshot processing—including image stitching, raster rendering, vector annotations, blur, pixelate, permanent redaction, canvas composing, and file format conversion—takes place locally inside your browser sandbox on your device.

Captured screenshot content and edited graphics are not transmitted to PageSnapper servers, Mashhoori servers, advertising networks, analytics services, or third-party cloud storage platforms.

SECTION 04

Temporary Local Storage

Under Google Chrome's Manifest V3 extension architecture, background service workers are ephemeral and may be suspended by the browser during operation. To ensure that newly captured image data is reliably transferred from the capture helper into the full-tab editor without data loss, PageSnapper may temporarily write captured screenshot data to your browser's local client-side IndexedDB storage.

TECHNICAL WORKFLOW

Local Browser Handoff Lifecycle

1
User CaptureVisual pixels captured in active tab
2
Local IndexedDBTransient record stored on device
3
Editor LoadCanvas initializes with image
4
PurgedHandoff record deleted from DB

Handoff Record Lifecycle:

  • Immediate Removal: Temporary handoff records are removed from IndexedDB immediately after the editor successfully reads and initializes the image on the canvas.
  • Opportunistic Purging: If an editor tab is closed before completing initialization, unconsumed or expired temporary records are cleaned up opportunistically during subsequent extension activity.
  • Strictly On-Device: This temporary IndexedDB storage exists within your local browser profile. PageSnapper does not sync, back up, upload, or transmit these temporary records to PageSnapper, Mashhoori, or third-party servers.
SECTION 05

Chrome Extension Permissions

PageSnapper requests only the minimum set of permissions necessary to execute its user-initiated screenshot, editing, and export capabilities. Below is an explanation of each permission requested in our extension manifest:

activeTab

Grants temporary access to the currently active webpage only when you click the PageSnapper extension popup or initiate a capture. It does not grant continuous background access to other tabs or browsing sessions.

scripting

Allows the extension to inject lightweight visual selection helpers and scroll handlers into the active tab to execute element inspection, rectangular crop overlays, and full-page scroll-and-stitch capture.

offscreen

Used for browser-local canvas processing and image stitching required by screenshot capture workflows under Manifest V3.

clipboardWrite

Used strictly when you click "Copy Image" or "Copy to Clipboard" to place the rendered PNG image onto your system clipboard for quick pasting into external applications.

Explicit Limitation: PageSnapper does not request broad host permissions, does not request <all_urls> access, and cannot inspect or capture tabs in the background without user interaction.

SECTION 06

Data Sharing

Because PageSnapper processes all captures locally and does not transmit captured images or browsing content to any server:

  • PageSnapper does not sell, rent, or monetize screenshot or browsing data.
  • PageSnapper does not transmit screenshot content or metadata to advertisers or commercial data brokers.
  • PageSnapper does not share your captures with third parties for marketing, profiling, AI model training, or any unrelated purpose.
SECTION 07

Analytics & Tracking

PageSnapper v1.0 is built with privacy by design and contains:

  • No Advertising SDKs: Zero commercial advertising code or display ad trackers.
  • No Behavioral Analytics: Zero telemetry suites tracking individual user actions or webpage visits.
  • No Tracking Pixels: Zero remote tracking pixels, web beacons, or fingerprinting scripts.
  • No Third-Party Scripts: Zero remote analytics libraries running inside the extension package.
SECTION 08

Data Retention

Data processed by PageSnapper follows strict local lifecycles:

  • Active Editor Sessions: Your active screenshot canvas and vector annotations exist in browser memory only for the duration of the editor tab session. Closing the editor tab discards unsaved canvas memory.
  • Temporary Handoff Records: Transient IndexedDB records are deleted upon editor initialization or cleaned up opportunistically as described in Section 04.
  • Exported Files: When you download a PNG, JPG, WebP, or PDF file, the file is saved directly to your local file system (such as your browser's Downloads folder) and is under your complete control thereafter.
SECTION 09

Children's Privacy

PageSnapper is a general-utility browser extension and does not knowingly collect, store, or solicit personal information from children. Because the extension does not collect personal data or require account creation, no personal information from children is stored or processed on external servers.

SECTION 10

Website Hosting & Technical Logs

This section applies specifically to your visits to the public PageSnapper website (getpagesnapper.com), which operates separately from the PageSnapper Chrome extension.

The PageSnapper website is a static website and does not use Google Analytics, Meta Pixel, Hotjar, commercial advertising trackers, or third-party behavioral analytics scripts.

The website is hosted using Hostinger web infrastructure. When you visit the website, standard web server and content delivery infrastructure may automatically receive and process technical network request information necessary to deliver, secure, and operate the site. This technical information may include:

  • IP Address & Network Data: Internet Protocol (IP) address and approximate geographic region or country derived from network routing.
  • Browser & System Information: Browser type, version, operating system, and user-agent header.
  • Request Details: Requested page URL, HTTP referrer, HTTP method, and exact timestamp of the request.
  • Server Response: HTTP status codes, payload size, and server diagnostic or error messages.

This standard infrastructure processing is handled at the web hosting layer to maintain website availability, mitigate automated abuse, and ensure technical security. It is completely separate from the PageSnapper browser extension, which processes all screenshots locally on your device without transmitting visual data to our website or hosting servers.

SECTION 11

Changes to This Policy

We may periodically update this Privacy Policy to reflect technical updates in browser extension requirements, new local features, or regulatory standards. When updates are published, the "Last updated" date at the top of this document will be revised accordingly.

SECTION 12

Contact & Support

If you have questions regarding this Privacy Policy or PageSnapper's local-first architecture, please reach out to our team:

PageSnapper

A product by Mashhoori