Privacy

Privacy notes for a static release site.

Last updated May 11, 2026. This page separates website privacy, download privacy, and wallet/network privacy so users know what the page can and cannot see.

Overview

No accounts, no forms, no seed collection

This website is a static product and release page. In the current codebase it does not include account registration, comment forms, analytics scripts, advertising tags, payment forms, or wallet-seed input fields.

Never enter a seed phrase, private key, or recovery phrase into this website.

The website exists to host release links, checksums, verification notes, and policy pages. Wallet secrets belong only inside trusted wallet software or your offline backup process.

Website data

What the front end does

No cookies are set by the HTML, CSS, or JavaScript in this project.
No analytics endpoint is referenced by index, docs, terms, or privacy.
The JavaScript only controls the sticky header and mobile navigation menu.
Static hosting providers may still create normal access logs, such as IP address, user agent, requested file, referrer, and timestamp.

Downloads

Release-file requests

When you download a release file or checksum manifest, your browser requests a file from the site host. That request can reveal normal network metadata to the hosting layer. The page itself does not add a separate tracking request.

Use the internal checksum table and verification commands before installing downloaded wallet software.

Wallet privacy

Wallet network behavior is separate

Running a desktop wallet can create network traffic that this website does not control. Electrum-style wallet connections may reveal metadata to servers depending on configuration, address type, server selection, and transaction behavior.

Transparent use

Transparent Zcash activity is visible on-chain. Treat addresses, amounts, and transaction links as public context.

Shielded use

Shielded Zcash activity is designed for privacy features, but user behavior, wallet support, and network choices still matter.

Local safety

Protect seed phrases, wallet files, backups, device access, and clipboard behavior. A private protocol cannot fix a compromised endpoint.

External pages

External navigation is intentionally minimized

The primary navigation, resource cards, footer, and verification route are internal. If future versions add source repositories, community channels, or protocol references, those links should be visibly external and reviewed as separate privacy boundaries.

Controls

What users can do

Verify release files locally before opening them.
Keep wallet downloads and checksum manifests in the same folder during verification.
Use browser privacy controls, a trusted network, and a clean device when downloading wallet software.
Review Terms for self-custody and software-risk boundaries.

Changes

Policy updates

Material changes should update the date at the top of this page and keep download verification, terms, and privacy language aligned. Do not add analytics, forms, or external embeds without documenting them here.