Privacy

This site sets no cookies, runs no analytics and has no accounts. Nothing you do here is sent anywhere else.

Does this site have a page about yours? Everything that matters to you is inwhat is held about your site: where it came from, and the two ways to remove it.

If you are just reading

Cookies: None. Not even the sort that call themselves essential. There is no consent banner because there is nothing to consent to.
Analytics: None. No Google Analytics, no pixels, no session recording, no fingerprinting, no advertising, and nothing that follows you to another site.
Accounts: There are none. Nothing to sign up for, so there is no password or address here to leak.
Third-party requests: None. Every font, style and script comes from this domain. Web fonts are deliberately self-hosted rather than loaded from Google, because that would hand your IP address to Google on every page you open.
Stored in your browser: One thing: choosing light or dark saves that preference under wt-theme in your own browser. It never reaches the server, is never read by anyone, and clearing your site data removes it.
Server logs: Requests are logged the way any web server logs them: IP address, the page, the time, and the user-agent your browser sends. They are used to keep the service running and to look into abuse, and for nothing else. They are deleted after 14 days.
Cloudflare: The site is served through Cloudflare, so its network carries your connection and keeps its own short-lived logs for security and performance. It is the only other company involved in your visit to this site.

What is held about your site

Most of what this site publishes is about other people's websites, so this is the part worth reading carefully. Everything below is drawn from sources that are already public: what your own site serves, what your registry publishes, and public certificate and DNS records. Nothing is bought, and nothing comes from a private source.

What is held	Where it comes from
The domain name	Public Certificate Transparency logs, which every TLS certificate is written to, and the Tranco research list
Title, description, language, page structure	One visit to your homepage, exactly as a browser would make it
Platforms and frameworks detected	The same visit: what your HTML, headers and cookies announce about themselves
Hosting provider, country, approximate city	The IP address your domain resolves to, looked up in DB-IP's city database. This locates a datacenter, not a person
Registration date and registrar	Your registry's own public RDAP record
Mail host, DNS provider, DMARC policy, IPv6	Your domain's public DNS records
robots.txt rules and llms.txt	Files you publish specifically for crawlers to read
One homepage screenshot	A headless browser, one visit, no interaction, stored at 640 pixels wide
First archived capture	The Internet Archive's public index

What is never collected or published

Registrant names, addresses, phone numbers or email addresses. These are not collected at all, even from registries that still publish them. The registrar is recorded as a company; the person behind the domain is not.
Security findings. The crawler records some security signals to spot broken configurations and to keep its own detection honest. None of it is shown publicly, ranked, graded in public, or sold.
Anything private. Only your homepage is fetched, and only if robots.txt allows it. Nothing behind a login or a paywall is touched, no port is scanned, no path is guessed, and your page's HTML is not kept once the facts above have been extracted from it.

How to have your site removed

Two ways. Both are honoured, and neither asks you to justify yourself.

Tell the crawler to go away. Add this to your robots.txt. Crawling stops within one cycle, and the screenshot is deleted on the next pass.
```
User-agent: WebtelemetryBot
Disallow: /
```
Ask. Email support@webtelemetry.dev with the domain. It is removed from the public site and added to a permanent exclusion list, so it is never added back by a later crawl. No account, no form, no explanation needed.

The same address works for corrections. Detection is automatic and therefore sometimes wrong; if this site says something untrue about yours, say so and it will be fixed.

How the data can be used by others

Profiles are public pages, and there is a free public API and anRSS feed carrying the same information. Anyone can read them, so assume that anything visible on your profile can be copied elsewhere. That is the nature of a public census, and it is the reason the removal routes above exist and are honoured quickly.

Where the underlying data comes from

Certificate Transparency logs, for discovering domains as certificates are issued
Tranco, a research ranking of popular domains
Registry RDAP records, for registration dates and registrars
DB-IP Lite, for mapping IP addresses to a network and a city
Public DNS, for mail and nameserver records
The Internet Archive, for a domain's earliest capture

The methodology page describes every step in detail, including where the numbers are incomplete or skewed. The crawler page covers how WebtelemetryBot behaves.

If you are in the EU or UK

Most of what is held here is not personal data. It is facts about websites, companies and software. Where a site is run by an individual, some of it may be, and in that case the basis for holding it is legitimate interest in documenting the public web. That interest gives way to yours as soon as you ask: the two routes above are how to exercise it, and no one is asked to prove ownership or give a reason first.

Requests for access, correction, objection or erasure go to the same address and are handled by the same person who runs the crawler.

Contact

support@webtelemetry.dev, for removals, corrections, and anything on this page.

Last updated 26 September 2026. This page is changed when the site changes, not on a schedule. Sites registered in the last 30 days are the ones the feeds are built from; that makes no difference to anything above, which applies to every site in the census.