Privacy and data handling

Last updated: July 19, 2026

​

1. Privacy boundary

Flew uses Arcium confidential computation to protect position sides and live aggregate pool state. Solana remains a public blockchain, and Flew also operates off-chain services required for authentication, transaction preparation, position history, analytics, and error monitoring.

​

2. Public Solana data

When you interact with Flew, public on-chain data can include:

• Your Solana wallet address
• The market and program accounts you interact with
• Transaction signatures, slots, timestamps, and status
• Your position amount and associated SOL transfers
• The fact that you placed, exited, claimed, or refunded a position
• Public exit, payout, and refund amounts emitted or transferred during settlement
• Market questions, configuration, creator, resolver, oracle settings, and deadlines
• Aggregate YES and NO pool totals revealed at resolution

Blockchain data is permanent and can be copied or analyzed by third parties. Flew cannot delete confirmed Solana history.

​

3. Data protected during an active market

The current protocol encrypts:

• Your YES or NO side in the on-chain position account
• The live aggregate YES and NO pool totals
• Intermediate pool updates used by Arcium computations

Your position amount is not encrypted on-chain. It is supplied as a plaintext lamport amount so the program can bind the pool credit to the SOL transferred. At resolution, Arcium reveals aggregate pool totals. The encrypted side stored in each individual position account is not published as plaintext by the normal resolution flow.

​

4. Data processed by Flew services

Flew’s API processes data needed to prepare and display positions, including:

• Privy account identifier
• Wallet address
• Market and position account addresses
• Position amount and side
• Per-position encryption key material generated while preparing the transaction
• Encrypted position data used to recover position details for an authenticated account

Flew stores a user record that links a Privy identifier to a wallet address. Flew also stores position records containing the wallet, market, amount, side, and encrypted position data. Access controls restrict authenticated position-history requests to the Privy account linked to the wallet. No access control eliminates all security risk.

​

5. Authentication

Flew uses Privy for email and wallet authentication. Depending on how you sign in, Privy may create and manage an embedded Solana wallet or connect an external wallet. Privy’s handling of authentication identifiers, embedded wallets, and linked accounts is governed by Privy’s own terms and privacy practices.

​

6. Analytics and diagnostics

The Flew web interface uses PostHog for product analytics. After authentication, Flew identifies the PostHog profile using the connected wallet address. Analytics events can include:

• Page views and page-leave activity
• Wallet authentication events
• Markets and events viewed
• Market lifecycle and settlement interactions
• Position market, side, amount, and wallet
• Payout, refund, and settlement interactions
• Browser, device, referrer, and session metadata collected by the analytics SDK

Flew uses Sentry for errors, performance traces, and session replay. The current client configuration masks text and blocks media in replay recordings, but diagnostic events can still include request, device, network, account, or interaction metadata. Flew’s shared Sentry configuration permits default personally identifiable information.

​

7. Other service providers

Flew relies on service providers that may process data needed for their role:

• Solana: Public transaction execution and account state
• Arcium: Confidential computation and callbacks
• Switchboard: Verified oracle quotes for applicable markets
• Privy: Authentication and embedded wallet services
• PostHog: Product analytics
• Sentry: Error, performance, and replay monitoring
• Database and hosting providers: API, web application, and off-chain record storage
• Market-data providers: Price and candle information displayed for supported crypto markets

Review each provider’s policies before using Flew.

​

8. How Flew uses data

Flew uses the data it processes to:

• Authenticate accounts and link wallets
• Prepare and submit market transactions
• Display position history and settlement status
• Operate market metadata and event listings
• Detect errors, abuse, and service failures
• Analyze feature usage and improve the interface
• Comply with applicable legal obligations

Flew does not claim that off-chain position data is hidden from Flew’s own services.

​

9. Retention and deletion

On-chain Solana data cannot be deleted by Flew. Off-chain user, position, analytics, and diagnostic records are retained according to operational, security, and legal requirements. Deleting an authentication account does not remove public Solana history or copies held independently by service providers. Where applicable, you may request access, correction, or deletion of off-chain personal data. Some records may be retained when required for security, fraud prevention, dispute handling, or legal compliance.

​

10. Security

Flew uses wallet signatures, authenticated API routes, encrypted position-data storage, Solana program constraints, verified oracle quotes, and Arcium callbacks. These controls reduce risk but do not guarantee security or uninterrupted availability. Never share your wallet seed phrase or wallet private key with Flew. Position-encryption key material used by Flew is separate from the private key that controls your Solana wallet.

​

11. Children and jurisdiction

Flew is not intended for anyone under 18 or below the legal age required in their jurisdiction. You are responsible for determining whether your use of prediction markets and digital assets is lawful where you live.

​

12. Updates and contact

Flew may update this page when its protocol, interfaces, providers, or data practices change. For questions or data requests, use the Flew feedback form or contact Flew through @flewislive on X.