Privacy

1. What we collect

Using the site or the API, we record:

• Lookups. The subject you search (IP, prefix or ASN), when you searched it, and what we answered.
• Visitor data. Your IP address reaches our server with every request, as it must for any website. We use it to answer you and to build the salted hash described above, and then discard it. We do not store your address, browser, device, referrer or location. The analytics providers in section 5 collect their own data under their own policies.
• API usage. Endpoints called, request volumes, and your key once keys exist.
• Cookies and identifiers. Set by us and by the analytics tools below.

2. What we build from it

This is the part most privacy policies bury, so here it is plainly: query logs are an input to the product.

• What gets searched tells us which address space to fetch, sample and re-check. Your lookup can trigger our own checks on that subject.
• Our algorithms run over the log, including how often a block is looked up, from where and in what bursts, to prioritise archiving and to propose labels.
• The result is a dataset about networks: records, routing history, sampling verdicts and derived signals. It may include aggregate query interest, meaning "often looked up", and never who looked it up.
• We also use logs for the boring, necessary things: serving cached reports, rate limiting, and abuse prevention.

3. Analytics and third parties

We use third-party analytics, currently Google Analytics and possibly similar tools later, to understand how the site is used. They set cookies and receive your IP address and usage data under their own privacy policies.

Separately: when your lookup is not in our cache, the subject of the lookup, meaning the IP, prefix or ASN and never your identity, is forwarded to upstream data sources such as RDAP registries, RIPEstat, Team Cymru, PeeringDB, ipapi and Scamalytics so we can fetch fresh records.

4. How long we keep things

Indefinitely, by default. The service exists to remember what others overwrite, so cached records, observed changes and query-derived signals are part of the permanent archive. The lookup log is part of that: the query, the time and the salted hash. Because the salt is discarded on every restart, the oldest entries cannot be linked to the newest even by us.

5. What we share

• We do not sell or rent your personal data: your IP, your identity, or your individual search history.
• The network dataset we build, including signals derived in aggregate from queries, is the product, and may be published, licensed or sold.
• We disclose data if the law genuinely requires it.

6. Your choices

• Block or clear cookies; the site works without them. Analytics respects standard opt-outs.
• Use the API directly, which means no browser, no analytics scripts and no cookies. Lookup logging still applies.
• Email us with any question about this policy. We cannot look up what you personally have searched, because nothing in the log identifies you: the salted hash is one-way and its salt is already gone.

7. Changes and contact

If this policy changes in a way that matters, the date at the top changes and we will say so on the site. Questions and requests: [email protected]