Privacy Policy
NessGate is designed to know as little as possible.
What we store
Nothing about you, and nothing about the domains you look up. NessGate keeps no domain data at all — no mappings, no copies of resources, no index. The only thing we store is short-lived, IP-based rate-limit counters (see Technical data), which exist purely to keep the free service available and expire on their own.
We also record anonymous, categorical events about the service's own operation: for each discovery call, a single label — resources returned, none returned, invalid input, or error — with a timestamp. These events carry no domains, request contents, IP addresses, or identities, cannot be linked to any person, session, or query, and are stored as individual events that we aggregate only when we query them. They are sampled and retained for about three months, and exist solely to measure whether NessGate returns results.
When the GET /discover/{domain} endpoint is queried, NessGate fetches a
fixed set of standard public locations on the queried domain (such as /llms.txt
and /.well-known/ files), reads and normalizes the responses, returns them with
a link back to each source, and discards everything fetched. Nothing is stored, indexed, or
crawled in the background — a lookup happens live, only when someone asks.
What we don't collect
NessGate has no user accounts and asks for no names, email addresses, or personal information. The site sets no cookies and uses no visitor analytics or tracking scripts. We do not read or record client IP addresses for measurement. The only measurement we perform is the anonymous categorical event described above, which never identifies you.
Technical data
Our infrastructure runs on Cloudflare. Like virtually all web services, requests pass through standard server infrastructure that processes IP addresses to deliver responses, prevent abuse, and enforce rate limits. The data we retain is limited to short-lived, IP-keyed rate-limit counters kept in Cloudflare KV (which expire automatically within about an hour) and anonymous categorical operational events kept in Cloudflare Analytics Engine — a single outcome label with a timestamp, and no domains, request bodies, IP addresses, or identities. Analytics Engine stores these events, aggregates them when queried, may sample them, and retains them for about three months. We do not build profiles of visitors. Cloudflare processes traffic under its own privacy policy.
Changes and contact
If this policy changes, the new version will be published on this page with an updated effective date. Questions: see Contact.