Privacy policy

Last updated 31 October 2026

Snapline is a screenshot app that runs on your Mac, Windows PC or Linux computer. It has no servers, no accounts of its own, no analytics and no tracking. Your screenshots are read only on your computer. An image leaves your computer only when you choose to upload, search, email or share it, and then it goes only to the place you chose.

This policy covers the Snapline apps for macOS, Windows and Linux, and this website. Snapline is made by Barayuda (“we”, “us”).

What Snapline does on your computer

Capturing the screen, drawing, auto-hide of sensitive data and Copy Text all run on your computer. On a Mac they use Apple's built-in frameworks (ScreenCaptureKit and Vision). On Windows they use Windows' built-in text recognition (Windows.Media.Ocr) and face detection. On Linux they use Tesseract, which is part of Snapline; Linux has no face detection yet.
No screenshot and no recognised text is sent to us or to anyone else to be read, analysed or stored.
Snapline does not collect usage data, crash reports or any other telemetry.
Your settings are stored on your computer: on a Mac in Snapline's preferences, on Windows in %APPDATA%\Snapline\settings.toml, on Linux in ~/.config/Snapline/settings.toml. Secrets (bucket keys and your Google sign-in) are stored in the macOS Keychain, in Windows Credential Manager, or on Linux in the desktop keyring (GNOME Keyring or KWallet).
On Windows, Edit, Share and Print write a temporary copy of the screenshot to %TEMP%\Snapline, so the app you open it in can read it. Snapline does not delete these copies; Windows Storage Sense or Disk Cleanup can, or you can delete the folder yourself. On Linux, Edit, Share and Print write the copy to ~/.cache/Snapline/temp.

When an image leaves your computer

Only when you ask for it:

Upload sends the image to the destination you set up: your own S3-compatible bucket, or your own Google Drive. Anyone with the link can view it.
Search similar images uploads the image there first, then opens Google Lens or TinEye in your browser with that link. Those services handle the image under their own privacy policies.
Email (Mac) hands the file to your mail app. Nothing is sent until you send the email.
Share (Windows) hands the file to the app you pick in the Windows Share window, such as Outlook or Teams. That app handles it under its own terms and privacy policy, and nothing is sent until you send it there. Share (Linux) opens a new email with the file attached in your mail app; nothing is sent until you send it.

We never receive these images. The services you upload to (for example Google, Amazon Web Services or Cloudflare) handle them under their own terms and privacy policies.

Google account data

If you choose Google Drive as your upload destination and sign in with Google, Snapline asks for these permissions:

See, edit, create and delete only the specific Google Drive files you use with this app (drive.file). Snapline uses it to create a “Snapline” folder in your Drive, upload the screenshots you choose to upload, and set them to “anyone with the link can view” so the link works. Snapline cannot see any other files in your Drive.
Your email address and basic sign-in (openid, email). Snapline uses it only to show which Google account is signed in, in Preferences (Settings on Windows).

How this data is handled:

Google sign-in happens in your own browser. Snapline never sees your Google password. It receives the sign-in result on a local address on your computer (127.0.0.1).
The sign-in token is stored in the macOS Keychain or Windows Credential Manager, and your email address in Snapline's settings, both only on your computer. They are sent only to Google, to upload files and to sign out.
We do not receive, store, sell or share your Google data. It is not used for advertising, it is not read by people, and it is not used to train AI or machine learning models.

Snapline's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

To remove access, click Sign out in Snapline's Preferences (Settings on Windows), which also revokes Snapline's access at Google. You can also remove it at any time on your Google Account permissions page. Files you uploaded stay in the “Snapline” folder in your Drive until you delete them.

S3-compatible storage

If you use an S3-compatible bucket, your access key and secret are stored in the macOS Keychain or Windows Credential Manager. They are used only to sign upload requests sent directly to the endpoint you entered, over HTTPS.

This website

This website is a set of static pages. It uses no cookies, no analytics and no third-party scripts or fonts. If you pick light or dark mode with the theme switch, your browser remembers that choice in its own storage; it is never sent to us. It is hosted on Netlify, which may keep standard server logs, such as IP addresses and browser type, to run and protect the service. See Netlify's privacy policy.

Children

Snapline is not directed at children under 13, and we do not knowingly collect any data from them. Snapline does not collect personal data from anyone.

Changes to this policy

If this policy changes, the new version will be posted on this page with a new date. The history of changes is in the source repository.

Contact

Questions about privacy: open an issue at github.com/barayuda/Snapline/issues.