Privacy Policy
Last updated November 17, 2026.
This policy describes data handling in the Snipvera macOS app and on snipvera.online. For privacy questions or requests, contact [email protected].
Screen capture and local processing
Snipvera uses macOS Screen Recording permission to capture the area, window or display you request. You can review or revoke this permission in macOS System Settings. Capturing, annotation, image effects, styling and supported offline text recognition run on your Mac. Confirming a cloud upload sends the rendered image to the configured Snipvera service.
Local history and sensitive information
When history is enabled, original screenshots, editable annotation documents and thumbnails are stored in the app’s local Application Support storage. Pending upload drafts may also be stored locally for retry. You can manage captures and retention in the app. Exported files, clipboard contents and copies sent to other applications have their own lifecycles.
Blackout covers pixels in rendered output. Editable local history still retains the original image. Blur and pixelate can leave recoverable details. Review the final output before sharing and separately delete local originals when necessary. OCR results appear in the extraction window and are placed on your clipboard when you choose to copy them.
Cloud uploads and public share links
A confirmed upload sends the rendered image, its size, type, checksum and upload-management information to the server. The service validates and re-encodes supported images and stores image bytes in its database. The app receives a randomly generated share URL. Anyone who has a live URL can view and copy its image. Signed-in uploads may be associated with your account.
New cloud images expire 15 days after upload creation. Expiry checks prevent access to expired images, and the running server clears expired image bytes through periodic cleanup. You can revoke a link earlier through Cloud Uploads. Temporary ownership and status records may remain briefly to support retries and cleanup. Deleting local history does not automatically revoke a cloud link.
Share pages and image responses instruct search engines not to index them. This instruction does not restrict access by someone who has the URL or remove copies already downloaded by recipients. Database backups and infrastructure logs can have separate retention schedules; contact us with a specific deletion question.
Google accounts and authentication
If you choose Google sign-in, Snipvera receives your Google account identifier, verified email address and name. These identify your account and associate signed-in uploads with it. Snipvera uses Google’s sign-in flow rather than collecting your Google password. Website sessions use HttpOnly cookies, and app sessions are stored in macOS Keychain. Sessions normally expire after 30 days. Sign out of the app and website separately to revoke their respective sessions.
Short-lived login state and one-time app handoff records support authentication and expire after ten minutes. Session credentials and upload ownership capabilities are stored as hashes on the server. You can also review Snipvera’s connection from your Google account settings. Google explains its own processing in the Google Privacy Policy.
Service operation and security
Requests necessarily expose network information to the hosting infrastructure, such as IP addresses, requested paths and browser or client headers. The application uses upload metadata and hashed rate-limit buckets to validate transfers, enforce limits and prevent abuse. Hosting, reverse-proxy and database providers may process operational logs and backups as part of running the service. We do not require screenshot contents to be included in a support request.
Third-party services and optional support
Update checks contact GitHub Releases. Downloading an installer also uses GitHub infrastructure. Image search prepares an image for Google Images or TinEye; those providers receive it when you submit it through their browser interfaces. Each destination applies its own policies. See GitHub’s privacy statement and TinEye’s privacy policy.
The optional Ko-fi support button opens an external service. Ko-fi and its payment providers process payment information under their own policies. Information supplied with a support payment or message may be visible to the creator. See the Ko-fi privacy policy. Ordinary browsing of Snipvera does not require making a payment.
Support messages and privacy requests
If you email us, we receive your email address and the information you include. We use this correspondence to respond and investigate the issue. Avoid sending passwords, access tokens or private screenshots. You can request access to, correction of, or deletion of account information by emailing [email protected]. We may need to verify that you control the relevant account before acting on a request.
Privacy rights and any exceptions depend on the law applicable to you and the service. Some information may need to be retained for security, legal obligations or resolving a dispute. Account deletion requests are handled through support; signing out alone does not delete the account or all associated uploads.
Children, changes and contact
Snipvera is a general-purpose productivity tool. Use of account and online sharing features must meet the age and consent requirements applicable where you live and those of the sign-in provider. Please contact us if you believe a child’s personal information has been provided improperly.
We may update this policy as the app and service change. The date above identifies this version. Questions, privacy requests and reports can be sent to [email protected]. Read the Terms of Use for conditions governing the app and online service.