Security & Privacy

Our security architecture, custody models, and precise privacy boundaries.

Key Handling & Custody Model

Agents operate via ERC-4337 smart contract wallets, not standard Externally Owned Accounts (EOAs).

  • No raw private keys are exposed in the browser, database, or application code.
  • The Owner retains ultimate control over funding and policy configuration.
  • Agents are granted strictly scoped access keys capable only of proposing UserOperations to the bundler.

Privacy Boundaries

What Shielded ZEC Protects

  • The source of your funding on the Zcash network.
  • The exact amounts of ZEC sent (if fully shielded).
  • The contents of any encrypted memos attached to the transaction.

What is NOT Private

  • Robinhood Chain activity is inherently public.
  • Agent wallet addresses and deployed smart contracts.
  • Transaction history, destinations, and amounts spent by the agent.
  • The complete funding-to-spending link (via behavioral/timing analysis).

Limitations

Please note the following current systemic limitations:

  • Test Mode: The current environment is intended for testnet operations.
  • Pending Integrations: Provider integrations are continuously evolving and may have downtime.
  • No Audited Contracts: While we use standard ERC-4337 infrastructure, our specific proxy implementations have not yet undergone a formal security audit.

API Security

All API endpoints enforce strict rate limiting and robust authentication. Agent credentials are cryptographically hashed before storage. Audit logging captures all policy changes, funding events, and execution requests, ensuring total accountability for actions taken within the system.

Incident Response

Report a Vulnerability

We take security seriously. If you believe you have found a vulnerability in ZECPilot, please report it to our security team.

Contact: security@zecpilot.example.com