Short version: iseeu.cc shows you what your request reveals and then forgets it. We keep no request logs, no database of visitors and no cookies. We count how often each endpoint is used, without your IP address or any other detail about you, and we count page views with Cloudflare's cookieless analytics.
What we receive
Like every website, our server receives your request: your IP address, the request headers your browser or tool sends (such as User-Agent and Accept-Language), and connection details that our host, Cloudflare, attaches (approximate location and network of your IP address, TLS and HTTP version, round-trip time). We use these only to build the response you asked for.
What we keep
- No request logs. Cloudflare's per-request logs (which would contain your IP address and headers), tracing and log export are switched off for our Worker. For monitoring, the Worker writes one anonymous line per request — the endpoint, a broad client category and the response status — plus error messages. The lines we write never include your IP address, browser details or headers. Cloudflare keeps them for up to 7 days together with its own execution metadata, such as the time and the page path that was requested (with any query string removed).
- No database of visitors. There is nowhere to store your IP, headers or fingerprint, and we don't.
- No cookies, no ads, no cross-site tracking. We set no cookies, load no advertising code and use no third-party fonts.
- Cookieless page-view statistics. Our pages load Cloudflare Web Analytics, a privacy-first counter run by our host. It sets no cookies, uses no local storage and does not fingerprint you; it reports the page visited, the referring site, browser and device type, an approximate country and page-load timing, and we only ever see aggregate totals, not individual visits. It does not run on the API or MCP endpoints.
- Endpoint counters. For each request to our server we record one anonymous data point: which endpoint was used (for example
/jsonor/mcp) and a broad client category (for example "browser", "command-line tool" or "AI crawler"). No IP address, User-Agent string, headers or location are included. These counts are stored in Cloudflare Workers Analytics Engine and help us decide whether the site is worth running.
Checks that run in your browser
The fingerprint, time zone and WebRTC checks run in your browser. Their results are shown to you and never sent to us. To check whether local storage is available, the fingerprint test writes a test value and deletes it immediately.
The WebRTC test asks Cloudflare's public STUN server (stun.cloudflare.com) which IP address it sees, because that is exactly what a WebRTC leak is. That request goes from your browser to Cloudflare directly; we receive nothing from it.
Tools that contact another server
- DNS lookup. Your browser sends the question directly to the resolver you pick, Cloudflare (1.1.1.1) or Google Public DNS (8.8.8.8), over HTTPS. That resolver sees your IP address and the name you looked up, under its own privacy policy. The query does not pass through iseeu.cc.
- WHOIS / RDAP lookup. Our server sends your query to the registry that IANA lists for it. The registry sees the query and a Cloudflare network address, not yours. We keep no record of the query or its result.
- Security headers check. Our server requests the URL you enter and reads only the response headers. The website sees a request from Cloudflare's network, not from you. We keep no record of the URL or the result.
The email header analyzer, subnet calculator, MAC address lookup, Punycode converter and browser feature detection run entirely in your browser. The MAC lookup downloads a slice of the public IEEE registry from iseeu.cc; the address you type is never sent anywhere. If you use the theme switch in the page header, your choice is stored in your browser's local storage and never leaves your device.
Our host: Cloudflare
Every page reaches you through Cloudflare's network. To hand you a response and screen out attacks, Cloudflare necessarily handles your IP address and the request itself. Cloudflare may keep limited operational data under its own policy; see the Cloudflare privacy policy. We have not enabled any Cloudflare feature that would give us per-visitor logs.
The API and MCP server
The same rules apply to curl iseeu.cc, the JSON endpoints and the MCP server: the response is built in memory and discarded. Rate limiting counts requests per IP address for one minute inside Cloudflare's rate limiter; we cannot read or export those counters.
Your rights
Because we hold no personal data about you, there is nothing for us to access, correct, export or delete. If you believe we hold something we shouldn't, write to us and we will check.
Children
The site is a general-audience technical tool and does not knowingly collect information from anyone, including children under 13.
Changes
If we ever start keeping anything new, we will update this page before doing so and change the date at the top.
Contact
Privacy questions: hello@iseeu.cc.