privacy

Privacy

Two different things are covered here and they are worth keeping apart: this documentation site, which you are reading now, and the component library, which runs inside applications other people build. Neither has user accounts, and neither asks for personal information.

This documentation site

The site is a static build hosted on Vercel. Vercel processes standard request data — IP address, user agent, requested URL — to serve and protect the site; that processing is Vercel's, under their privacy policy, and is not exposed to the maintainer beyond aggregate traffic counts.

The site uses Umami, a cookieless privacy-focused analytics service, to count page views. Umami sets no cookies, assigns no cross-site identifier, and does not fingerprint visitors. Blocking the script has no effect on the site's functionality.

Your theme preference (light or dark) is stored in your browser's localStorage. It never leaves your device and is not readable by anyone else.

  • No accounts, no sign-in, no newsletter, no contact form
  • No advertising, no cross-site tracking, no data brokers
  • No cookies set by this site
  • No wallet connection is ever requested — the site and library are read-only

The component library

The components contain no analytics, no telemetry and no error reporting. They make exactly one kind of outbound request: a GraphQL query to The Graph's gateway for the chain being displayed, authenticated with the read-only API key the consuming application configures. AgentImage additionally loads whatever image URL an agent registered, which may be an IPFS gateway or an arbitrary HTTPS host chosen by that agent.

That means when you ship these components, your users' browsers talk to The Graph's gateway and, if you render agent images, to third-party image hosts. Those parties see your users' IP addresses and their own request data under their own policies. If that matters for your application, proxy the requests server-side or use the FingerprintBadge fallback instead of remote images.

On-chain data is public and permanent

Everything these components display — agent names, descriptions, endpoints, owner addresses, feedback values, review text, validator responses — was published to a public blockchain by someone else and indexed by The Graph. It is world-readable by design, it predates this library, and it cannot be deleted, corrected or hidden by the maintainer of this project. Revoked feedback is filtered out of the components' queries, but revocation is itself an on-chain event: the original entry remains in the chain's history.

Requests to remove on-chain content have to go to whoever published it, not here. This project only reads what the registries already contain.

Changes and questions

This page describes current behaviour rather than a legal commitment, and it changes when the site changes; the repository's history is the authoritative record of when and why. Questions about anything on this page belong in a GitHub issue, where the answer stays public and useful to the next person who asks.

This page as markdown: /privacy.mdAgent index: /llms.txt