CacheBar

Privacy Policy for CacheBar

CacheBar ships without the network entitlement, so it cannot open a connection of its own. Your data stays on your Mac.

Also available in: Deutsch

This Privacy Policy applies to the macOS desktop application CacheBar. For the aaronwst.de website itself — hosting and server log files — the website privacy policy applies.

Effective: 24 October 2026

1. Introduction & Controller

We take your privacy very seriously. This Privacy Policy informs you about the processing of personal data in connection with the desktop application “CacheBar” (hereinafter “App”).

The provider named below is the data controller within the meaning of the General Data Protection Regulation (GDPR) and the German Digital Services Act (DDG); Section 3 explains for which processing operations that is the case:

Name: Aaron Wüst, App-Entwicklung

Address: c/o POSTFLEX PFX-232-123, Emsdettener Straße 10, 48268 Greven, Germany

Email: service@aaronwst.de

Telephone: +49 163 7108634

2. Scope & Categories of Processed Data

The App is a local-only clipboard management utility. When you run the App, it monitors and stores content copied to your macOS clipboard. Depending on what you copy, this data may include personal data or sensitive information such as text, passwords, private keys, contact details, links, or code snippets.

If you switch the “Keep copied images” setting on, copied pictures — screenshots above all — are stored as well, up to a size limit of 12 MB per picture taken off the clipboard as an image. A stored picture may show anything that was on your screen when it was taken.

If you switch the “Keep copied files” setting on, files you copy — in Finder or in any other application — are stored as complete copies rather than merely by name, up to the per-file size limit you choose in Settings (5 MB to 100 MB, 25 MB by default). Copying several files at once stores up to ten of them, one entry each. A picture copied as a file follows the “Keep copied images” setting instead. A stored copy holds the entire contents of that file and can therefore contain any personal or confidential data the file itself contains; it stays on your Mac and can be pasted back as a file or written back out to disk from within the App. Copies are kept independently of the original: deleting or changing the original file does not change the copy, and deleting the entry in the App deletes the copy. Folders are never stored. Once stored pictures and files together exceed 2 GB, the oldest of them are deleted automatically; pinned entries, your Space and your notes are exempt.

For each entry the App also records which application was in the foreground when you copied it: that application’s name and its bundle identifier. This is shown on the entry so you can tell your clips apart, and it is used for the exclusion list described in Section 12.

Monitoring only begins after you have confirmed the welcome screen described in Section 14. Content that matches your Private Filter, content copied out of an application you have excluded, and content that other applications mark as concealed or temporary, is discarded before it is stored (see Section 12).

In addition to copied content, the App stores notes that you write yourself in its “Notes” area, and clips you have joined together using its merge function. Both are kept in the same local database as your clipboard history and are never transmitted.

The App also stores what it works out about an entry by itself: the text read out of a stored picture, the contents of any codes in it, a one-line headline for a long entry, and a marker recording that an entry was recognised as sensitive and locked. All of these are derived from content that is already stored, are kept in the same local database, are deleted together with the entry, and are described in Section 13.

CacheBar processes the contents of your clipboard exclusively on your device and on your behalf; they never reach the developer at any point. Where personal data of other people is involved because you copied it, that happens within your own sphere of responsibility — for purely personal or household purposes, Art. 2(2)(c) GDPR applies to you.

The developer is a controller within the meaning of Art. 4(7) GDPR only for the processing described in Sections 5 and 16, where data actually reaches him.

4. No Data Collection, Transmission, or Selling (CCPA/CPRA)

We do not collect, store, transmit, or share your clipboard data or settings on external servers. The App operates completely offline; it is distributed without the network entitlement that macOS requires for outgoing connections. The on-device analysis described in Section 13 changes nothing about this: it uses functions built into macOS that answer on your device. We do not sell, rent, or lease any personal data, nor do we share it with third parties. Under the California Consumer Privacy Act (CCPA) / California Privacy Rights Act (CPRA), this constitutes a complete “No Sale / No Share” policy.

5. App Store, Payments & Telemetry

The App is distributed through the Apple App Store, operated by Apple Distribution International Ltd. or Apple Inc. (“Apple”). Apple processes your store account, billing info, and downloads according to Apple’s own privacy policy. CacheBar does not integrate any third-party analytics SDKs (such as Google Analytics or Firebase) inside the App. We only receive anonymous, aggregated crash reports and installation statistics from Apple if you have consented to share them.

6. Do Not Track (DNT) Signals (CalOPPA)

Pursuant to the California Online Privacy Protection Act (CalOPPA), we disclose that because the App does not collect user data or track your online activities across third-party websites or services, it does not track you and does not respond to “Do Not Track” (DNT) signals.

7. Children’s Privacy

The App is not directed at children under the age of 13 (or 16 in the EU/UK). We do not knowingly collect or process personal data from children. Since all data is stored strictly locally on your device, we have no access to it.

8. Data Security & Storage

All data is stored locally in a SwiftData SQLite database inside the App’s macOS sandbox container. Access is limited by macOS file permissions and sandbox protection. The App does not encrypt this database itself; on disk it is protected by FileVault if you have switched it on. This also applies to locked entries (Section 13): the lock keeps them out of sight within the App, it does not encrypt them. iCloud Drive does not synchronise this container. Depending on your settings, it may be included in Time Machine or other backups; the security of those backups is governed by the programs that make them. Stored pictures and stored copies of files are held as separate files beside that database, inside the same sandbox container. When you paste a stored file, the App writes it out once more into its own temporary folder inside that container so the receiving application can read it; those temporary copies are deleted when the next one is written, and at the latest the next time the App starts. Private Filter entries are the exception: they are not kept in this database but in the macOS Keychain, as described in Section 12.

9. Data Retention & Deletion

Your history size is limited to your preference (50, 100, 250, 500 or 1000 items). The limit applies to unpinned history entries: once it is reached, the oldest of them are automatically deleted. Pinned entries, items saved to your Space, and notes you have written yourself are not subject to this limit and are kept until you delete them. You can clear the entire history, your Space, or your notes at any time from the settings menu. Entries that match a newly added Private Filter entry are deleted immediately, including entries in your Space and notes you wrote yourself.

If the database can no longer be opened after a defect, CacheBar sets it aside under a new name in the same folder instead of deleting it, and says so in its window. That copy holds your previous history and is subject neither to the history limit nor to clearing from the settings menu; you can delete it directly from that notice.

If you remove CacheBar, the App’s data folder at ~/Library/Containers/com.aaronwuest.ClipKeep and your Private Filter entries in the macOS Keychain remain until you delete them yourself. Clear your history, your Space and your notes from the settings menu, and your Private Filter list with “Remove all”, before removing the App if you want nothing left behind.

10. Your Rights under GDPR & CCPA

You have the right to access, rectify, delete, restrict processing, or export your data. Because we do not collect or store any of your data on external servers, we cannot access, retrieve, or delete it for you. You can exercise all of your rights directly on your device by copying, editing, or deleting entries in the App, or by deleting the App and the data described in Section 9.

11. Right to Lodge a Complaint with a Supervisory Authority (Art. 77 GDPR)

Pursuant to Article 77 of the GDPR, you have the right to lodge a complaint with a supervisory authority if you believe that the processing of personal data relating to you infringes data protection laws. The competent authority for the developer’s place of business is:

Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW)

Kavalleriestraße 2-4, 40213 Düsseldorf, Germany

Email: poststelle@ldi.nrw.de

Website: https://www.ldi.nrw.de

12. Private Filter, Concealed Content & Biometric Protection

The App provides a “Private Filter”: a list of texts (for example passwords, keys or account numbers) that must never enter the clipboard history.

13. On-Device Analysis (Text Recognition, Locking, Apple Intelligence)

Beyond storing your clips, the App analyses them on your device in order to make them findable again and to keep recognised secrets out of sight. “Entry” in this section means everything the App holds: the history, your Space and the notes you wrote yourself. Everything described here runs locally, through functions built into macOS. Nothing is transmitted; the App continues to ship without the network entitlement that outgoing connections would require. You decide about the three parts that run by themselves — text recognition, the lock and headlines — on the welcome screen described in Section 14, and you can switch each of them on or off separately under Settings > Privacy & Intelligence. “Ask your history” has no such switch because it never happens by itself: it runs only when you press the ✨ button beside the search field and submit a question. Switching a part off takes effect immediately and also removes what it had produced: the text read out of pictures and the headlines are deleted, and the entries the lock is holding are released — apart from the one case named below.

14. Your Confirmation Before Processing (Onboarding)

On first launch — and again whenever what the App processes changes materially — the App shows a short welcome screen on which you must confirm that you have read this Privacy Policy, and on which you decide whether copied pictures and files are kept as well and whether the App analyses your clips on your device — the text recognition, the lock and the headlines described in Section 13. Until you confirm, the App does not read or store any clipboard content.

Your confirmation, the date of the confirmation, and the version of the policy are recorded locally in the App’s settings (macOS user defaults) and are not transmitted. Because all processing takes place locally and no data reaches the developer, this confirmation serves transparency purposes under Art. 12 and 13 GDPR; it is not a consent within the meaning of Art. 6(1)(a) GDPR.

15. Effective Date & Changes to this Policy

This Privacy Policy is effective as of October 24, 2026 and replaces the version of October 6, 2026. We may update this policy from time to time. Updates will be bundled with App releases and updated directly inside this document.

16. Support

Choosing the support entry in the menu opens a prepared email in your mail application. What you write to us is processed solely in order to handle your request (Art. 6(1)(b) and (f) GDPR) and is deleted once the request has been dealt with and no retention obligations stand in the way. The App itself transmits nothing; it does not have the network entitlement that would be required for that.