Your screenshots
stay yours.

Local files

Shnapp keeps your capture library, editable originals, rendered previews, preferences, and update-check state on your PC. Direct-download editions use %LOCALAPPDATA%\Shnapp by default; an advanced --data-root launch option can move it elsewhere. The Microsoft Store edition uses its own Windows LocalCache folder, which Windows excludes from device backup. Quit a direct-download copy before the Store edition's first launch. It then copies an existing library into that folder and leaves the original files in place.

When you copy a PNG, Shnapp places it on your Windows clipboard. When you choose Save, the exported PNG goes to the location you select. Shnapp does not automatically upload captures to us or GitHub.

Network and updates

Portable ZIP copies check the repository’s latest GitHub Release over HTTPS at most once per day; you can also check from Settings. The request contacts api.github.com and includes an app user-agent and, when available, an ETag. Shnapp stores update-check details locally. A portable ZIP copy downloads a verified update from github.com into its app folder and starts it on the next restart. Velopack installer copies also check GitHub-hosted releases in the background, normally once a day across restarts; a failed check can retry after an hour, and you can check on demand in Settings → About & Updates. They download an available update and prepare it for restart. These requests do not send your captures.

Scoop, WinGet, and Chocolatey installations use their package managers for upgrades after you choose the update action. A Microsoft Store package asks Windows Store services to check and may download an update in the background; choosing Update now asks Store to install it. Sideloaded Store packages may need updates from their original source.

The site itself has no analytics script or tracking cookies. As with any website, your browser makes requests to the site host to load the page and images. When you open the download page, your browser also requests the latest release feed from raw.githubusercontent.com over HTTPS to show the current version, release notes, and download links. GitHub may receive your IP address and standard request details. This request does not include your captures.

Sharing and feedback

Shnapp opens the Windows Share sheet only when you choose Share. It gives Windows the finished PNG and, when available, a thumbnail. Share and Copy path create separate local PNG snapshots so later edits cannot change files another app may read. Snapshots become eligible for cleanup after seven days; deleting a capture also attempts to remove its snapshots. A file another app is using may remain until a later cleanup. You choose the destination; that destination’s privacy practices apply after you share.

Links to bug reports and feature requests open GitHub when the public issue tracker is available. GitHub handles information you submit there under its privacy statement. If you email us, your message is handled by our email provider. Please avoid including sensitive screenshots in a public issue.

Your choices

You choose what to capture, copy, export, and share. For a direct-download edition, quit Shnapp and delete %LOCALAPPDATA%\Shnapp, or the folder you set with --data-root, to remove its local library and preferences. The Microsoft Store edition keeps a separate copy in its Windows app-data folder; removing or resetting that edition may delete its copy. Back up editable captures before removing it. PNGs saved elsewhere must be deleted separately.

For a capture containing sensitive details, use opaque Cover on the exported image. Blur and Pixelate may leave text or shapes recognizable. The editable original remains in your local library until you delete it.

Contact

Shnapp is created by Erik Zettersten and published by Nenvy LLC. For privacy or security questions, write to erik@zettersten.com.