{
  "$schema": "https://thesalestraveler.com/data/schema/web3-policy.schema.json",
  "policyId": "onchain-data-use",
  "title": "What On-Chain Data Would (and Would Not) Be Used For",
  "status": "active-limited",
  "effective": "2026-08-12",
  "lastReviewed": "2026-08-12",
  "summary": "A plain, itemized list of which on-chain data points this site's contract-backed token gating and loyalty reads use when RPC and deployed contract addresses are configured, and which data they explicitly do not use.",
  "wouldUse": [
    { "dataPoint": "Balance of a specific, named ERC-20/721/1155 token at a connected address", "reason": "The single mechanism for a token-gating rule (e.g. 'holds 1+ of collection X')." },
    { "dataPoint": "Membership in a specific, named allowlist or attestation registry", "reason": "An alternative or complementary gating rule that doesn't require holding a token." },
    { "dataPoint": "A loyalty/soulbound badge balance issued by this site itself (if built)", "reason": "Powers the on-chain loyalty tier shown at /web3/loyalty/, scoped to badges this site itself issues." }
  ],
  "wouldNotUse": [
    { "dataPoint": "General transaction history or counterparties of a connected wallet", "reason": "Not needed for any disclosed feature; reading it would be surveillance beyond the stated purpose." },
    { "dataPoint": "Holdings of unrelated tokens/NFTs not tied to a specific published gating rule", "reason": "Prevents silently profiling a wallet's broader portfolio." },
    { "dataPoint": "DeFi positions, staking history, or DAO voting history", "reason": "Out of scope for gating, loyalty, or attribution as defined on this site." },
    { "dataPoint": "Cross-chain identity graphs from third-party wallet-analytics vendors", "reason": "This site does not purchase or query third-party wallet-profiling data." }
  ],
  "howReadsWouldWork": "On-chain reads happen server-side through the configured RPC endpoint at the moment of a specific action (loading a contract-gated item or checking loyalty status). If the RPC endpoint or deployed addresses are missing, the backend returns an explicit unavailable state instead of fabricating a chain result.",
  "auditability": "Contract addresses, chain id, and deployment metadata are published in /data/web3/contracts.json and the live behavior is reflected by /api/v1/config and /api/v1/health.",
  "relatedDocs": {
    "spec": "/web3/spec/wallet-gating/",
    "loyaltyLandingPage": "/web3/loyalty/",
    "backendDoc": "/web3/backend/",
    "walletPrivacyPolicy": "/web3/policy/wallet-privacy.json"
  }
}
