Privacy policy

There is nothing to collect.

Rakkun ships without a network entitlement. That isn’t a promise we make about our servers — it’s a capability macOS never grants the app.

Effective 30 July 2026. This policy covers the Rakkun app for macOS and this website, rakkun.app. During private early access Rakkun is distributed as an Apple-notarized download from this site; it is also being released on the Mac App Store. The same policy applies either way — the app is identical.

The short version

  • Rakkun has no network entitlement of any kind. The app cannot open a connection, so nothing you copy can leave your Mac.
  • No analytics, no telemetry, no crash reporting. No account, no sign-in, no server, no sync.
  • Clipboard history is written only to Rakkun’s own sandbox container, in a file you can delete.
  • Content copied from a password manager is never recorded at all.
  • The only data that ever leaves your Mac is what you export by hand — a drag-out or a Save As…

No network entitlement

Rakkun runs in the macOS App Sandbox. A sandboxed app can only do what its entitlements permit, and entitlements are enforced by the operating system — they are a capability the OS grants, not an assurance a developer writes down.

Rakkun’s entitlements request exactly two things: the sandbox itself, and permission to write the one file you pick in a Save As… dialog. There is no com.apple.security.network.client and no com.apple.security.network.server. Without them the app can neither reach out to a server nor accept an incoming connection. There is no switch to turn off and no traffic to inspect: no code path in Rakkun can touch a network, because macOS will not permit it.

That single fact is why the rest of this policy is short. An account, sync, telemetry, ad IDs, crash uploads and A/B tests all require the entitlement Rakkun does not have.

Where your clipboard history lives

Rakkun stores your history in its own sandbox container on your Mac, at:

~/Library/Containers/com.rakkunapp.Rakkun/Data/Library/Application Support/Rakkun/history.json

It is an ordinary file you own. Delete it and your history is gone; Clear History inside the app does the same thing without quitting. Your settings live in the app’s own preferences inside that same container. Nothing is written anywhere else on your disk, and there is no second copy anywhere.

What Rakkun never records

Some content is skipped before it is ever read, so it cannot appear in your history:

  • Password managers and autofill. Anything carrying the concealed pasteboard type (org.nspasteboard.ConcealedType) is never recorded — not masked, not encrypted, never captured.
  • Transient content. Items marked transient or auto-generated by the app that produced them are skipped the same way.
  • Apps you exclude. Add any app under Settings → Privacy and copies made while it is frontmost are ignored.

One honest caveat: macOS gives an app no signal that a copy came from a private-browsing window. Private mode governs the browser’s history and cookies, not the system clipboard, so a copy made in a private window is recorded like any other. Exclude the browser, or mark the item as a secret, if that matters to you.

Secrets, masking and the Keychain

Rakkun recognizes common credential shapes — API-key prefixes, private-key blocks, bearer tokens, connection strings — and you can mark anything else as a secret yourself. Recognized secrets are masked in the interface.

  • Not pinned: the value is kept in memory for the session only. Nothing is written to the history file, and quitting Rakkun ends it.
  • Pinned: the raw value goes into the macOS Keychain (service com.rakkun.pinned-secret), stored device-only so it does not sync to iCloud. The history file keeps only a secret-free stub.

Deleting the item, unpinning it, unmarking it, or running Clear History removes the Keychain entry as well.

Images, text recognition and QR codes

When an image lands on your clipboard — a screenshot, say — Rakkun reads it locally with Apple’s Vision framework for text recognition and QR decoding. The image bytes are discarded afterwards; only the recognized text or decoded payload is kept.

This happens entirely on your Mac. Rakkun uses no camera and asks for no Screen Recording permission: it only ever looks at an image that is already on the clipboard, and it never captures your screen.

The one permission Rakkun asks for

Rakkun can request macOS Accessibility permission for exactly one purpose: pressing ⌘V for you after you pick an item, so it pastes straight into the app you were in. It does not read your screen, inspect other apps’ contents, or automate anything else.

The permission is optional and is never requested at launch — it is offered only from explicit UI: the in-app “Enable direct paste” explainer, or Settings. Without it, Rakkun puts the item on your clipboard and you press ⌘V yourself. Everything else works exactly the same.

Data you move yourself

The only way clipboard content leaves your Mac is when you send it there. Drag an item out as a file or save it with ⌘S and it goes to the location you choose — which may well be a synced folder, if that’s what you picked. That is your action, not a transfer by Rakkun.

Drag-out files are staged in the app’s container temp directory and purged at launch and when the panel closes.

What Apple collects

We can speak for Rakkun, not for its storefront. When you buy or download a Mac App Store app, Apple handles the transaction and keeps its own purchase and download records, plus whatever app analytics you have chosen to share with developers in your device settings.

What reaches us from that is aggregate App Store reporting — units, regions, versions. It never includes anything about your clipboard, because Apple never has it either. Apple’s handling of that data is governed by the Apple Privacy Policy. Rakkun’s App Store privacy label declares Data Not Collected.

This website

rakkun.app is a static site. It sets no cookies, runs no analytics, and loads no third-party scripts, fonts or trackers. There is nothing here to opt out of.

Two places data does show up:

  • The early-access download form. Your access code is checked on the server against a salted hash and is never logged. To slow down guessing, the IP address of a failed attempt is held briefly in the server’s memory; it is not written to a database, and it is not shared.
  • Email. If you write to us, we have your message and your address, and we use them only to answer you.

The site is hosted on Vercel, which — like any web host — processes standard request logs such as IP address, user agent and timestamps in order to serve pages and block abuse. See the Vercel Privacy Policy.

Your rights, and why there’s little to exercise them on

Access, correction, export and deletion requests all resolve the same way: we hold no personal data about you, so there is nothing to hand over or erase. Your clipboard history is already in your own hands — it’s a file in your home folder.

The one exception is an email thread you started. Ask and we’ll delete it. Rakkun is not directed at children, and it has no profile, no identifier and no advertising of any kind.

Changes to this policy

If what the app does changes, this page changes with it — before or alongside the release, not after. The effective date at the top always reflects the current version, and the current version always lives at rakkun.app/privacy.

We have no mailing list to notify you through, for the same reason the rest of this policy is short: we never collected your address.

Questions

Ask us anything about this.

Privacy claims deserve scrutiny, especially from people who copy credentials for a living. If something here is unclear — or looks wrong — tell us and we’ll fix the page or the app.