Privacy policy
RouteLab is a static site with no accounts and no backend of its own. This page explains what that means in practice. Last updated October 30, 2026.
What we collect
RouteLab does not collect personal data. There are no accounts, forms, cookies set by the site, advertising or analytics scripts, and no database. We do not receive the RPC URLs you type or the results of your tests.
Where requests go
When you run a benchmark, your browser sends JSON-RPC requests directly to dRPC’s public endpoints and to any URLs you enter. Those services see your IP address and request details, as any website you call would, and handle them under their own policies. RouteLab’s own pages never see that traffic.
The looping video on the home page is loaded from a third-party content host, which sees your IP address when it is fetched.
The configuration generator never asks for an API key. The files it produces contain a YOUR_DRPC_KEY placeholder that you replace yourself. If you paste an RPC URL that contains a key into the benchmark, the key is used only for the requests you start. It is held in the page’s memory and cleared when you close or reload the tab.
Storage in your browser
The site writes one value to session storage, a flag that lets the opening animation skip itself on repeat visits during the same browser session. It contains no personal data and is removed when the session ends.
Hosting and fonts
The site is hosted on Vercel, which may log standard request data such as IP address and user agent for security and operations, under its own privacy policy. Fonts are served from this site, so your browser makes no request to a font provider.
Links to other sites
Pages link to dRPC, GitHub, viem and X. Those sites have their own privacy practices, which we do not control.
Changes and contact
If this changes, the date above changes. Questions can go to @Oh_Jay0 on X.