Privacy Policy

1. Information We Collect

Zcash Wallet is designed to function without collecting personal data or monitoring user activity. We do not track identities, balances, transaction history, or wallet behavior. Our architecture is built so that sensitive information never leaves your device, and we have no ability to access, recover, reset, or view your wallet data under any circumstances. We do not maintain user accounts, we do not log connection metadata, and we do not use analytics that fingerprint devices or profile usage. Your wallet stays yours — privately, locally, and encrypted at all times.

We do not collect or store:

• Private keys or seed phrases
• Wallet balances or transaction history
• Wallet addresses (shielded or transparent)
• Names, emails, phone numbers, or any identity data
• IP addresses, device identifiers, geolocation, or network metadata
• Contact lists, clipboard data, local files, or system information
• Usage fingerprints, behavioral patterns, or advertising identifiers

Zcash Wallet operates on a zero-knowledge principle: we cannot see, access, derive, correlate, or reconstruct user activity — even if compelled. This includes wallet creation, backup, transaction signing, memo data, and shielded activity. We do not and cannot associate any wallet with any individual. All wallet logic, including encryption, key generation, transaction construction, and memo handling, occurs locally and remains isolated on the device.

Voluntary Information (User-Provided)

The only information we receive is information you intentionally choose to send when contacting support. This may include description of an issue, device model, error messages, log excerpts, or screenshots — provided voluntarily and only for troubleshooting. We never request your seed phrase, private keys, or sensitive wallet data. If you send them by mistake, they are immediately deleted and we will instruct you to move funds for security reasons.

We do not automatically attach technical metadata to support messages and we do not crawl devices for diagnostic information. All troubleshooting is opt-in, user-initiated, and strictly limited to the content you explicitly choose to share. You control the information flow — not us.

Website-Only Minimal Analytics (Not in the Wallet App)

When you visit our public website, we may use privacy-respecting analytics that do not collect personal data, do not use cookies, and do not store IP addresses in identifiable form. We measure basic website performance and page visits in aggregate only, to understand general interest and improve documentation. This does not apply to the wallet application itself — the app operates without remote telemetry or analytics of any kind.

2. How We Use Information

Zcash Wallet is built on a privacy-first foundation. Because we do not collect identifying information, wallet data, or blockchain activity, our ability to use data is intentionally limited — by design. We only use what is strictly required to operate the wallet securely, maintain functionality across devices, and assist users who voluntarily contact support. There is no user profiling, commercial usage, external enrichment, or behavioral tracking at any stage of our process. If the wallet can function without a piece of information, it is never requested or processed.

Service Functionality

We use limited technical context only to ensure the wallet functions as expected across devices, operating systems, and Zcash network upgrades. This does not include wallet contents, identities, or activity. The purpose is purely operational — maintaining reliability, sync performance, and security integrity in a decentralized environment without server-side accounts or centralized logs.

This may include, when necessary:

• Ensuring protocol compatibility: with Zcash consensus rules and upgrades
• Verifying cryptographic performance: ensuring libraries remain reliable and secure
• Supporting secure device storage: and OS-level security features
• Addressing stability concerns: such as potential crash or memory management issues

At no point do we access wallet secrets, addresses, balances, or transaction details. We do not create fingerprints, usage profiles, or analytics tied to individual users.

Security Assurance

Security is continuous, and sometimes users choose to share diagnostic data when troubleshooting issues. When this happens, we use that information only long enough to identify and resolve the problem, then delete it. Troubleshooting never requires your seed phrase, viewing keys, or transaction history.

We may temporarily process technical diagnostics solely for:

• Identifying security vulnerabilities
• Investigating crashes or failures
• Resolving sync or shielded note issues
• Maintaining wallet stability and reliability

If any sensitive wallet data is ever provided unintentionally, it is not stored or used, and users are instructed to rotate keys for safety.

User-Initiated Support

When you choose to contact support, we only use the information you voluntarily provide to help solve your issue. The wallet never requests private keys or wallet backups, and we advise users to report any suspicious requests.

Typical support assistance may include:

• Reviewing non-sensitive logs you explicitly choose to share
• Providing troubleshooting steps based on your OS or device type
• Diagnosing installation or update issues
• Offering recovery guidance without accessing wallet secrets

We never require identity documents, blockchain addresses, or wallet secrets, and we cannot remotely access or modify your wallet in any form.

Product Reliability & Improvement

To improve performance and wallet usability over time, we utilize anonymized and aggregated technical signals. These insights help improve stability — not monitor user activity — and are not tied to individual wallets.

Improvements may be driven by:

• Stability insights: for example, aggregated crash frequency
• Sync performance patterns across devices and OS versions
• Shielded scanning efficiency metrics
• Optional user feedback provided voluntarily

There is no collection of personal identifiers, wallet data, balances, transaction metadata, or behavioral patterns.

No Commercial or Third-Party Exploitation

Zcash Wallet data is never used for advertising, user tracking, third-party analytics, or monetization. We do not sell, trade, or share any personal or wallet information.

We do not and will not:

• Sell user data or insights
• Share data with marketers or brokers
• Participate in tracking ecosystems
• Build behavioral or advertising profiles
• Integrate external tracking SDKs

All data usage is strictly limited to maintaining security, functionality, and reliability — never commercial exploitation.

3. Data Storage & Security

Zcash Wallet uses a self-custodial security model designed so that wallet data remains isolated on the user’s device and protected by cryptographic standards. The application operates without centralized storage, account systems, or identity-linked infrastructure. Each wallet instance generates and maintains its own secure environment, ensuring that financial access cannot be compromised through server breaches, credential theft, or external account recovery systems.

Local Security Controls & Encryption

All wallet-sensitive material — including cryptographic keys and historical state required for transaction validation — is encrypted at rest using OS-level secure storage primitives and processed in memory only when necessary for wallet operations. Access to secure material is controlled by the device’s local security mechanisms (such as secure enclaves or protected key containers when supported), meaning the confidentiality of wallet data is tied directly to the security of the device you control.

Network Protection & Privacy Boundaries

When the wallet interacts with the Zcash network, only protocol-required information is exchanged. No persistent identifiers or supplemental metadata are attached to requests, and network interaction does not reveal wallet structure or user identity. The wallet does not employ traffic fingerprinting, session tagging, or behavioral telemetry. Connections are encrypted where possible, and users may choose to route network traffic through privacy-enhancing tools (e.g., local network relays or VPNs) without impacting wallet functionality.

Software Integrity & Vulnerability Response

Security is reinforced through open-source code transparency, independent review of cryptographic libraries, and ongoing monitoring of relevant security advisories. When vulnerabilities affecting underlying components or supported platforms are disclosed, remediation procedures prioritize user safety and responsible deployment of patches. If a high-severity issue is discovered that could affect wallet correctness or confidentiality, clear communication and guidance will be provided to users, along with recommended protective actions.

4. Information Sharing

Zcash Wallet is built so that private wallet data remains under the sole control of the user. The application does not transmit wallet contents, identifiers, or user-specific metadata to any external parties. As a self-custodial system, there is no internal mechanism for our team — or third parties — to access keys, balances, or transaction activity. Because we do not maintain centralized identity systems or financial records, there is no information for us to share that could deanonymize users or expose wallet activity.

When Information May Be Disclosed

There are limited circumstances in which non-sensitive operational data may be shared. These situations are strictly controlled and apply only to information explicitly provided by the user or generated through system interaction:

• Security & Abuse Prevention
  Sharing technical incident details with security specialists if malicious behavior or software exploitation is suspected, limited to technical context and never wallet secrets.
• User-Requested Support
  If you voluntarily supply diagnostic logs or troubleshooting information, it may be shared internally with technical personnel solely to resolve the issue you reported.
• Legal Compliance
  If required by applicable law, we may be obligated to disclose information we have access to (for example, non-wallet technical logs). Since we do not store wallet data or financial identifiers, we cannot provide information that does not exist within our systems.

No Commercial or Visibility-Based Sharing

Zcash Wallet does not share information for any commercial purpose. Specifically, we do not:

• sell data
• share user information for advertising or profiling
• participate in data-exchange agreements
• provide any party visibility into wallet activity or network usage

The wallet architecture prevents access to sensitive data even during lawful requests. If compliance is required, only the minimum non-identifying operational information available to us is provided.

5. Third-Party Services

Zcash Wallet is designed to operate autonomously, without relying on centralized identity systems, custodial back-ends, advertising networks, analytics SDKs, or tracking infrastructure. The wallet never transmits keys, seed phrases, addresses, balances, or transaction history to any external party — core wallet logic remains entirely offline and local to the device.

Some optional features may interact with third-party services, but always in limited, privacy-preserving ways. These connections never reveal the user's identity or wallet activity, and they are never required for the wallet to function normally. Nothing is triggered silently, nothing is persistent, and nothing enables profiling.

All third-party interactions follow three rules:

• Only initiated when needed or explicitly chosen
• Do not leak identifiers, wallet data, or metadata
• Never allow external entities to monitor usage or behavior

5.1 Network Connectivity

The wallet connects to the Zcash network strictly to sync blocks and broadcast transactions. This communication is protocol-level only — no identity markers, wallet metadata, or usage fingerprints are attached. Whether using public lightwallet infrastructure or a personal node, the server sees a blockchain client, not a user.

This connection may occur via:

• Public lightwallet servers
• A user's own full node (if enabled)

Nodes cannot determine:

• wallet ownership or linked addresses
• balance or note ownership
• transaction history
• user identity or device profile

5.2 Exchange-Rate Feeds

If fiat pricing is enabled, the wallet retrieves market rates from a public source. This is a convenience feature only — disabling it does not reduce functionality. Requests are simple one-way pulls, without identifiers, telemetry tags, or behavioral fingerprints. The wallet does not correlate market lookups with user activity.

Price lookups never transmit:

• wallet addresses
• balances
• transaction context
• device identifiers

5.3 Backup Services

Users may choose to store encrypted backups externally. Before any backup leaves the device, it is fully encrypted locally. Backup providers receive only an encrypted file — unreadable and not linkable to wallet identity or contents. Decryption is possible only with keys controlled by the user.

Cloud services never receive:

• keys or seed phrases
• wallet address data
• note or balance context
• behavioral metadata

5.4 Diagnostic Reports

Support logs are shared only if the user intentionally submits them. They focus on software behavior and stability, not financial data. Nothing is ever uploaded automatically; users review logs before sending. If sensitive information is somehow included, users are advised to rotate keys — the wallet assumes a paranoid security posture by default.

Logs never contain:

• private keys or seeds
• wallet balances or addresses
• transaction data

6. Your Rights & Choices

You have full control over your experience when using Zcash Wallet. Since the wallet is built to avoid collecting personal information whenever possible, most privacy rights are inherently satisfied by design — there is nothing to access, export, correct, or delete because sensitive data never leaves your device in the first place. Still, if you interact with optional features such as encrypted cloud backups or support communication, you maintain the right to access or remove the information you voluntarily provided. Any request you make regarding optional submitted data will be honored promptly and without friction. You can always choose to not share diagnostic information, not enable cloud backups, and not interact with third-party services — the wallet remains fully functional in all cases.

If you contact support and share logs or technical information, you may request deletion of that data after the issue is resolved, and it will be permanently removed from our systems. If you choose to stop using optional services at any time, you can revoke access, disconnect backup destinations, clear local support data, wipe cache files, or uninstall the application. Since wallet keys and all blockchain-related information are stored only on your device, uninstalling the application or deleting the wallet file from your device wipes your funds’ access completely — we cannot restore your wallet for you, and possession of your seed phrase is the only recovery method available. This setup ensures that your financial autonomy is never dependent on us.

You may also decline updates, although for your own security we strongly recommend applying them, especially when they include protocol improvements or critical fixes. You are free to disable internet connectivity when operating the app for offline signing or local privacy reasons, and doing so will not restrict access to your previously synced wallet data. If you ever disagree with changes to this policy or how the wallet operates, your choice to stop using it and migrate to another Zcash wallet remains intact — the network is decentralized and your keys work elsewhere. Our role is to provide secure tooling, not gatekeeping or custody. In every scenario, you stay in control: your data, your keys, your machine, your choice.

7. Cookies and Tracking

The wallet app itself does not use cookies. Cookies apply to our public website and documentation pages. We keep them minimal and avoid any tracking that does not serve a clear purpose for basic functionality or security.

You can use our website without accepting non-essential cookies. If you choose to block analytics or preference cookies, the core content remains available. Your browser also lets you clear cookies at any time.

• Essential Cookies: Required for basic site functions like page navigation, CSRF protection, and session integrity. These do not track your browsing across other sites.
• Analytics Cookies: Lightweight, privacy-focused analytics that help us understand page load performance and general usage patterns. We do not build behavioral profiles or sell data to advertisers.
• Preference Cookies: Save simple choices such as language or theme, so you do not need to set them on every visit.

We do not use social media pixels, cross-site trackers, or fingerprinting scripts on our site. If any third-party content is embedded (for example, a video), it follows that provider’s cookie policy. You can choose not to load such embeds.

8. International Data Transfers

Zcash Wallet is engineered so that sensitive wallet information never leaves your device. Private keys, seed phrases, transaction details, balances, and address data are not transmitted to us or stored by us — which means there is nothing meaningful for us to transfer internationally, intercept, or disclose. Traditional cross-border data concerns primarily apply to systems that centralize personal information; we avoid this model entirely.

In limited situations, certain non-sensitive, user-initiated data may cross regional boundaries. This occurs only when you choose to use optional features or request support. For example, if you voluntarily submit application logs to report a bug, that data may pass through secure infrastructure that can be located in another jurisdiction. Such logs contain no wallet secrets, are encrypted in transit, and are deleted once support is complete.

You remain the sole party capable of decrypting any encrypted backup stored externally. Storing an encrypted backup in a cloud service may result in the encrypted file traveling through foreign servers — but backup providers cannot read or extract any wallet content from it. The location of their storage systems never affects the confidentiality of your wallet data.

To keep this simple and transparent, international interaction only occurs when you explicitly choose it, and the data involved never includes your financial information or identity. For clarity, cross-border handling may apply to:

• User-submitted diagnostic logs (optional, redacted before sending, removed after use)
• Encrypted cloud backup files (optional, unreadable to service providers)
• Email communications with support (optional, contains only what you choose to share)

9. Data Retention

Zcash Wallet is designed to minimize the amount of data we handle. Most wallet activity — including your keys, balances, addresses, and transactions — exists only on your device and never reaches our servers.

Certain limited information may be temporarily processed if you choose to enable optional features (for example, encrypted cloud backups or error logs). This data is encrypted and removed once no longer required to provide the feature or support experience.

• Wallet keys & funds: Stored only on your device
• Error and crash logs: Purged automatically
• Support conversations: Retained only while resolving your issue
• Encrypted backup data: Removed if you disable backup features

If you request deletion of support data related to your inquiries, we will comply unless laws require temporary retention (for example, fraud prevention or security investigations).

10. Changes to This Policy

This Privacy Policy may be updated from time to time as the wallet evolves, new features become available, or regulatory environments change. Any modifications are made with a single priority in mind — preserving user privacy and strengthening security standards.

We do not alter data practices silently or retroactively. When changes are introduced, we will:

• Publish the updated policy on our website and within the wallet interface
• Clearly indicate the date of the most recent revision
• Provide advance notice for any material changes affecting how data is handled
• Maintain an accessible archive of previous versions for transparency

Updates will never introduce data collection mechanisms or weaken privacy guarantees without explicit user awareness and choice. If future features require additional optional data processing, users will be informed and given clear opt-in controls.