Your data stays yours.
Your data never reaches our servers. License checks send only your license. Frisket is invasive by design: it sees your keystrokes and clipboard, and it can type on your behalf. This page lists what the app does with that access, and every network request it can make.
What runs on your Mac, and only there
All of Frisket's work happens on your Mac: the command palette, clipboard history, typing emulation, cheat-sheet overlays, snippets, transforms. Your keystrokes, clipboard contents, and anything Frisket reads from other apps are processed locally and stored locally, in the app's own container on your disk.
- No telemetry, no analytics. The app contains no analytics framework and sends no usage data.
- Crash reports stay local. If the app crashes, the report is written to your disk for you to inspect and share only if you choose. Nothing is uploaded.
- Passwords are off-limits. When macOS signals secure input (a password field), Frisket stands down: it does not observe, record, or type.
- Captured content is never logged. Keystrokes, clipboard text, and screen text are never written to logs or diagnostics.
The complete list of network requests
Frisket can make exactly three kinds of network connection, each for a named reason.
1. License checks
When you activate the app, and periodically afterwards (roughly every 7 days, with about a 30-day offline grace window), the app contacts the licensing service to confirm your license and its seat count. Deactivating a Mac makes the same kind of request.
Sent: your license key · a hashed machine identifier (never the raw hardware ID) · the app version. Nothing else — no content, no personal data.2. Update checks — only with your consent
The app asks once whether it may check for updates automatically. If you say yes, it periodically fetches two static files from frisket.app: the release feed (appcast.xml) and a signed license-revocation list checked during the same request — never on its own schedule. If you say no, nothing is fetched; you can still check manually. System profiling is permanently off: no OS version, hardware model, or usage data is ever attached.
Sent: an ordinary HTTPS GET — the app name and version in the request's User-Agent, and your IP address as with any web request.3. iCloud clipboard sync — optional, and yours
If you enable clipboard sync, your clipboard history syncs through your own iCloud account's private database, between your Macs. It never touches a Frisket server — there isn't one. Apple's iCloud terms and protections apply; we have no access to the data.
Sent: clipboard history records, to your iCloud private database only. Off by default until you enable it.What we can see
Almost nothing. Purchases are processed by our payment provider, which acts as merchant of record — it handles checkout, payment details, taxes, and receipts under its own privacy policy. We receive your order details (name, email, license) so we can issue and support your license, and we never receive your payment card. The frisket.app website and downloads are served by a CDN (Cloudflare); like any web host it keeps standard edge logs, which we do not export or analyze. The website itself contains no analytics, no trackers, and no cookies.
Your controls
- Update checking is a switch in Settings, off until you consent.
- Clipboard sync is off until you turn it on, and can be turned off anytime.
- Every macOS permission (Accessibility, Input Monitoring, Automation) is requested only when a feature first needs it, is explained in plain language, and can be revoked in System Settings — the app degrades gracefully without it.
- Deactivate any Mac from Settings to free its license seat.
- Clipboard history can be cleared at any time; deleting the app removes its local data.
Questions
Write to support@frisket.app. If any behavior of the app ever seems to contradict this page, tell us. We treat that as a serious bug.
Last updated: 2026-08-15