Privacy Policy

Last Updated: October 26, 2026

1. Introduction

This Privacy Policy describes how Zenland DAO ("Protocol," "we," "us," or "our") handles information when you use our decentralized escrow protocol and related services.

Zenland DAO is fundamentally different from traditional web services. We are a decentralized protocol that prioritizes user privacy by design. This policy explains our approach to privacy and what limited information interactions may involve.

πŸ›‘οΈ Privacy by Design

Zenland DAO is designed with privacy as a core principle. We never ask for your name, email or other contact details, and we don't sell data or use it for advertising. Specifically:

  • No backend servers - The Protocol is a frontend interface only
  • No databases - We don't run databases holding your personal information
  • Usage analytics only - We measure how the interface is used, not who you are, and never link it to your wallet address (see section 5)
  • No user accounts - You connect with your own wallet, no registration required

2. Blockchain Data

When you use the Protocol to create or interact with escrows, your transactions are recorded on the Ethereum blockchain. This is a fundamental characteristic of blockchain technology, not a choice by the Protocol.

Blockchain data that becomes publicly visible includes:

  • Your wallet address
  • Transaction history and amounts
  • Escrow creation, release, and dispute resolution records
  • Hash of escrow terms (not the terms themselves)

This blockchain data is permanent, publicly accessible, and cannot be deleted by anyone. This is inherent to blockchain technology and is outside our control.

3. Wallet Connection

When you connect your wallet to use the Protocol, the connection is handled directly by your wallet provider (e.g., MetaMask, WalletConnect). We do not receive or store your wallet credentials, seed phrases, or private keys.

Your wallet address is visible to the Protocol only during your active session and is not stored or logged on any server.

4. Browser Local Storage

The Protocol may use your browser's local storage to save:

  • Your UI preferences
  • Theme settings (dark/light mode)
  • Language preferences

This data is stored only on your device and is never transmitted to us or any third party. You can clear this data at any time through your browser settings.

5. Analytics

To understand how the interface is used, what to improve and what breaks, we use these analytics and error-monitoring services:

  • Google Analytics (Google LLC) - records page visits, device, browser and operating system, approximate location (country and city, derived from your IP address), the website that referred you, and interface actions such as opening the wallet dialog, moving through the escrow form, or a transaction failing. It sets first-party cookies (_ga, _ga_*) to recognize repeat visits.
  • Microsoft Clarity (Microsoft Corporation) - records how pages are used (clicks, scrolling, mouse movement) to produce heatmaps and session replays. Text typed into form fields is masked; replays can show public information displayed on the page, such as shortened wallet or escrow addresses. It sets cookies such as _clck and _clsk.
  • Sentry (Functional Software, Inc.) - receives a report when something breaks in the interface: the error and where it happened in the code, the page, browser, device and operating system, your IP address, and the interface steps leading up to the error. For sessions with an error it also keeps a short replay of the page with all text and images masked. Wallet addresses are removed from error reports before they are sent.

We don't send your wallet address, the amounts or terms of your escrows, or what you type into forms to these services, and we use the data only in aggregate to improve the interface. Page addresses reported to them can include public escrow or agent contract addresses when you view those pages. To tell which recording belongs to which error, each browser tab gets a random visit ID that is shared between Clarity and Sentry; it is not derived from your wallet. Google, Microsoft and Sentry process this data under their own privacy policies (policies.google.com/privacy, privacy.microsoft.com/privacystatement and sentry.io/privacy).

You can opt out at any time by blocking cookies for this site in your browser, using a content blocker, or installing Google's opt-out add-on (tools.google.com/dlpage/gaoptout). The interface works fully without analytics.

6. Third-Party Services

The Protocol may interact with third-party services to function:

  • Blockchain RPC providers (to read blockchain data and submit transactions)
  • Wallet providers (to enable wallet connections)
  • Blockchain indexers (to query historical data)

These third-party services have their own privacy policies. We encourage you to review their policies. We have no control over and assume no responsibility for their privacy practices.

7. PDF Documents

When you create an escrow, a PDF document containing the terms may be generated in your browser. This PDF is generated entirely client-side and is not uploaded to or stored on any server.

You are responsible for storing and managing your escrow PDF documents. We do not have copies of these documents.

8. Your Rights

We don't hold personal information such as your name or contact details. You can limit analytics collection as described in section 5. If you want analytics data associated with your browser deleted, contact us (section 11) and we will request its deletion from the provider.

For blockchain data: Due to the immutable nature of blockchain technology, on-chain data cannot be modified or deleted. This is a fundamental characteristic of public blockchains.

9. Children's Privacy

The Services are not intended for individuals under 18 years of age. We do not knowingly provide services to minors. If you are under 18, please do not use the Services.

10. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page with an updated "Last Updated" date.

11. Contact

If you have questions about this Privacy Policy, please reach out through our community channels at DAOForum.org or our Telegram community.

Related Documents: