Privacy

Analytics (Google Analytics 4)

We use Google Analytics to see how the site is used and where visitors come from.

• Page views: the page address without your token pair, campaign tags such as utm_source, the page title, the referring site, and your browser and device type. Google receives your IP address when your browser contacts it and uses it to estimate your approximate location.
• Wallet connected: the wallet type only, for example MetaMask.
• Quote requested, swap submitted, swap completed: the chain, the token symbols, the price provider, and the approximate USD value of the trade.
• Bridge quote requested, bridge order created, bridge delivered: the two asset names only, for example bitcoin.btc and robinhood.eth. A Robinhood Chain token picked by its address is sent as robinhood.token.

Your wallet address and your transaction hashes are never sent to Google Analytics.

Cookies

Google Analytics sets cookies (_ga and _ga_…) to tell returning browsers apart. You can block or delete these cookies in your browser settings. The site itself stores nothing else in your browser.

Your wallet and your swaps

To compare prices and build a swap, the site sends your tokens, amount and slippage to the FlowRouter API on our server. When your wallet is connected, it also sends your wallet address, so the swap can be built for it.

Our server then asks 0x, KyberSwap, Velora, Uniswap and LI.FI for quotes and ready-to-sign swaps, and FlowRouter's own router can ask RFQ market makers (Bebop, Native and Swaap) for firm quotes. When your wallet is connected, these requests include your wallet address, so each one can price and build the swap for your wallet: for example, 0x receives it as the "taker", and KyberSwap as the "sender" and "recipient". When no wallet is connected, a fixed placeholder address is sent instead of yours. Our server logs the requests it handles.

Wallet connection is provided by Privy, which may store its own data in your browser when you connect. Swaps you sign are public on the Robinhood Chain blockchain.

Bridge (Rift, LI.FI Intents, Relay, Across, Layerswap and deBridge)

When you use Bridge, the site sends the two assets, the amount, your destination address and your refund address to the FlowRouter API on our server. Our server passes them to Rift (rift.trade), which prices the route, creates the order and its deposit address, and screens both addresses against sanctions lists.

To price the other routes, our server sends the two assets and the amount to LI.FI (li.fi), Relay (relay.link), Across (across.to), Layerswap (layerswap.io) and deBridge (debridge.com). A Robinhood Chain token is named by its contract address. These price requests carry a fixed placeholder address, or no address, not yours. When you bridge with Relay, Across or LI.FI Intents, into or out of Robinhood Chain, or with deBridge out of Robinhood Chain, our server also sends your wallet address and destination address to that source, which builds the transfer your wallet signs. To follow a deBridge transfer, our server reads its order at deBridge by the order's ID. When you bridge into Robinhood Chain, your wallet reads your token allowance and estimates the network fee on the chain the money starts from, through its own network connection. When you bridge with Layerswap, our server creates the order at Layerswap with your destination address and your refund address (your wallet address, or the Bitcoin address you enter). Your browser never contacts these sources.

Your browser keeps the open order (its ID, the deposit address, the amounts and your two addresses), or the transfer you sent (its transaction, the amounts and your destination address), in local storage, so a reload does not lose it. It is removed when you start a new bridge. Deposits and deliveries are public on their blockchains.

Hosting logs

The site is served by nginx on our server, behind Cloudflare. Like most websites, they keep request logs: the time, the address requested, the response, and browser details. Cloudflare processes your IP address to deliver and protect the site.

How long we keep data: Google Analytics data for 14 months, and our server logs for 30 days.

Contact

Questions about this page: [email protected].