Zipper is built to collect as little as possible. This policy states plainly what the website and the service do — and do not — touch.
This site uses no analytics, no advertising cookies, and no third-party trackers. It does not set tracking cookies of any kind.
The only browser storage the site uses is on the node management page
(manage.html): it keeps a node operator's admin key in
the browser tab's session storage so a page refresh does not lose it.
That value is never sent anywhere and is discarded when the tab
closes.
Zipper has no accounts, no signup, and no user profiles. A room assembles in a node's memory, is never written to disk, keeps no logs, and evaporates when the conversation ends. Message content, files, and calls are end-to-end encrypted; a node only ever relays ciphertext it cannot read.
To route a connection, a node necessarily sees the network (IP) address of each connecting party for the duration of that connection. This is inherent to any networked service. It is not written to disk and not logged.
An invite is a sealed, encrypted bundle held briefly in a node's memory so a recipient can fetch it once, after which it is dropped. The secret that opens an invite travels inside the invite link and never reaches a server.
If a node operator chooses to list their node publicly, the directory stores only what that operator entered — the node's name, URL, and region. The directory holds nothing about users.
Anyone may run their own Zipper node. This policy covers nodes operated by AI-Ministries. A node run by someone else is operated by that person, under their own terms.
The site may link to third-party services, such as a recommended hosting provider. Those sites have their own privacy practices and may set their own cookies; this policy does not cover them.
If this policy changes, the date above is updated.
Questions: [loading]