Privacy Policy

1. Overview

Zoetra is built around a simple principle: the blockchain is the only backend. This has direct privacy implications, described below, that are different from a typical web application.

2. We Do Not Operate User Accounts

Zoetra has no sign-up, no login, no username/password, no email collection, and no user database. We cannot identify "who you are" beyond the public wallet address you choose to interact with the Registry from.

3. What Data Exists, and Where

4. On-Chain Data Is Public and Permanent

Anything you submit to the Registry contract, your wallet address, device name, stake amount, heartbeat timestamps, is written to a public blockchain. This means:

• It is visible to anyone, indefinitely, including block explorers, chain analytics tools, and anyone running their own node.
• It cannot be deleted, redacted, or made private after the fact. Blockchains are append-only. If your jurisdiction's privacy law grants a "right to be forgotten" or similar right, be aware that this right cannot be technically fulfilled for data once committed to the chain. Do not register a device using a name or any field that contains personal information you are not comfortable making permanently public.
• Zoetra's dashboard is a read-only viewer over this public data. Removing the dashboard, or Zoetra ceasing to operate entirely, would not remove this data from the chain.

5. The One Server-Side Component: the Alert Relay

Zoetra includes exactly one server-side code path, a stateless serverless function at /api/alert. Here is precisely what it does and does not do:

• Does: when your browser detects (from public on-chain data it already read) that a device has breached its SLA, and you have configured a webhook URL, your browser sends a request to /api/alert containing the device ID, name, score, and your chosen webhook URL. The function validates the URL, forwards a short text message to it, and returns success or failure.
• Does not: store this request anywhere. There is no database, no logging pipeline, and no retention. Each request is processed and discarded.
• Does not: send data anywhere except the exact webhook URL you typed in yourself. It will refuse to relay to private/internal network addresses.

6. Cookies and Tracking

Zoetra does not use tracking cookies, analytics scripts, or advertising identifiers. Your wallet browser extension (MetaMask, etc.) may itself set its own storage or communicate with its own servers; that is governed by that extension's own privacy policy, not Zoetra's.

7. Local Storage

The only data Zoetra's frontend writes to your browser is the optional webhook URL described above, stored via standard browser localStorage, scoped to Zoetra's domain, and never transmitted anywhere except to the /api/alert relay when a breach fires. Clearing your browser storage removes it.

8. Third-Party Wallets and RPCs

When you connect a wallet, that wallet extension (not Zoetra) mediates the connection and may have its own data practices. When the dashboard reads chain data, it queries public RPC endpoints (e.g., rpc.botchain.ai) operated by BOT Chain's infrastructure providers, not by Zoetra; those requests are subject to those providers' own logging practices, which Zoetra does not control.

9. Children's Privacy

Zoetra is not directed at children and does not knowingly process data related to children, consistent with the fact that it collects no personal data at all beyond what a user voluntarily and publicly commits to a blockchain.

10. Changes to This Policy

This policy may be updated as the Service evolves (for example, if a future backend component is added). Material changes will be reflected in the "Last updated" date above and, where practical, noted in the project's public repository.

11. Contact

Questions about this Privacy Policy may be directed via the contact information listed in the project repository.