Privacy Policy

Wisp is built to respect your privacy by design. This page describes what data Wisp does and does not handle — written in plain language because that's what you'd want.

The short version

Wisp does not collect, transmit, or process any personal data. There are no accounts, no telemetry, no analytics, no crash reporting, no "anonymized usage statistics," and no third-party SDKs of any kind. Your scratchpad never leaves your Mac unless you choose to put it inside a sync folder (iCloud Drive, Dropbox, etc.), in which case the sync is handled by that service — not by Wisp.

What stays on your device

The only network requests Wisp makes

Wisp checks for updates by making HTTPS requests to GitHub's public Releases API:

That's it. GitHub's own privacy practices apply to those requests, and they will see your IP address and the User-Agent your operating system sends — the same as any normal web request. Wisp does not add headers, cookies, account identifiers, or tracking parameters.

If you enable sync

Wisp lets you choose any folder on disk as the location for scratchpad.md. If you point it at a folder inside iCloud Drive, Dropbox, Syncthing, or any other sync service, your text will be synced by that service to wherever you've configured it. Wisp itself does not participate in the sync — it just reads and writes a file.

The sync service's privacy policy governs how your text is transmitted and stored. Wisp recommends iCloud Drive for most users because it's already on every Mac.

What we will never do

Source code

Wisp is open source under the MIT license. You can read every line at github.com/sulemaanhamza/wisp to verify these claims yourself, or grep for any network call.

Changes to this policy

If this policy ever changes meaningfully, the updated version will live here with a new "Last updated" date. The intent is for it to keep saying roughly the same thing it does today: Wisp does not collect data.

Questions

Open an issue at github.com/sulemaanhamza/wisp/issues.