Beilpre-launchOpen app
API

Our own APIs.
Measured, not promised.

The Beil site and app talk to a short, fixed list of services: the site itself, the Beil relayer, the Beil indexer and one BNB Chain RPC endpoint. Here is each one, what it can and can't see, and a live test you can run right now.

3 Beil services + 1 RPCNo third-party scriptsNo analytics, cookies or trackersNo IP addresses stored
Your deviceKeys · proofs · balancemade and kept here
Beil's services
  • site
  • relayer
  • indexer
  • rpc
Outside
  • PancakeSwap
  • Venus
  • token data
reached by the relayer, not your browser
Watch it happen

A live network check, in your browser.

This pings each service the deployment is configured with, then lists every origin this page has actually contacted and whether any cookie was set.

beil · network checkready

Press run to measure from this device.

Every number is measured right now, on your device.

Check it without us: open your browser's developer tools on any Beil page and watch the Network tab. Every request goes to one of the services listed below.

Every API your device uses

What each one sees.

None of Beil's services keeps access logs. Your IP address reaches them, as with any website, and is only held in memory to limit how many requests one client can make. It is never stored.

The site & appthis origin

Serves the pages, their code and the proving files. Static files, the same for everyone.

Receives
Requests for those files.
Never sees
Anything you type or hold. The app runs on your device, and your keys never leave it.
Relayernot configured

Submits your private transactions and pays their gas. Quotes fees, swaps and Venus positions.

Receives
Each transaction with its proof, and quote requests: tokens, amounts, and a withdrawal's destination.
Never sees
Your keys or your balance. It can't change where funds go: your proof fixes the recipient and the fee.
Indexernot configured

Serves public pool data, the same for everyone: encrypted notes, nullifiers, the Merkle root, token metadata.

Receives
Requests for that public data.
Never sees
Which notes are yours. Your device finds them by decrypting, and checks the root against the pool contract.
BNB Chain RPCbsc-dataseed.bnbchain.org

Reads the chain for the app and these pages: balances, fees, pause flags, transaction status.

Receives
Read requests, such as a contract view or a balance lookup, and your IP address.
Never sees
Your Beil keys or which notes are yours. Point the app at your own node if you'd rather it saw nothing.

Endpoint reference for the relayer and indexer: Docs → Relayer & indexer API. Anyone can run their own.

Nothing else

Nothing else runs in your browser.

No third-party code

Every script comes from this site. No analytics, ads, tag managers or chat widgets.

No outside fonts or images

Fonts are bundled with the site at build time. Token logos come through the indexer, so the hosts that serve them never see you.

No cookies, no accounts

Nothing to sign up for, and nothing that follows you from site to site.

Outside services

Where outside services come in.

ServiceWhat it's used forWhat it sees
BNB Chain RPC nodeReading the chain for your browser; the relayer uses its own node to send transactionsYour IP address and the read requests your browser makes. Use your own node to avoid that.
PancakeSwap, VenusSwaps and lending, executed on-chain by the pool through allowlisted adaptersThe pool as the trader. The trade itself is public on BNB Chain; who made it is not.
Your walletMetaMask, Trust Wallet, Binance Wallet or another wallet you connect for shields and to receive exitsIts own software with its own connections and policies.

Links you open, such as BscScan, take you to those sites. Anything you shield or withdraw is public on BNB Chain, like any transaction. More about what stays on your device: Privacy policy.