Privacy

There is no account, there is no cookie, and there is no access log. The only thing that leaves your browser is the search term you type. This page states exactly what is recorded, why, and how to have it removed.

1. What we do not collect

Each line below is a property of the running service, not a promise about intentions:

• No account and no login. There is no registration, so there is no user record to hold.
• No cookies. The search pages set none.
• No access log. The search service does not write per-request logs; it does not record the visitor's IP address, user-agent string, or request headers.
• No third-party requests. The search pages load only resources served from this site. There is no analytics script, no advertising tag, no external font, and no embedded third-party widget — so no third party receives your visit.
• No personalisation. Results do not depend on who you are. There is no profile, and no behaviour is attributed to a returning visitor — see How results are ordered, the section “Is the order the same for everyone?”.

2. What is recorded, and why

When a search is run from this site, one record is added to an internal, server-side log keyed by the query — not by the person who ran it. It contains:

• the search term, both as last typed and in a normalised form used as the aggregation key;
• how many times that term has been searched, and when it was first and last seen;
• how many results it returned, how often it returned none, and how often the result limit was reached;
• a label for the kind of caller (the public site, or our own benchmark), which is what keeps our test queries out of the human signal.

Why: a search that returns nothing is a fact about our index that we should not forget. These records are how the operator decides which terms and which sites to add to the index. They are internal: they are not published, not shown on any public page, and not sold or shared.

What it cannot do: because no identifier is stored, this log cannot be used to reconstruct what any individual searched. Two different visitors who search the same term produce one record, not two.

3. Retention, location, and removal

• Where. In the data directory of the server running this deployment. It is not transferred to any third party, and there is no cross-border transfer of it.
• How long. For as long as the service runs. The record of a completed search is aggregated rather than event-logged, which is why it is kept rather than rotated away — the longer a gap goes unfilled, the more useful it is.
• Removal. A query record is deleted on request — write to [email protected] and name the search term. Note what this costs us in return for collecting no identity: we cannot locate “your” records, because we never had a way to tell which ones were yours. Naming the term is the only way a deletion can be carried out.

A search term can incidentally contain personal information, if that is what the visitor typed. That is the reason the removal route above exists, and the reason the log is keyed by term rather than by visitor: the remedy follows the term.

4. What stays in your own browser

Two interface preferences are kept in your browser's localStorage: the interface language, and the light/dark appearance setting. They are read and written by this site only, they are never sent to the server, and clearing site data removes them.

Separately, if this site is opened with an operator access token in the URL, that token is kept in the same browser storage so it does not have to be re-entered. It is a credential for the operator surface, not a visitor account; the URL is rewritten immediately so the token does not remain in it or in history.

5. When you follow a link off this site

Listing links open in a new window and carry rel="noreferrer", so the browser sends the destination site no referrer and no search term from us. Once you arrive there, that site's own privacy practices apply — including any logging or tracking it does. We are not a party to that and have no control over it. See also Terms of use, the section “Third-party sites are not ours”.

6. Lookups we make on our own behalf

Building the index means our own servers, without any visitor involved, fetch publicly reachable pages and query domain-registration sources (RDAP/WHOIS). Those requests come from the index, not from you, and contain nothing about any visitor.

7. Minors

This service is not directed at children, and there is no account or profile for any age group. Because no personal information is collected, none is collected from minors.

8. Changes and contact

If what is recorded changes, this page is changed with it, and the effective date below is updated. Questions, and every request under this page, go to [email protected].

The description above is written against the running implementation, and the three claims that carry the most weight are properties that can be re-checked directly: the search pages set no cookies, they load no third-party resources, and the search service writes no per-request log. This page is published in English only, so that exactly one version of the text is in force. Effective date: 2026-10-12.