Security
How Snipper handles screenshots, network access, downloads, and release integrity.
Local-first by default
Snipper is designed so screenshot capture, annotation, clipboard copy, and normal editing stay on your device. Your screenshots are not uploaded to Snipper servers.
The free app works offline. Pro unlocks are validated against the licensing service, then restored locally on that device afterward.
Network requests
The free app makes no routine network requests during normal use.
When you activate a Pro key, the app sends the license key, a one-way device identifier hash, and the platform to the licensing service so device limits can be enforced. After successful activation, the app restores that state locally instead of rechecking on every launch.
Activation and deactivation requests are served from the official Snipper website. Those requests exist only for license activation, deactivation, and related purchase recovery flows.
Enterprise allowlist guidance
If your workplace firewall, proxy, or endpoint policy uses an allowlist, permit outbound HTTPS access to the official Snipper website and licensing host plus the Stripe checkout page used for purchase.
In practice that means allowing the official Snipper website domain for license activation and deactivation, and allowing the configured Stripe checkout domain when purchasing Pro through the website.
Snipper does not require inbound firewall rules, background telemetry endpoints, or a long list of third-party tracking domains for normal app use.
Telemetry and analytics
Snipper does not include in-app telemetry, ads, or user accounts.
Release integrity
Snipper installers are published through the official Snipper website and hosted download path.
If you download Snipper from the official site, you are getting the intended public installer for that release.
Current signing status
Snipper is distributed with a signed Windows installer using a verified OV code-signing certificate issued by Certum.
Browser reputation systems, SmartScreen, or stricter managed Windows policies can still caution on a newly published build for a period of time, even when the installer is correctly signed. That is a reputation-distribution issue rather than proof of tampering.
Questions or incident reports
If you need help validating a download or want to report a security concern, email snipperapphq@gmail.com.