Skip to content
Bitfork
Back to swap

What this app sees

Most apps publish a privacy policy written to protect the company. This page is the opposite: a plain list of every network request Bitfork makes, who receives what, and the things we genuinely cannot protect you from.

What we collect

Nothing. Specifically:

  • No account, email address, username, or password
  • No cookies — our server sends no Set-Cookie header at all
  • No analytics, no telemetry, no tracking pixels, no session recording
  • No third-party scripts or fonts loaded from other domains
  • No KYC, no identity documents, no phone number
  • No location or IP checks — we do not inspect where you are to decide whether to serve you
  • No custody — your keys never leave your wallet
  • No database. We have nowhere to store anything about you

There is no user database to breach because there are no users in a database.

Every request this app makes

Swapping requires talking to other services. Here is all of them.

  • LI.FI (li.quest)

    When
    Every time you request a quote
    Receives
    Your wallet address, your IP address, and the amounts you enter
    Why
    Finding the best route needs to know who is trading what

  • LI.FI (scan.li.fi)

    When
    While a swap or bridge is in progress
    Receives
    Your transaction hash and your IP address
    Why
    Tracking whether your transfer completed

  • Tenderly (api.tenderly.co)

    When
    Before you sign, on some routes
    Receives
    The simulated transaction and your IP address
    Why
    Previewing the outcome so a bad transaction can be caught first

  • Your wallet's own node provider

    outside our control
    When
    Constantly, while your wallet is open
    Receives
    Your address, IP, balances, and browsing of dapps
    Why
    Your wallet needs chain data. MetaMask uses Infura by default

  • Our web host

    When
    When you load the page
    Receives
    Your IP address and browser user-agent, in standard server logs
    Why
    Unavoidable for any web server. We add no tracking of our own

  • The blockchain itself

    outside our control
    When
    The moment you execute
    Receives
    Everything: addresses, amounts, timing, forever
    Why
    This is what a public ledger is

  • Hyperliquid (api.hyperliquid.xyz)

    When
    While the Perps tab is open and a wallet is connected
    Receives
    Your wallet address and your IP address
    Why
    Balances, positions, and mark prices. Your browser talks to Hyperliquid directly — we do not proxy it

  • Hyperliquid exchange

    When
    When you approve the builder fee or place an order
    Receives
    Your address, the signed action, and your IP address
    Why
    Approvals and orders are Hyperliquid L1 actions. Bitfork never holds keys

  • Circle CCTP on Arbitrum

    When
    When you deposit USDC into Perps from this app
    Receives
    Your Arbitrum address, USDC amount, and your IP at the RPC
    Why
    Native USDC is burned on Arbitrum and credited to your Hyperliquid perps account. We do not take custody

  • Bitfork Welcome pass (Arbitrum NFT)

    When
    When you complete How to trade the first time
    Receives
    Your wallet address, on a public chain
    Why
    A non-transferable token records that you accepted perps terms. That is the record. We do not keep a user list off-chain

What we cannot protect you from

  • The chain is permanently public

    Every swap you make is recorded on a global, replicated ledger that is never deleted and can be read by anyone forever. Firms like Chainalysis and Arkham exist specifically to link addresses to identities. Nothing a website does can change this.

  • Your wallet talks to its own servers

    Even with a perfectly private interface, your wallet software reports to its own node provider. If you use MetaMask with default settings, Infura sees your address and IP regardless of what we do.

  • Your network sees that you were here

    Your ISP, and any VPN you use, can see that you connected to this site, even though they cannot see what you did inside it.

Don't take our word for it

Every claim above is checkable in about two minutes.

  1. 1Open your browser devtools, Network tab, and watch every request this page makes. It should match the table above exactly.
  2. 2Check the Application tab for cookies and local storage. You will find no cookies from us.
  3. 3View source. There are no third-party script tags.
  4. 4Read the code. The whole app is open and the fee logic lives in one file.

If this page ever stops matching what the app actually does, that is a bug and we want to hear about it. Changing this list is part of shipping a change, not an afterthought.