Privacy

Reading the site produces ordinary web analytics. The categories are:

• Your IP address, recorded by our analytics processor when a request arrives, and the approximate location it derives from that: country and city, nothing finer.
• Your browser and device: the user-agent string, screen size, and the page performance timings behind our Core Web Vitals.
• What you looked at: the pages you opened, the page you arrived from, and three deliberate actions, an outbound link click, a copy, and a site search.
• A random device identifier stored in your browser, so two pageviews can be recognised as one visit. It is tied to no identity, and we never call the function that would create a user profile.

Three machine-readable surfaces are counted on the server instead, because no browser renders them: the Markdown views, /api/stat and /api/citable. There the identifier is a daily hash of the requesting user agent, and no profile is created.

We never ask for and never want: your name, your email, a wallet address, a private key, a seed phrase or an API key. No feature of this site requires one.

Automatic event capture is off, so nothing is recorded except the events named above. Session recording is off: no replays, no heatmaps, no keystroke or form capture.

• To know which benchmarks are read, so we work on the ones people use.
• To measure whether pages load well, which is what the performance timings are for.
• To rate limit the public API per address, so one caller cannot deny the service to everyone else.

Not for advertising, not for profiling, and not for building a picture of you across other sites. There is no advertising on this site and no cross-site tracking identifier.

• PostHog, our analytics processor, hosted in the United States. Analytics are proxied through this site’s own origin, so your browser never contacts them directly.
• Vercel, which hosts and serves the site and necessarily handles requests to it.

Nobody else. We do not sell data, share it with advertisers or data brokers, or pass it to any third party beyond those two processors.

• Analytics events: one year, the retention configured on our analytics project, after which they are deleted by the processor.
• Rate-limit counters: minutes. They live in the memory of the serving process, are never written to disk, and are discarded whenever the site is redeployed.
• Benchmark measurements: indefinitely, because they describe infrastructure providers rather than visitors and contain no personal data.

• Analytics can be blocked in your browser, or by any content blocker, or by enabling Do Not Track. Nothing on the site stops working.
• Clearing your browser storage removes the random device identifier, and the next visit starts a new one.
• Because we hold no name, email or account, we cannot look up, export or delete “your” records on request: there is nothing tying them to you. If you believe we hold something about you, write to contact@openchainbench.com and we will look.

The Model Context Protocol endpoint at https://openchainbench.com/api/mcp/mcp is public, read-only and requires no authentication or account. It answers questions about published benchmark data and stores nothing about the conversation that reached it. A question containing something that looks like a credential is redacted before it appears anywhere in the response.

When you reach this data through an AI assistant, that assistant has its own privacy policy covering your conversation. We receive the question it chooses to send us and nothing else.

This is a technical reference for people choosing infrastructure providers. It is not directed at children, and we do not knowingly collect anything from them.

This page changes in public commits like the rest of the site, in the same change that alters what is collected. Questions and corrections to contact@openchainbench.com. See also the terms of use and the methodology.