Privacy Policy

Snapper is engineered to keep your desktop captures completely private.

Last Updated: June 9, 2026

We believe that your screen content is yours alone. That is why Snapper is built as an offline-first utility. All captures, edits, annotations, and processing are done entirely on your local machine. No screenshots are ever sent to external servers unless you explicitly configure and authorize it.

1. Screen Data Processing

Snapper intercepts visual content only when you trigger a capture shortcut. This content is stored exclusively in system RAM while you annotate, crop, or format it in the Editor.

  • No screenshot data is written to disk until you click the Save button.
  • No background analytics, metadata collection, or screenshot telemetry is active.
  • When you close the Annotation editor, any unsaved visual buffers are securely scrubbed from system RAM.

2. Required System Permissions

To operate natively on macOS, Snapper requests two permission grants. Here is exactly what they are used for:

Screen Recording Permission

Allows Snapper to capture the display buffers and detect bounding boxes of active macOS windows. This grant is used 100% locally and does not transmit network packets.

Accessibility Permission

Required only when using the **Scroll Capture** feature. It permits Snapper to simulate mechanical mouse wheel scroll inputs on browser tabs or documents so that it can automatically scroll and stitch captures together.

3. Optional Cloud Uploads

Snapper supports direct uploads to ImgBB to allow easy screenshot link sharing.

  • This feature is **disabled by default**. No network requests are made to ImgBB unless you enter your own API key in *Settings → Upload*.
  • When you click **Upload**, only the currently active, annotated screenshot is pushed to the ImgBB server.
  • Any image uploaded is subject to ImgBB's terms of service and privacy settings. We recommend checking your ImgBB account settings to control auto-deletion rules.

4. License Verification

To verify license keys and coordinate device transfers, Snapper communicates with this server:

  • The verification request sends the **License Key** and a cryptographically hashed **Hardware UUID** to block multi-device exploitation.
  • No details about your screen, location, or usage habits are gathered or transmitted during verification.
  • License transfers are only executed after you click a **magic link** delivered to the email used at checkout.

If you have any questions or security concerns about Snapper, feel free to inspect the source code in our GitHub repository.