Skip to main content
Klipp
Privacy

Privacy Policy

Last updated: August 9, 2026

Summary

Klipp is a native macOS menu-bar app. It keeps a history of what you copy and the screenshots you take on your Mac, in a database encrypted with a key held in your Keychain, and it reads and analyses images on-device. By default nothing is uploaded anywhere. Klipp has no servers of its own, no analytics, and no tracking, and your data is never sold or shared. There is no Hagerling-operated backend that receives your data. Cloud upload and location tagging are optional and off until you turn them on.

1. Who we are

Klipp is a native macOS application developed by Carl Hagerling (Lehune AB, Sweden). Contact: carl@hagerling.se.

2. What data Klipp handles

Klipp works with the clipboard items and screenshots you capture, information it derives from them on your Mac, and the settings you configure. All of it is stored locally on your device:

  • Clipboard items and screenshots

    The text and images you copy, and the screenshots you take, are held on your Mac. Their text and details go into an encrypted local history database; the captured image files themselves are kept as ordinary files in Klipp's own application support folder, protected by macOS file permissions rather than by Klipp's own encryption. Klipp never captures passwords or clipboard content marked as concealed by other apps, and does not read that content at all.

  • Information derived on-device

    Klipp reads the text inside images using macOS's built-in on-device text recognition, and it derives colours, links, tags, and the name of the app a capture came from. This analysis happens entirely on your Mac.

  • Optional location tags

    If you turn on location tagging, Klipp adds a coarse, city-level location tag to new captures using your Mac's location services. It stores only city, region, and country labels, never precise coordinates, and it is off until you enable it.

  • Your tokens and settings

    If you connect an upload destination, its access token, plus your preferences, are stored on your device so Klipp can upload where you asked it to.

Klipp does not collect telemetry, analytics, crash reports, advertising identifiers, or any device identifiers.

3. Where your data goes

By default, your data stays on your Mac and goes nowhere. Uploading is optional: if you connect an upload destination, Klipp uploads captures only to the one you configure, such as your own Notion workspace or a folder on your Mac, and can copy a hosted link to your clipboard instead of the file. Klipp runs no server of its own, there is no Hagerling-operated backend involved, and your data is never sold or shared with anyone. When you upload, your images travel directly from your Mac to the service you chose. The one other case where anything leaves your Mac is location tagging: if you switch it on, your approximate coordinates are sent to Apple's geocoding service to turn them into a city name. Your captures are never part of that.

4. How your data is protected

  • Encrypted local history

    Your clipboard and screenshot history is stored in an encrypted local database on your Mac. The encryption key is held in the macOS Keychain, marked available only when your Mac is unlocked and never synced off the device. The captured image files stored alongside it are not separately encrypted by Klipp.

  • Tokens kept in the Keychain

    Any upload access tokens you add live in the macOS Keychain, device-only and non-syncing, so they never leave your Mac.

  • On-device analysis only

    Text recognition, colour sampling, and link detection all run locally on your Mac. No image or its contents is sent anywhere for analysis.

  • Nothing captured in the background

    Klipp never captures passwords or clipboard content marked concealed, and it makes no upload you didn't set up.

5. Third-party services

The third parties Klipp contacts are the upload destination you choose to connect it to, such as Notion, and, only if you turn location tagging on, Apple's geocoding service. If you connect no destination and leave location tagging off, Klipp makes no third-party network calls at all. When you do upload, your data is handled under that provider's own terms and privacy policy. Klipp uses no analytics SDK, advertising network, or error-reporting service.

6. Permissions Klipp requests

Klipp asks only for what it needs to do its job:

  • Screen recording and screenshot access

    So Klipp can capture screenshots and read the new screenshots you take into your local history.

  • Location (optional)

    Requested only if you turn on location tagging, and used at coarse, city-level accuracy to add location tags. Denying it simply leaves captures untagged.

  • Automation / Apple Events (optional)

    Used on a best-effort basis to note the source app, and the active browser tab's URL, of a capture. Denying it just omits that detail.

  • Outgoing network connections

    Used only if you connect an upload destination, so Klipp can upload to the destination you configured, and to look up a city name if you turn location tagging on.

  • Keychain access

    So your encryption key, and any upload tokens, can be stored securely on your device.

7. Children's privacy

Klipp does not knowingly collect any data from children or any users. See "What data Klipp handles" above.

8. Changes to this policy

This policy is dated August 9, 2026. If it changes, the new effective date will be shown at the top of this page.

9. Contact

Questions: carl@hagerling.se