Effective Date: April 22, 2026
This document contains the Privacy Policy governing use of the Flew Protocol. Please read carefully before using the protocol.

1. Introduction

This Privacy Policy describes how Flew Protocol collects, uses, stores, and discloses information in connection with your use of the Protocol. By using the Protocol, you acknowledge that you have read and understood this Privacy Policy. Flew Protocol is designed with privacy as a core architectural principle. The Protocol uses confidential computation to protect live betting state. However, interaction with any blockchain involves inherently public data. This Privacy Policy explains the boundary between what the Protocol protects and what it cannot.

2. Information We Collect

2.1 On-Chain Data (Inherently Public)

Blockchain networks are public ledgers. The following information is publicly visible on Solana for any user who interacts with the Protocol and cannot be made private by Flew:
  • Wallet addresses that initiate transactions with Protocol smart contracts
  • Transaction hashes, block timestamps, and confirmation data
  • Market creation events, including creator wallet address, bond amount, and market parameters
  • The fact of bet placement (i.e., that a wallet submitted a transaction to the Protocol), even though bet size and side remain encrypted during the live phase
  • Claim and refund events following market resolution
  • On-chain policy configuration and market state data
Users should be aware that third parties, including blockchain analytics services, may correlate publicly available on-chain data with off-chain identity information without Flew Protocol’s involvement or consent.

2.2 Data Protected by Confidential Computation

The following data is encrypted through Arcium’s MPC pipeline and is not exposed in plaintext on-chain during the live market phase:
  • Bet amounts
  • Bet side (YES or NO)
  • Intermediate YES/NO pool accounting state during the live market phase
At resolution, only the aggregate pool values necessary to compute settlement ratios are revealed. Individual bet-level data is not disclosed during normal protocol operation.

2.3 Off-Chain Interface Data

If you access the Protocol through a web, mobile, or third-party interface (including any front-end operated by Flew or by an Integrator), that interface may collect:
  • IP addresses and device identifiers for security and abuse prevention purposes
  • Browser type, operating system, and session duration
  • Wallet connection events and interaction logs within the interface
  • Any information you voluntarily submit through contact forms or community channels
Data collected by third-party integrators is governed by those integrators’ own privacy policies. Flew Protocol is not responsible for integrators’ data practices.

3. How We Use Information

Flew Protocol uses the information it has access to for the following purposes:
  • Protocol operation: Operating smart contracts, processing computational callbacks, managing market lifecycles, and facilitating settlements
  • Security and integrity: Detecting and preventing fraudulent, abusive, or unauthorized use of the Protocol
  • Protocol improvement: Analyzing aggregate, non-identifying on-chain activity to improve Protocol design, fee structures, and market policy configurations
  • Communications: If you have engaged with Flew Protocol through official channels, responding to inquiries and providing protocol updates
  • Legal compliance: Complying with applicable legal obligations, including responding to lawful requests from governmental authorities
Flew Protocol does not sell, rent, or trade personal information to third parties for marketing or commercial purposes.

4. Sharing and Disclosure

4.1 Arcium Infrastructure

Bet inputs are transmitted to Arcium’s MPC node network for confidential computation. This is a necessary and fundamental component of the Protocol’s architecture. Arcium’s nodes process encrypted inputs without the ability to observe plaintext values. You should review Arcium’s own privacy and security documentation for a complete understanding of how MPC execution is handled at the infrastructure layer.

4.2 Integrators

If you access the Protocol through an Integrating platform, that platform may have access to your wallet address and on-chain interaction data consistent with what is publicly visible on Solana. Flew Protocol may share aggregate protocol usage statistics with Integrators for the purpose of fee reconciliation and analytics. Flew Protocol may disclose information if required to do so by law, regulation, legal process, or governmental authority. We will endeavor to notify you of such disclosure to the extent permitted by law.

4.4 Business Transitions

In the event of a merger, acquisition, restructuring, or sale of substantially all Protocol assets, user information may be transferred as part of that transaction. Users will be notified through official Protocol channels prior to any such transfer.

5. Data Retention

On-chain data is permanent by the nature of public blockchains. Flew Protocol cannot delete or modify on-chain transaction history. For any off-chain data held by Flew Protocol or associated interfaces, we retain such data only for as long as necessary to fulfill the purposes set out in this Privacy Policy, subject to applicable legal retention obligations.

6. Security

Flew Protocol employs the following measures to protect data and protocol integrity:
  • Confidential computation via Arcium’s MPC infrastructure for sensitive bet and pool state
  • X25519 key exchange and Rescue-based encryption for encrypted protocol inputs
  • Verified callbacks that validate computation outputs before applying on-chain state transitions
  • Smart contract access controls and policy-enforcement mechanisms
Despite these measures, no system is perfectly secure. You are responsible for maintaining the security of your own wallet, private keys, and seed phrases. Flew Protocol will never ask for your private key or seed phrase.
You are solely responsible for the security of your wallet credentials. Loss of private keys or seed phrases cannot be reversed by Flew Protocol and will result in permanent loss of access to associated funds.

7. Children’s Privacy

The Protocol is not directed at individuals under the age of 18. Flew Protocol does not knowingly collect information from minors. If you believe that a minor has used the Protocol, please contact us through our official channels.

8. Cross-Border Data

The Protocol operates on a global, permissionless blockchain infrastructure. On-chain data is replicated across globally distributed Solana validator nodes by design. Any off-chain data held by Flew Protocol may be processed in jurisdictions other than your own. By using the Protocol, you consent to the cross-border transfer of data to the extent necessary for protocol operation.

22. Your Rights

Depending on your jurisdiction, you may have rights regarding your personal data including:
  • The right to access information we hold about you (to the extent that information is off-chain)
  • The right to request correction of inaccurate off-chain data
  • The right to request deletion of off-chain data (subject to legal retention obligations)
  • The right to object to or restrict certain processing activities
Please note that on-chain data is immutable and cannot be deleted in response to such requests. To exercise your rights regarding any off-chain data, contact us through the official channels listed below.
The Protocol may integrate with or reference third-party platforms, wallets, or protocols. This Privacy Policy applies only to data handled by Flew Protocol. We encourage you to review the privacy practices of any third-party services you interact with in connection with your use of the Protocol.

24. Updates to This Privacy Policy

This Privacy Policy may be updated from time to time to reflect changes in the Protocol, applicable law, or our data practices. Material updates will be communicated through Flew Protocol’s official channels. Continued use of the Protocol following an update constitutes your acceptance of the revised Privacy Policy.

25. Contact

For questions, concerns, or requests related to these Terms and Conditions or this Privacy Policy, please contact Flew Protocol through our official channels:
  • Twitter/X: @flewlive_
  • For legal and data protection inquiries, contact information will be published on the Protocol’s official documentation portal
These Terms and Conditions and Privacy Policy are provided for informational purposes and do not constitute legal advice. Users are encouraged to seek independent legal counsel regarding their use of the Protocol in their respective jurisdictions.

© Flew Live · April 22, 2026 · flew.live