Privacy
Zwisper has no server. Nothing you write, read, or store is sent anywhere.
What we collect
From the extension and the web app: nothing. There is no account, 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.
From this website: page views. zwisper.pages.dev uses a cookie-free analytics service that
gives visitors no identifier. It tells us, in aggregate, how many people opened each page, roughly which country
they were in, what kind of browser they used, and which site sent them. It never sees a note, a contact, a
password, or the part of a reveal link after the #.
What is stored, and where
Everything Zwisper keeps lives in your browser's extension storage on your own device:
- Settings. Your preferences and per-site rules, in local extension storage.
- Contacts vault. One shared key per person. It is encrypted on disk with AES-GCM under a master passphrase you choose, in local extension storage. While the vault is unlocked, the decrypted keys sit in session storage, which is memory-only and cleared when the browser closes or the auto-lock timer fires.
- Inbox. Notes you have opened. This is off by default. When it is off, the inbox lives in session storage and disappears when you close the browser. When you turn it on, it is written to local extension storage so it survives a restart. You can clear it at any time from settings.
The web app at zwisper.pages.dev/app keeps the same settings and the same encrypted vault, in that browser's own storage for this site instead of extension storage. Clearing the site's data removes them; there is no copy anywhere else.
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 website
This site is static files. Apart from the analytics script described above, it loads no third-party scripts and sets no cookies. Whoever hosts it may keep ordinary web server access logs, which would record that a 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 to use, provided as is, without warranty of any kind. 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? Use the Support tab on Zwisper's Chrome Web Store page.