DATA PRIVACY

Privacy Policy

We optimize route metrics with a focus on cryptographic integrity. Read how we manage order signatures, execution data, and routing metadata.

1. Information We Collect

We collect metadata associated with your multi-venue routing activities. This includes your public wallet addresses, requested trading thesis strings, routing paths generated, API request rates, and response latencies.

We do not collect or store private keys, seed phrases, or personal identity details. FLOPPA AI operates as a trust-minimized client interface.


2. How We Use Data

Your data is processed to optimize execution candidates and generate historical logs displayed inside your session dashboards. This includes:

  • Calculating spread performance differences across PolyMarket, Unhedged, and other venues.
  • Maintaining persistent order history states for tracking execution splits.
  • Profiling latency to adjust auto-routing algorithms in real-time.

3. Third-Party Venues

To complete trade executions, your submitted orders and instructions are relayed directly to external venues via public RPC nodes or API endpoints. This processing is governed by the respective privacy frameworks of those third-party platforms. We recommend reviewing their privacy declarations prior to executing significant order volume.


4. Cryptographic Security Measures

All communication with the FLOPPA routing network is encrypted in transit using TLS 1.3. Developer API credentials are saved securely in local storage, and execution payloads are signed directly on the client side whenever possible to keep keys in the custody of your preferred browser extension or local hardware wallet.