Privacy Policy

Last updated: October 23, 2026

InSnap is built to be local-first: your screenshots, recordings and history stay on your computer. This policy explains the small amount of information we do handle — for licenses, accounts and the optional Cloud service — and your choices. In this policy, “InSnap”, “we” and “us” mean InSnap, who can be reached at [email protected].

1. The short version

Screenshots, recordings, annotations, history and text recognition (OCR) are processed and stored on your device.
The free app needs no account. Activating InSnap Pro and using InSnap Cloud need an InSnap account, created with your email address or with Google sign-in. We don’t run advertising or behavioural analytics: the app sends only an anonymous install heartbeat (a random ID, the app version and platform — see the table below). This website’s public pages use Microsoft Clarity for anonymous visit statistics.
Files are uploaded only when you use the Share button with an active InSnap Cloud subscription.
We never sell your personal information.

2. Information that stays on your device

The following is created and stored locally and is not sent to us:

Captured images, screen recordings, GIFs and guides, with their annotations.
Your capture history, including the name of the app and window title you captured and — if you leave “record source page address” on in Settings — the address of the web page that was open. You can turn this off or clear history at any time.
Text recognized from images (OCR). Recognition runs with models bundled inside the app; no image is sent to a server.
Your settings and hotkeys.

3. Information we collect, by feature

Feature	What we receive	Why
Buying Pro or Cloud	Your email address and order details (order ID, product, status) from our payment provider. We do not receive your card number.	To deliver your activation code, provide support and handle refunds.
Activating Pro	The activation code (stored only as a salted hash), a one-way hash derived from your computer’s hardware identifier, device name, platform, app version, your approximate country and a salted hash of your IP address.	To issue and renew your license, enforce the device limit, prevent code sharing and detect abuse.
InSnap account	Your email address, one-time sign-in codes and session tokens (stored hashed); if you choose Google sign-in, the verified email address and an account identifier that Google returns (we do not receive your Google password and do not access any other Google data); which licenses and devices belong to your account; and your Cloud subscription status and storage usage.	To sign you in, tie your Pro license to your account, show it to you on the website, provide the service and manage your subscription.
Signing in from the app	When you click “Sign in” in the app, a short-lived request containing your device name, platform, app version and approximate country is created so you can approve it on our website.	To let you sign in to the desktop app without typing credentials into it.
This website’s account area	Your sign-in session is kept in your browser’s local storage on insnap.app so you stay signed in. It is not shared with anyone, and there are no tracking cookies. Signing out removes it.	To keep you signed in and let you manage your license and uploads.
This website’s public pages	We use Microsoft Clarity, a web-analytics service, on our public marketing pages (not on the sign-in, account or support pages). Clarity sets first-party cookies and records how visitors use the pages — clicks, scrolling, page views and approximate location — together with technical data such as device type, browser and IP address, to produce session replays and heatmaps. Clarity masks text typed into form fields. Microsoft processes this data as our service provider; see the Microsoft Privacy Statement. You can block it with your browser’s tracking protection or a content blocker, or by enabling Do Not Track / Global Privacy Control.	To understand which pages are useful and fix usability problems.
Uploading with Cloud	The files you choose to upload, plus their size, type, upload time and share-link settings (expiry; an optional password, stored hashed). Anyone with a link can open that file unless you set a password. Uploaded files are reviewed for malicious content.	To store your files, serve your share links and keep Cloud free of malicious content.
Update checks	A standard web request to our update server (IP address, app version and operating-system version in the request, as with any download).	To tell you when an update is available and deliver it.
Using the app (install heartbeat)	A random installation ID generated by the app, the app version, your platform (macOS or Windows) and your operating-system version. It is sent once on first launch, then about once a week. It is not linked to your account, device name or IP address, contains no screenshots or usage details, and we keep only this install record and daily activity counts.	To count how many people use InSnap, how many installs are active, and which versions are in use, so we can prioritise fixes and plan updates.
Support emails	Whatever you send us, including your email address.	To answer you.
Product emails	Your email address, your display name (if you set one), and whether you have unsubscribed. We send occasional emails introducing InSnap’s features, Pro and Cloud only to people who created an account and have not bought anything yet, and usually no more than about once a month. We do not track whether you open these emails or click their links.	To tell you about the product. Every such email has an unsubscribe link (and a one-click unsubscribe in mail apps that support it); once you unsubscribe we stop sending them. Emails about your account — sign-in codes, activation codes, receipts and support replies — are not affected.

Apart from Microsoft Clarity on our public pages (described in the table above), this website loads no analytics, fonts, scripts or trackers from third parties, and the sign-in, account and support pages load none at all. Like any web host, our infrastructure provider (Cloudflare) processes technical request data such as IP address and user agent to deliver the site and keep it secure.

4. System permissions

On macOS, InSnap may ask for Screen Recording, Accessibility, Input Monitoring, Microphone and Camera access. On Windows, screen capture needs no permission, and the microphone and camera follow the system privacy settings. These permissions are used only on your device for the feature that needs them (see the download page). The data they provide is not transmitted to us.

5. Content review

We review the resources you upload to InSnap Cloud, and we block or remove malicious ones and content our Terms prohibit, such as sexually explicit or other adult material. If you think we made a mistake, email [email protected].

6. Payments

Purchases are processed by our payment provider, which collects and processes your payment details, handles taxes and sends receipts under its own privacy policy. We receive only the order information described above.

7. How we use information

To provide, secure and support InSnap, your license and the Cloud service.
To prevent fraud, abuse and unauthorized sharing of license codes.
To comply with legal, tax and accounting obligations.

We do not use your information for advertising and we do not build profiles about you.

8. Who we share it with

We use a small number of service providers (processors) to run InSnap:

Cloudflare — hosting, network delivery, database, file storage for Cloud, and email delivery of sign-in codes and license emails.
Google — only if you choose “Continue with Google”: Google authenticates you and tells us your verified email address. Google’s own privacy policy applies to that sign-in.
Our payment provider — payments, taxes and receipts.

We may disclose information if required by law or to protect the rights, safety and security of our users and service. We do not sell or rent personal information.

9. How long we keep it

License records are kept while your license is valid and afterwards as long as needed for accounting, tax and legal obligations.
Sign-in codes expire after 10 minutes.
Cloud files are kept while your subscription is active. After it ends you have 30 days of read-only access, and files are deleted 90 days after the subscription ends.
Share links expire on the date you choose in the app (7 days by default, or never) and stop working when you delete the file or your subscription lapses.
Blocked files are removed from your account and deleted after a short period. We keep a record of the decision (not the file) for moderation.
Deleting your account removes your Cloud account, uploaded files and share links.
Infrastructure logs are kept by Cloudflare for its standard retention period.

10. Security

Connections to our services use HTTPS. Activation codes, sign-in codes and refresh tokens are stored only as salted hashes, and license tokens are digitally signed. The account area of this website runs under a strict content-security policy with no third-party scripts. No method of transmission or storage is perfectly secure, but we work to protect your information and fix problems promptly.

11. Your choices and rights

Depending on where you live (for example under the GDPR, UK GDPR or CCPA), you may have the right to access, correct, export or delete your personal information, to object to or restrict certain processing, and to withdraw consent. To exercise a right, email [email protected]. You can delete your Cloud account yourself under Settings › Account & license. We process information on the basis of contract (to provide what you purchased), legitimate interests (security and abuse prevention) and legal obligation.

You may also lodge a complaint with your local data-protection authority.

12. International transfers

Our providers operate globally, so your information may be processed in countries other than your own, including the United States. Where required, we rely on appropriate safeguards such as the providers’ standard contractual clauses.

13. Children

InSnap is not directed to children under 13 (or under 16 where the law sets a higher age), and we do not knowingly collect their personal information. If you believe a child has given us information, contact us and we will delete it.

14. Changes to this policy

We may update this policy as InSnap changes. We will change the “Last updated” date above and, for significant changes, tell you in the app or by email.

15. Contact

Questions about privacy? Email [email protected].