Privacy Policy
Snapper is engineered to keep your desktop captures completely private.
This Privacy Policy describes how Thomas Agius ("we", "us", or "our") collects, uses, and discloses your information in connection with the Snapper macOS application ("Snapper") and the website.
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:
3. Google API Services User Data Policy
Snapper offers an optional integration with Google Drive to allow you to save and upload your screenshots directly to your own Google Drive storage.
- Information Accessed: To upload your screenshots, Snapper requests authorization to write files to your Google Drive. This uses the narrow
https://www.googleapis.com/auth/drive.filescope, meaning Snapper can only access, view, or modify files that were explicitly created or uploaded by the Snapper app. It cannot read, edit, or delete any other files in your Google Drive. - Local Credentials: All OAuth tokens and authorization details are stored securely on your local device (e.g., in macOS Keychain). We do not collect, store, or transmit your authentication credentials to our own servers.
- Data Usage: Any data retrieved from Google APIs (such as upload confirmations or file IDs) is used exclusively to facilitate the saving process and display the uploaded file link inside the Snapper application. We do not use this data for advertising, profiling, tracking, or any other purposes.
- No Data Sharing: Snapper does not share, transfer, or sell your Google user data or screenshots to any third parties. All screenshot files are uploaded directly from your local device to your Google Drive via secure HTTPS connections.
- Limited Use Disclosure: Snapper's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
4. 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.
5. 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.
6. Contact Information
If you have any questions, concerns, or requests regarding this Privacy Policy or how your data is handled, please contact:
- Developer: Thomas Agius
- Email: agiusthomas@gmail.com