SnapPlix – Privacy Policy

1Introduction

SnapPlix is a browser extension for Google Chrome that captures, annotates, and exports screenshots of web pages. This Privacy Policy explains what data SnapPlix collects, how it is stored, and what permissions are used.

2Core Principle

SnapPlix does not collect, transmit, or share any user data.

All data is processed and stored locally on the user's device. There are no external servers, no cloud services, no analytics, and no telemetry.

3Data Collected and Stored Locally

All data below is stored exclusively on the user's device.

Full-resolution screenshots — stored in the browser's IndexedDB database (spx-images). Used for editing and export. Stored as long as the corresponding history entry exists.
Screenshot thumbnails — compressed preview images (640px wide, JPEG) stored in chrome.storage.local for the history panel. Maximum 200 entries.
Screenshot metadata — page URL, page title, capture date, image dimensions, file size. Stored in chrome.storage.local.
Tags — user-created color-coded labels attached to screenshot entries. Stored in chrome.storage.local.
User preferences — theme, language, image format, quality, auto-copy/editor toggles. Stored in chrome.storage.local.
Timer state — temporary countdown timer data. Auto-removed after completion.
Schema version — internal migration version number.

chrome.storage.local

8 MB limit — thumbnails, metadata, tags, and preferences. Oldest entries evicted automatically at 200-entry limit (LRU policy).

IndexedDB

Full-resolution screenshots, browser-managed quota (hundreds of MB). Cleared on entry deletion or "Clear All History".

Deleting a history entry removes both the thumbnail from chrome.storage.local and the full image from IndexedDB. "Clear All History" removes everything from both storage locations. Uninstalling the extension deletes all data.

4Data NOT Collected

SnapPlix does not collect or process:

Personal information (name, email, phone, address)
Authentication credentials or account data
Browsing history beyond captured page URLs stored in screenshot metadata
Cookies or tracking identifiers
Analytics, usage statistics, or crash reports
Any data from pages the user does not explicitly capture

5Network Activity

SnapPlix makes zero network requests.

There are no external API calls, cloud uploads, sync services, third-party SDKs that phone home, remote code execution, or dynamic script loading.

The Content Security Policy enforces connect-src 'none', which blocks all outbound network connections from extension pages.

6Permissions and Their Purpose

activeTab	Capture the visible area of the currently active tab when the user clicks the capture button or uses a keyboard shortcut. Accesses the visual content of the active tab only at the moment of capture, only after an explicit user action.
storage	Store screenshot thumbnails, metadata, tags, and user preferences locally on the device using `chrome.storage.local`. Read/write to local extension storage only. No sync storage or external storage is used.
alarms	Schedule countdown capture timers (3/5/10 seconds) and periodic storage quota checks (every 30 minutes). No data access. Used solely for timing events within the extension.
downloads	Save captured and annotated screenshots to the user's disk via the browser's download manager. Initiates file downloads to the user's default download folder. Does not read existing files.
clipboardWrite	Copy screenshots to the system clipboard when the user clicks the "Copy" button. Writes image data to the clipboard. Does not read clipboard contents.

7Permissions NOT Requested

SnapPlix intentionally does not request:

scripting tabs webRequest notifications offscreen <all_urls> host_permissions cookies

scripting — no code is injected into web pages
tabs — full tab enumeration is not needed (activeTab is sufficient)
webRequest — no network traffic is intercepted or modified
notifications — no push notifications or alerts are shown
offscreen — image processing uses the native OffscreenCanvas API available in the Service Worker without this permission
<all_urls> or host_permissions — no access to arbitrary websites
cookies — no cookie access

8Content Scripts

SnapPlix does not use content scripts.

No code is injected into any web page at any time. All processing happens within the extension's own pages — popup, editor tab, and Service Worker.

9Image Processing

All image operations (thumbnail generation, cropping, format conversion, annotation rendering) are performed locally using:

OffscreenCanvas and createImageBitmap APIs in the Service Worker — for thumbnails, crop, and format conversion
Fabric.js canvas library in the editor tab — for annotations

No images are sent to external services.

10Third-Party Libraries

SnapPlix uses open-source libraries bundled within the extension:

React Zustand Tailwind CSS Fabric.js Lucide React zod nanoid date-fns

All libraries are included in the extension bundle. None of them make network requests or collect data.

11Data Retention and Deletion

Screenshot history is retained until the user manually deletes individual entries or clears all history
Automatic eviction removes the oldest entries when the 200-entry limit or 8 MB storage limit is reached
Uninstalling the extension removes all stored data from both chrome.storage.local and IndexedDB
Users can delete all data at any time via the "Clear All History" button in the History panel

12Children's Privacy

SnapPlix does not knowingly collect any data from children. The extension does not collect personal information from any user regardless of age.

13Changes to This Policy

Any changes to this Privacy Policy will be reflected in the updated version of the extension.