# SnapMate Privacy Policy

_Last updated: 2026-11-08_

SnapMate is a local-only screenshot capture and annotation tool. This policy describes exactly what the extension does and does not do with your data, matching its actual implementation.

## Summary

**SnapMate does not collect, transmit, or share any of your data with anyone, including its developer.** There are no servers involved. There is no account. There is no analytics or telemetry of any kind.

## What SnapMate accesses

- **The current tab, only when you act.** SnapMate uses Chrome's `activeTab` permission, which grants temporary access to the page you're on only when you click the extension icon or use one of its keyboard shortcuts. It has no standing access to your browsing and cannot read pages you haven't explicitly asked it to capture.
- **Screenshot pixel data**, to capture and stitch the image you asked for.
- **The page URL and title** of the tab you captured, so it can be shown back to you in the editor's Details panel and optionally included as a caption on export. This is stored locally with the project and is never sent anywhere.

## What SnapMate stores, and where

- **Screenshots and editor projects** (the image, your annotations, and the URL/notes you entered) are stored in your browser's local `IndexedDB`, scoped to the extension. This data never leaves your device.
- **Settings** (default capture mode, export format, annotation color, etc.) are stored in `chrome.storage.local`, also local to your device.
- Local storage is automatically pruned to the most recent screenshots to avoid unbounded disk use. You can also clear everything at any time by removing the extension or clearing its site data from Chrome's settings.

## What SnapMate never does

- It never sends screenshots, URLs, notes, or settings to any server — SnapMate has no backend.
- It never requires or uses an account, sign-in, or API key.
- It never includes analytics, crash reporting, or any third-party tracking SDK.
- It never reads your browsing history.
- It never runs on pages you haven't explicitly chosen to capture (no broad `<all_urls>` content script).
- It never loads remotely hosted code; everything it runs is packaged in the extension itself.

## Permissions, in plain terms

| Permission | Plain-language purpose |
|---|---|
| `activeTab` | Only works on the tab you're currently looking at, only after you click the icon or press a shortcut. |
| `scripting` | Lets SnapMate inject its capture/selection helper into the current tab on demand. |
| `storage` | Saves your settings and last-used capture mode on your device. |
| `downloads` | Lets you save an exported image to your Downloads folder. |

SnapMate does not request `host_permissions`, `<all_urls>`, `webRequest`, `history`, `cookies`, `tabs` (the broad version), or the `debugger` permission.

## Changes to this policy

If SnapMate's behavior ever changes in a way that affects this policy, this document will be updated alongside the extension's version history before the new version is published.

## Contact

This is an independent, local-first project. If you have questions about this policy, please reach out through the extension's Chrome Web Store listing support channel once published.