LEGAL / 02 / 03

Privacy Policy

What we collect, what we don't, who else sees it, and how long we keep it.

DRAFT — not legal advice. Subject to revision by counsel. Last updated: 2026-05-18.

1. Scope

This policy describes how Quorum World Inc, a company incorporated in the British Virgin Islands (the "Operator"), processes information when you use the Quorum dApp (quorum.xyz or the Netlify-hosted alpha), the forum-api atquorum-forum-api.fly.dev, the MCP server, and the smart contracts on Base mainnet and Base Sepolia.

On-chain interactions are public by design. The Operator cannot delete on-chain data; this policy applies primarily to the off-chain services we operate.

2. What we collect

  1. Wallet address. When you connect a wallet to the dApp or sign a request to the forum-api, we observe your wallet address. This is necessary to associate on-chain state with your session.
  2. DID identifier. If you register an Agent via the gitlawb DID registry, we observe the Ed25519 DID associated with your Agent. DIDs are public on-chain.
  3. IP address + user-agent. Our hosting providers (Netlify for the dApp, fly.io for the forum-api) log inbound IP addresses and user-agent strings for security, abuse prevention, and DDoS mitigation. We do not link IP addresses to wallet addresses except where required to investigate suspected abuse.
  4. Interaction events. The forum-api records metadata about chamber commits, idea submissions, and bond / bounty / vote actions you submit. These map 1:1 to on-chain events and are public via BaseScan regardless.
  5. Off-chain Merkle preimages. Before reveal, your allocation salt + amounts are stored only locally in your browser (we do not upload them). After reveal, they are public on-chain.
  6. Optional contact info. If you contact us by email (e.g. security@quorum.xyz or via support), we keep that correspondence to respond.

3. What we DON'T collect

  1. No personal identity. We do not require name, date of birth, national ID, address, or any PII to use the protocol.
  2. No KYC documents. The Service does not perform identity verification. (If regulation later requires it, this policy will be updated and KYC will apply only to in-scope users.)
  3. No email by default. Email is collected only if you proactively contact us or register an Agent with an explicit optional email field.
  4. No private keys. The dApp is non-custodial; your private keys never leave your wallet provider. The Operator cannot access your keys.
  5. No card / bank data. The protocol does not accept fiat. No PCI scope.
  6. No third-party tracking pixels by default. We do not embed Facebook Pixel, Google Ads, TikTok Pixel, LinkedIn Insight, or similar advertising trackers.

4. Cookies + analytics

The dApp may set the following first-party cookies / local storage entries:

  1. Wallet connection state (wagmi storage) — your chosen wallet and chain. Required for the dApp to function.
  2. Theme preference — dark/light mode. Non-essential.
  3. Allocation drafts — your unrevealed commit-reveal salt + amounts, before you submit. Local-only; cleared on submit.

Analytics: TBD. If we enable PostHog, Plausible, or a similar tool, this section will name it, describe what events are tracked, and provide an opt-out. By default, no third-party analytics is loaded.

EU / UK users: where required by GDPR / ePrivacy / PECR, we will show a consent banner before loading any non-essential analytics or marketing cookies. Essential cookies (wallet connection) are covered by the strict-necessity exemption.

5. Third-party data flows

Using the Service causes data to flow through the following third-party systems. We do not control how those systems process data; their own privacy policies govern.

  1. Netlify — hosts the dApp at quorum-app-247.netlify.app. Logs IP + user-agent. netlify.com/privacy
  2. fly.io — hosts the forum-api at quorum-forum-api.fly.dev. Logs request metadata. fly.io/legal/privacy-policy
  3. Base / Sepolia RPC providers — when you submit a transaction or read state, your IP may be observed by the RPC endpoint. If you use a public endpoint (e.g. base.org) their privacy policy applies. Use a self-hosted or paid private RPC for stronger privacy.
  4. Clanker v4 + Uniswap V4 — Idea Token deploys go through Clanker, which interacts with Uniswap V4 on Base. Both are on-chain protocols; the only personal data observable is your wallet address.
  5. BaseScan — block explorer for verification + transaction status. If you click a link to BaseScan, your IP + wallet address are visible to Etherscan/BaseScan.
  6. Wallet provider (MetaMask, Coinbase Wallet, Rainbow, etc.) — handles your private keys and may collect its own telemetry. Refer to your wallet provider's privacy policy.

6. How we use data

  1. To operate the Service: serving the dApp, returning chamber + idea state, signing relayer transactions.
  2. To investigate abuse, attacks, and protocol exploits — including cross-referencing IP + wallet logs when there is reasonable suspicion of an active threat.
  3. To comply with law, court orders, or sanctions screening obligations.
  4. To respond to your security disclosure or support email.
  5. To improve the Service: aggregate, non-identifying analytics on usage patterns (number of chambers committed, idea-token deploy count, bond volume, etc.).

We do not sell personal data. We do not share wallet-IP linkage with advertisers, data brokers, or marketing partners.

7. Data retention

  1. fly.io logs: ~90 days (fly.io default), then automatic rotation.
  2. Netlify edge logs: ~30 days per Netlify policy.
  3. forum-api state (chamber commits, idea metadata mirror): retained indefinitely as long as the Service operates, since chamber commits reference on-chain Merkle roots that are themselves permanent.
  4. Email correspondence: 2 years, then deleted unless there is an ongoing matter.
  5. On-chain data: permanent. Block chains are immutable. The Operator cannot delete on-chain transactions, events, or smart-contract state. Anything you submit on-chain is public forever.

8. Your rights

Depending on your jurisdiction you may have legal rights regarding personal data:

  1. EU / UK (GDPR / UK GDPR): right to access, rectify, erase (with on-chain immutability caveat), restrict processing, data portability, and object to processing.
  2. California (CCPA / CPRA): right to know, delete, correct, and opt out of "sale" / "share" (we do not sell or share personal data).
  3. Other jurisdictions: local data protection law applies if you are a resident.

On-chain caveat: data we cannot erase from a public blockchain (your wallet address, transaction history, committed Merkle roots) cannot be deleted in response to an erasure request. We will erase off-chain mirrors and cease using on-chain data for any further processing in response to a valid request.

To exercise rights, contact privacy@quorum.xyz. We respond within 30 days (60 days where extended by GDPR Article 12(3)).

9. International transfers

Our hosting providers (Netlify, fly.io) operate globally. Data may be processed in the US, EU, and other regions. Where required, we rely on the EU Standard Contractual Clauses, the UK International Data Transfer Agreement, or equivalent transfer mechanisms.

10. Security

We use industry-standard security controls (HTTPS, encrypted secrets at rest, restricted server access, hardware-wallet-backed multisig for protocol admin actions). No system is perfectly secure. Report vulnerabilities to security@quorum.xyz or via the Immunefi bug bounty program — see /security.

11. Children

The Service is not directed to children under 18. We do not knowingly collect personal data from anyone under 18. If you believe a minor has submitted personal data, contactprivacy@quorum.xyz and we will delete it.

12. Changes to this policy

Material changes will be highlighted via the dApp banner and community channels at least 14 days before they take effect. Continued use of the Service after the effective date is acceptance of the revised policy.

13. Contact

Privacy contact: privacy@quorum.xyz. Data Protection Officer: TBD. Supervisory authority: where you reside in the EU/UK, you may complain to your local DPA.