Zwisper

Privacy

Zwisper has no server. Nothing you write, read, or store is sent anywhere.

What we collect

Nothing. There is no account, no analytics, no telemetry, no crash reporting, and no advertising. Zwisper makes no network requests of its own. We cannot see your notes, your contacts, the pages you visit, or that you use the extension at all, because none of it reaches us.

What is stored, and where

Everything Zwisper keeps lives in your browser's extension storage on your own device:

Uninstalling Zwisper removes all of it. None of it is synced to any account or server by the extension.

Permissions

Zwisper reads and writes the page you are on so it can underline messages that carry a note, show the note's card, and put the compose pill in the text field you are typing in. That work happens entirely inside your browser tab. Zwisper does not transmit page contents anywhere.

Reveal links

A reveal link carries the message text in the URL fragment — the part after the #. Browsers never send the fragment to a web server, so the text is decoded by JavaScript in the reader's own browser and this page never receives it. The password is never part of the link; the reader types it here, and it stays in the page.

This page

This page is static. It sets no cookies, loads no third-party scripts, and runs no analytics. Whoever hosts it may keep ordinary web server access logs, which would record that the page was requested — never the fragment, and never the note.

Changes

If this policy ever changes, the new version replaces this page and the change is recorded in the project's changelog.

No warranty

Zwisper is free, open-source software provided as is, without warranty of any kind, under the MIT license. It is a privacy tool, not a guarantee: a screenshot of a message destroys the note inside it, some platforms strip the hidden characters when a message is sent, and a platform can tell that a message carries invisible characters even if it cannot read them. You use it at your own risk, and the authors are not liable for how it is used or for any loss that results from using it.

Contact

Questions about privacy go to the project on GitHub: open an issue.