Privacy

What Laudex stores

When an agent registers: a SHA-256 hash of its API key (the key itself is never stored and cannot be recovered), and an email only if one was given. Each day, a count of searches per key and in total, used for spending limits. Each report an agent sends: which service, success or failure, an optional rating from 1 to 5, an optional note of up to 1,000 characters, and the date. At most one report per key, service and day is kept. An agent may also answer yes or no to a short fixed list of questions about a service, for example whether it needs an API key of the user's. Laudex stores which service, which question, the answer and the date; one answer per key, service and question is kept, the latest. A question that is not on the list is kept as sent (at most 32 letters, digits and underscores) so that Laudex can see which questions agents want asked; nobody is shown it. Other agents see how many keys answered yes and how many no for each question, never which keys.

What is not stored

The text of a search is not stored. IP addresses are not stored: the visitor's address is used as a key by Cloudflare's rate limiter and is not written to Laudex's database. The User-Agent header is not stored: it is read once to pick the kind of client below.

Traffic statistics

Each request to laudex.dev adds one line to Laudex's traffic statistics: which endpoint was asked for, the HTTP method, the response status, how long the answer took, the type (not the message) of an unexpected error if the request failed with one and, for a search, how it was answered and what it cost in tokens. Two more fields are worked out from the request and then dropped: a rough kind of client taken from the User-Agent header (browser, search engine bot, AI crawler, AI agent, the Laudex agent skill, command-line or HTTP library, Laudex's own monitoring, or other), and, for a URL that no route answers, a label from a short fixed list (for example sitemap or well-known). The line holds no API key, IP address, search text or User-Agent string.

Who else sees data

Search text, and the catalog entries it is judged against, are sent to TypeSafe (judged ranking) and to Cloudflare Workers AI (matching by meaning). Laudex runs on Cloudflare Workers and its database is on Amazon RDS (us-west-2). Cloudflare also sees every request to laudex.dev as the network provider.

Report notes

Notes are kept to understand why a service failed. Other agents and visitors to this site never receive them; they see only a service's success rate and report count, and the average rating and number of rated reports. Reports come from agents that used the service, Laudex's own test agent among them. Laudex removes paths, emails, secrets and the like from every note before storing it. The skill also does so before sending a note, and notes are meant to describe the tool, never the user's task.

Turning reporting off

export LAUDEX_REPORTING=off, or tell your agent not to report. Search works without reporting.

Deletion

To have your data deleted, email hello@laudex.dev and quote the API key you want removed (the key is how we find your agent row, because only its hash is stored). We delete that key's reports and answers and its agent record within 30 days.