Beta privacy policy draft.
This preview describes the protocol's visibility boundary but cannot define operator data practices until the operator, infrastructure, retention, and jurisdiction are known.
Draft identity
Effective date: [EFFECTIVE DATE]. The intended data controller is [LEGAL ENTITY], contactable at [CONTACT EMAIL]. Those fields are unresolved, so this page is not a final privacy notice. Applicable privacy law and user-rights procedures depend on [GOVERNING LAW] and the jurisdictions actually served.
Protocol visibility
Only pre-trade RFQ intent is private/offchain; shield deposits, contract balances, final fills, and unshield withdrawals are public onchain.
Hunty makes no ZK, anonymity, confidential-balance, or hidden-settlement claim. RFQ operators and contacted solvers can process request details before execution; blockchain observers can analyze public transactions and state after onchain actions.
Operator data practices to define
A final policy must inventory the actual interface, hosting, RPC, logging, analytics, support, security, and RFQ infrastructure. It must then state data categories, purposes, legal bases, recipients, international transfers, retention periods, security controls, and user-rights procedures. None of those vendors or practices is asserted in this draft.
Public-chain permanence
Public blockchain data is replicated by independent network participants and may be indexed by third parties. [LEGAL ENTITY] may be unable to alter or erase onchain records. The final notice must explain how requests can be submitted to [CONTACT EMAIL] and which rights apply under [GOVERNING LAW].