Privacy
What this website and the Beam RPC endpoint collect, stated plainly.
This website
- No cookies are set.
- No analytics or tracking scripts are loaded.
- No requests are made to third parties. Fonts are self-hosted with the site. The only network call the pages make is to https://rpc.beamrpc.com/status, operated by us, to show live block height and health. It is covered by the endpoint rules below.
The RPC endpoint
Requests to https://rpc.beamrpc.com are not logged. Specifically, the endpoint does not log or store:
- IP addresses,
- user agents,
- request bodies (the JSON-RPC calls you make, including addresses you query).
Rate limiting uses the client IP address, held in memory only for the duration of the rate window. It is not written to disk and is not kept once the window has passed.
What is kept
Only aggregates that cannot identify a client:
- Request counts per JSON-RPC method.
- Request counts per hour.
- Request counts per referring dApp origin, from the Origin header that browsers send. This is the domain of the dApp that made the call, not anything about you.
- An estimate of unique clients per day, computed with a HyperLogLog sketch keyed by a hash of the client IP with a salt that changes daily. The sketch stores a handful of counters, not addresses; it cannot be reversed to recover an IP, and because the salt rotates, counts cannot be linked across days.
Transactions
Transactions submitted through eth_sendRawTransaction are forwarded to the network unchanged. The signed transaction bytes are retained for operational records. A signed transaction is public once it is mined, so this retains nothing the chain does not already show.
Contact
Questions about this page: [CONTACT EMAIL].
Last reviewed September 2026.