Privacy

EvalGlass is local-first. The tool and its Claude Code / Codex plugin run on your own machine and in your CI, collect no personal data, require no account, and send no telemetry — everything they touch stays in your repository. This page states exactly what that means, and then covers the one thing that isn't local: privacy-friendly, cookieless analytics on evalglass.com, which loads only if you allow it.

A "no false confidence" project should be able to state its data practices plainly and have them be verifiable. The tool is open source, so every claim about it here is auditable in the code.

The EvalGlass tool & plugin

EvalGlass Core is the software you install and run — through your existing coding agent (Claude Code or Codex) or directly on the CLI. Its data practices are short because it is local-first by construction:

No data collection, no accounts. There is no sign-up, no login, and no API key you buy from us. Installing or running EvalGlass creates no account and sends us nothing — we do not know that you use it.
No telemetry — nothing phones home. EvalGlass has no hosted service to call. It records no usage, emits no analytics, and transmits no crash or event data. Core sends nothing home.
Your data stays in your repo. Datasets, traces, prompts, evalglass.yaml, authority files, calibration, scorecards and run records all live in your filesystem (your repo and the vendored runtime under evals/_evalglass/). EvalGlass reads and writes them locally and never uploads them.
Driven by your own agent and keys. EvalGlass is operated by the coding agent you already run; that agent's handling of your code is governed by its own provider (for example Anthropic for Claude Code), exactly as for any other task. On its required path EvalGlass makes no model calls at all — judging uses a deterministic local model, with no network and no keys.
Optional lanes are opt-in and go where you point them. If you turn on an optional lane — a live model judge, or a trace/export connector (OpenTelemetry, Langfuse, Phoenix, …) — those calls go to the provider or destination you configure, under your credentials and their privacy terms. Nothing is enabled by default, and none of it reports back to EvalGlass.
Open source and deletion-proof. It is Apache-2.0 — you can read exactly what it does. The runtime is vendored into your repo and keeps working with the plugin removed, so it never depends on us to run.

More detail: Local-first · Security · Threat model · Honesty charter.

Commercial products (Discovery & Intelligence)

Discovery and Intelligence are separate, opt-in commercial products, contacted by email — there is no form and no CRM. Information you send in an enquiry is used only to respond to it and manage that commercial conversation, nothing more. Core's local-first, no-telemetry guarantee above is unchanged, and no customer artifact is used to train a shared model without your explicit agreement.

This website

Everything below is about visiting evalglass.com — never about how you run the tool. A website metric and runtime data collection are different things, and we never conflate them.

Static hosting. The site is static HTML served by Vercel; standard server access logs may record requests (IP, user-agent, URL) for operations and security, as with any web host.
Outbound links. Pages link to GitHub and other sites, which have their own privacy practices.
Fonts. Typefaces load from Google Fonts; that request is governed by Google's terms.

Website analytics

The only measurement on this site — and the last thing on this page, deliberately:

Consent first. Nothing is measured until you choose Allow on the banner. Choose No thanks — or send a Do Not Track signal — and no analytics loads at all.
Cookieless and aggregate. We use Vercel Web Analytics, which sets no cookies and builds no per-person profile. It reports aggregate counts (page views, referrers) with no cross-site or cross-day identifier.
What we store on your device. Only your choice — a single functional flag in your browser's localStorage (eg-analytics-consent). It is not a tracking identifier and is never sent anywhere.
No advertising or social pixels. No Meta, Google Ads, LinkedIn, or X pixels — none, ever.
Why. To learn which pages actually help readers and agents — not to chase raw traffic. We will never publish adoption numbers the project hasn't earned.

Changes & contact

If we change what we collect, we will update this page in the same change and say exactly what is collected. We will keep any website analytics first-party and cookieless, we will not add advertising pixels, and we will not publish adoption numbers the project hasn't earned. Privacy questions: contact us or email contact@evalglass.com.