KeyBay KeyBay Capital Bitcoin L1 Yield Launch App

Privacy Policy

Last updated: March 15, 2026

1. Information We Collect

KeyBay Capital operates on a minimal data collection principle consistent with pseudonymous blockchain infrastructure.

  • Wallet Addresses: Public Bitcoin and OP_NET addresses you connect to the platform. These are inherently public on-chain.
  • Transaction Data: Deposit intents, withdrawal requests, and credit vault interactions you initiate through the platform.
  • API Usage: Request metadata (timestamps, endpoints called) for s402 paywall and rate limiting purposes.
  • Server Logs: Standard HTTP access logs (IP address, user agent, request path) retained for security and debugging.

2. Information We Do Not Collect

  • We do not collect names, email addresses, phone numbers, or government IDs.
  • We do not use cookies for tracking or advertising purposes.
  • We do not use third-party analytics services.
  • We never have access to your private keys or seed phrases.

3. How We Use Information

Collected information is used solely for: processing your deposit and withdrawal requests, executing smart contract interactions, monitoring system health and security, enforcing rate limits and preventing abuse, and maintaining audit logs for operational integrity.

4. Data Storage

Transaction records and operational data are stored on our backend infrastructure hosted on Render (Oregon, US). On-chain data is permanently recorded on the Bitcoin blockchain and OP_NET execution layer. We do not control on-chain data once broadcast.

5. Data Sharing

We do not sell, trade, or rent your information to third parties. We may disclose information if required by law, subpoena, or legal process, or to protect the safety and security of the platform and its users.

6. On-Chain Transparency

All vault deposits, withdrawals, and credit operations are recorded on Bitcoin L1 and OP_NET. This data is publicly viewable by anyone with access to a blockchain explorer. By using the Service, you acknowledge and accept this inherent transparency.

7. Security

We implement reasonable technical safeguards including CORS restrictions, admin authentication, encrypted transport (TLS), and access logging. However, no system is completely secure. Use the Service at your own risk.

8. Changes

We may update this Privacy Policy from time to time. Material changes will be communicated through the platform. Continued use constitutes acceptance.

9. Contact

For privacy-related inquiries, reach out through our public channels or open an issue on GitHub.