SecurityInstitutionalSupportAgentDashboard
Privacy

Minimal data, explicit operational boundaries.

Clover is built to reduce strategy leakage, not to collect more metadata than necessary. The platform keeps persistent server-side data intentionally narrow and avoids storing plaintext financial details where the product can operate without them.

What Clover stores

  • Linked wallet identities required for authentication and account ownership checks.
  • Execution metadata such as route status, chain, tx hash, timestamps, and operational error states.
  • User profile preferences needed to make the dashboard behave consistently across sessions and devices.

What Clover avoids storing

  • Plaintext execution recipients and transfer amounts when the product can recover that context from chain data instead.
  • Confidential vault balances in decrypted form after the user closes their decryption session.
  • Wallet private keys or signing authority outside the wallet providers the user explicitly connects.

Operational note

Private execution hides intent from public orderflow only to the extent supported by the selected route, wallet, chain infrastructure, and settlement conditions at the time of submission. Privacy is improved, not absolute.