Privacy
ZecHub is an open-source education hub for a privacy-preserving currency, so we hold the site itself to the same standard. This page describes, plainly, exactly who can observe that you visited — no more, no less.
We do not track you
There are no analytics, no advertising, no tracking cookies, no fingerprinting, and no third-party trackers on this site. Reading the wiki requires no account, and we build no profile of you. We do not opt you into browser ad-topics APIs (they are disabled site-wide).
Your connection to the site
The site is served by our hosting provider (Vercel), which — like any web host — processes the network requests needed to deliver each page and keeps short-lived operational logs. Connections are HTTPS-only (enforced via HSTS). When you click a link that leaves the site, your browser sends only the originating site, never the specific page you were on.
Images, fonts, and assets
Fonts and the images on our pages are hosted by us and load from this domain, so rendering a page does not announce your visit to a content network. The only deliberate exceptions are a small number of logos served by Wikimedia and live status badges from shields.io — both chosen as privacy-respecting sources.
Embeds load only when you ask
Embedded videos (YouTube) and interactive maps load behind a click-to-load placeholder. Until you explicitly click to load one, nothing about your visit is sent to those services. Once you load an embed, it becomes a direct connection to that third party, which operates under its own privacy policy.
Optional features you choose to use
- Newsletter — if you subscribe, we store the email address you provide, for the newsletter only.
- Wallet “likes” — if you like an item, the server records that a vote happened, keyed by a hash of your IP address plus that item, purely to stop duplicate votes. It is not tied to your identity or used to track you across the site.
- AI assistant — the built-in assistant is disabled by default; it only activates if the operator configures a model-provider key. When active, it sends your question and the page you are on to that third-party provider to generate an answer, and the interface makes that clear before you use it.
Open source
Everything here is public. You can read and audit the site's code and this page's claims in our repositories on GitHub. This statement describes the site's current behaviour and is updated when that behaviour changes.