What we know about you — and what we cannot know

No accounts, no identity

Payment is the authentication. Aggregate reads are free; a question about a named wallet is paid per request over x402. There is no signup step, no token, no cookie and no session on the API — you are never identified, never profiled, and never asked to prove who you are. Only that you paid.

This is deliberate, not incidental: a service that knows who is asking can be pressured about who asked. Because no client identity exists, there is no visitor database to sell, leak, or be compelled to hand over — we cannot sell what we never collect. The full payment flow is documented at auth.md.

What the website itself uses

The only tracking on this static site is Google Analytics (tag G-4HWJ0FX20X, visible in the source of every page), used for standard visit measurement. It is loaded from Google and governed by Google's own policies; the API at api.describe.net carries no analytics tag at all.

Your browser's localStorage holds exactly three keys, all of them local preferences that never leave your machine: dn.lang (language), dn.mode (light or dark), and dn.theme (the site's fixed skin). The site writes them and reads them back; it sends them nowhere.

What a payment reveals

Paid calls are settled in USDC on public blockchains. That means the payment you make is a public on-chain transaction — public by the nature of the chain you chose to pay on, not by any decision of ours, and permanent in the way blockchains are. The receipt you get back is the settlement transaction hash: a public identifier, not a secret.

You never send us a private key. You sign an authorization locally and transmit only the signature; settlement gas is paid by the facilitator. If the wallet you pay from is linked to you elsewhere, that linkage exists on the public chain — choose your paying wallet accordingly.

Where the index data comes from

Everything in the index is a public blockchain event: ERC-8004 identity registrations and reputation ratings, written on-chain by the wallets that signed them. describe creates no data about anyone — it reads public logs and applies a published, versioned policy. Delete requests cannot apply to a blockchain we do not control; what we serve is a reading of records that are already public.

For human subjects the protections are stronger than for the rest of the index: there is no listing, no ranking and no index over display names — lookup is by wallet address only — and the human layer of this product is deliberately not launched until its documented preconditions are met.

Verify this page

Do not take a privacy page's word for it. The no-accounts model is observable: any paid route answers 402 to your first unauthenticated call, with no login to find anywhere — curl -i https://api.describe.net/pricing is free and shows the model. The three localStorage keys are in this site's own app.js, and the analytics tag is in the source of the page you are reading right now.