Legal
Privacy Policy
This policy explains how Cove approaches privacy, what standard web infrastructure may still observe, and how the product handles data around private settlement flows.
At a Glance
Quick Summary- Cove is built to shield payment details on-chain through zero-knowledge transaction flows rather than expose them publicly on Solana.
- Standard web infrastructure may still log operational metadata such as IP address, browser information, or request timing.
- We do not track, store, or sell the underlying financial data associated with private settlement activity.
1. Our Commitment to Privacy & Zero-Knowledge Architecture
- Cove is designed around privacy-preserving settlement on Solana. Our product goal is to reduce public linkage between sender, recipient, and payment flow where the underlying protocol allows it.
- Privacy here refers primarily to on-chain settlement mechanics, not to the total elimination of all internet or hosting metadata generated when you use a website.
- Cove is non-custodial and built to avoid creating a conventional user database of balances, profiles, or financial histories.
2. Information We Collect
- The interface may process wallet public keys, token selections, transaction payloads, and claim-link data needed to prepare, recover, or complete a transaction flow.
- Local browser storage may be used to preserve in-progress deposit or claim state so a user can recover from a refresh or interruption.
- We do not require traditional account registration for normal use of the app interface.
3. ZK-Proof Mechanics (How We Shield Your Data)
- Cove uses the Cloak SDK and zero-knowledge proof mechanics to support private settlement on Solana.
- On-chain amounts, sender-recipient linkage, and claim execution details are designed to be shielded through ZK-proof flows rather than publicly exposed as plain transfers.
- We do not track, store, or sell the underlying financial data associated with those shielded transactions outside the transient technical handling required to submit or recover them.
4. Data Handling by Third Parties (Vercel)
- Cove uses standard web infrastructure and hosting, including Vercel. Like many hosts, such providers may log basic connection data such as IP addresses, browser details, request metadata, and error logs.
- Wallet providers, RPC endpoints, and relay infrastructure may also process operational information needed to deliver the product experience.
- Those third parties operate under their own terms and privacy policies, which users should review independently.
5. Data Security & Retention
- Cove aims to minimize retention and avoid unnecessary collection. Some data may live only in browser storage, network logs, or ephemeral request handling.
- Because Cove is non-custodial, many core transaction artifacts exist only in the user's wallet, device state, or on-chain execution path rather than in a centralized Cove account system.
- Users should treat claim links and wallet environments as sensitive because unauthorized access can compromise funds even if the app itself is privacy-focused.
6. Data Rights & International Transfers
- Users may have local legal rights relating to personal data depending on jurisdiction, including rights to request information or object to certain processing.
- Because third-party infrastructure may operate across regions, some limited operational metadata could be processed internationally.
- Requests relating to Cove-controlled data will be evaluated in light of the non-custodial architecture and the limited categories of data we intentionally retain.
7. Contact
- Questions about this Privacy Policy or Cove's data-handling model should be directed through Cove's official public channels or documentation.
- Users should also review the privacy policies of wallets, RPC providers, and hosting vendors that participate in the experience.
- Continued use of the interface after policy changes constitutes acceptance of the updated policy.