Privacy Policy

Information processed when you visit

Cloudflare hosts and protects the site. Delivering and securing a request involves processing its URL, IP and network information, browser/request headers, and connection/security information. This can include approximate geographic information derived from network information, such as country, city or region. We do not request device GPS location.

Cloudflare can also inject browser security checks that evaluate browser characteristics and activity to distinguish automation. Cloudflare’s separate security analytics can retain sampled request records, including IP addresses, request paths and browser/device categories. This is separate from information we save in application diagnostics.

Benchmark Registry diagnostics

We use aggregate request counts, failures, response status, cache activity and performance metrics for reliability, debugging and security. Persisted per-request Worker logs, automatic invocation records and traces are disabled. We do not export application logs to another destination.

Application errors emit only a fixed failure category and build version. During exceptional debugging, authorized operators can view temporary live diagnostics; Cloudflare may include request and network context in that live view. We do not save those live sessions as application logs.

Storage in your browser

Your Light, Dark or System theme choice is saved locally until you change it or clear browser storage. Public Registry pages and data are cached for speed. Navigation and search results can remain in page-session memory, are refreshed or invalidated as data changes, and disappear when the page session ends.

Searches and filters are sent in the request URL to show matching public data. Your browser may keep visited URLs in its history and responses in its ordinary HTTP cache. We do not keep a persistent application search history or use these caches to build a visitor profile.

Cookies and advertising

The Registry application does not set cookies. Cloudflare’s browser security checks may use session storage and technical security cookies when needed to protect or deliver the service. We do not add advertising, behavioral analytics or session replay scripts. We do not use visitor information for advertising or behavioral profiling, and we do not sell it.

Support email

Viewing the site does not send us your email address. If you choose to email support, we receive your address, message, and any name, signature or attachments you include. We use that information to respond and handle follow-up. We do not currently specify a fixed automatic deletion period for support correspondence; contact us about a message you have sent.

Public data and external links

The public Registry stores information about companies, models, benchmarks, evaluation results and sources. This public reference data is separate from visitor information.

Following a source, GitHub, Densa Labs or other external link takes you to another service with its own privacy practices.

Retention

New per-request Worker logs and traces are not persisted. Logs saved before the September 28, 2026 hardening may contain IP addresses, network-derived location, browser/connection information and full request URLs, including queries. Those earlier logs expire automatically within Cloudflare’s three-day Workers Free retention period; disabling new persistence does not erase them immediately.

Aggregate Worker metrics are available for up to three months and zone analytics for the last 30 days. A previously enabled Cloudflare Web Analytics beacon collected page-view and web-performance statistics; it was disabled on September 28, 2026. Earlier Web Analytics data is unsampled for seven days, then available in sampled aggregates for up to six months. These are separate from application request logs. Our application logging settings do not control Cloudflare’s separate security processing. On our current Free zone plan, Security Events are available for 24 hours and Security Analytics for seven days. Cloudflare security session storage lasts for the browser tab session; security cookies have their own lifetimes. Local theme storage remains until changed or cleared; page-session caches end with the session, and your browser controls its history and HTTP-cache retention.

Changes

We may update this policy when the service or its data handling changes. The date above identifies this version.

Contact

For questions or corrections, email support@benchmarkregistry.org.