randbridge.org has no accounts, no sign-up, no analytics, no advertising and no cookies of its own beyond one that remembers the language you chose. It never sees your wallet keys and never holds your funds: your wallet signs every transaction. A bridge transfer is public by nature, and this page says exactly what it reveals.
What stays in your browser
- Your theme choice (light, dark or system), and the language you picked from the menu, which is also sent back to our server as a cookie so the site opens in that language next time.
- The transfers this browser started, up to 50: each one's id, network, token, amount and time, and the Rand address it was sent to when you pasted one. This is what the History page shows for deposits made with a pasted address.
Both are kept in your browser's local storage and are never sent anywhere. Clearing this site's data in your browser removes them.
What our servers receive and keep
- Your Rand address, when you deposit. Before a deposit, the site sends the Rand address you connected or pasted to the bridge relayer, which needs the full address to deliver the deposit to it. The relayer keeps the address for as long as it may have to deliver to it. Our status service keeps only the address's recipient hash, the value your deposit carries on the source chain.
- Transfer records. The status service indexes the bridge's public events from Ethereum, BNB Chain, Tron, Solana and Rand (amounts, source addresses, recipient hashes, transaction ids, times) so the site can show a transfer's progress. All of it is already public on those chains.
- History lookups. When the History page looks up transfers for a connected wallet, the wallet's public address is sent to the status service to find them. It is not stored beyond the server logs below.
- Server logs. Our web server logs each request: IP address, time, the address requested (which for a history lookup includes the wallet address) and the browser's user agent. Logs are kept for about 14 days to run and protect the service, then deleted. Requests are also counted per IP address, in memory only, to stop one client flooding the bridge.
- Your country, for the language. Cloudflare tells our server which country a request comes from, and the first page you open is served in that country's language if the site has it. The country is not stored.
- Cloudflare. The site is served through Cloudflare, which handles every request (including your IP address) to deliver and protect the site, and may set its own security cookies. Its handling is governed by Cloudflare's privacy policy.
Services your browser talks to directly
Using the bridge connects your browser to services we do not run. Each has its own privacy policy.
- Your wallet (MetaMask, Trust Wallet, Phantom, TronLink, Rand Wallet), which shares an account with the site only after you approve it. Reads on Ethereum and BNB Chain go through your wallet's own connection.
- Public blockchain nodes the site reads from and sends your signed transactions to: a public Solana node for Solana deposits, and TronGrid for Tron when your wallet does not provide a connection of its own (MetaMask, a phone over WalletConnect).
- WalletConnect (Reown), only if you choose to connect a phone wallet that way.
- Block explorers (Etherscan, BscScan, Tronscan, Solscan, RandScan), only when you open one of their links.
What a bridge transfer makes public
- A deposit is recorded on the source chain with your wallet address, the amount, the time and the recipient hash. On Rand, the transaction that mints your zUSD carries the full Rand address it was sent to, so a deposit publicly links your source-chain address to that Rand address. What you do with the zUSD afterwards is shielded on Rand.
- A withdrawal is recorded on Rand as a burn, and the release on the destination chain shows the address you withdrew to and the amount.
None of this can be removed: it is part of public blockchains, not of a database we control.
What we do not do
We do not sell, rent or share personal data, we do not track you across sites or apps, and we run no analytics or advertising code. The bridge's contracts and daemons are published at github.com/randprotocol/bridge.
Children
The site is not directed at children.
Changes
If this policy changes, the new text is published on this page with a new effective date.
Contact
Questions about this policy: open an issue at github.com/randprotocol/bridge/issues. See also the terms of service.