Privacy
No accounts, no cookies
The explorer has no sign-up, no login and sets no cookies of its own. Pages and the JSON API work identically for every visitor. Nothing you type into the search field or the API console is stored by this site; queries are forwarded to the indexer or the RPC node to answer the request and then discarded.
What is measured
The site loads Vercel Analytics and Vercel Speed Insights, which record anonymised page views and Core Web Vitals (load and interaction timings) per page. They do not use cookies and do not build a cross-site profile. The hosting provider keeps ordinary request logs (IP address, path, user agent, timing) for operational purposes and security, under its own retention policy.
GET /api/overview is rate limited per IP address using a sliding window of ten seconds. The counter lives in a managed Redis store and expires with the window; it is not joined to any other data.
What is forwarded
Every chain read goes through this site's server-side API, so the RPC node and the indexer see the request content (the method and its parameters, or the path) but not your IP address. The API console (/api) forwards only JSON-RPC methods on its published allowlist and only to the two ETO testnet endpoints; it will not relay to a host of the caller's choosing.
The Studio page (/studio) sends your chat messages, and the output of the tools the agent runs, to a large language model through the Vercel AI Gateway, and runs generated code in an isolated sandbox that is torn down when the session ends. Do not paste secrets into the Studio; treat it as a public testnet tool.
Your rights and changes
Because the site keeps no personal records of its own, there is nothing to export or delete here; requests about hosting-provider logs can be raised through the contact page. This page is updated whenever a new data flow is added. The source that implements each flow above is public, so the description can be checked against the code.