What is stored, what is not
The short version: no analytics, no visitor tracking, no hidden database. Your record is a public file you can read, and this page is the full list of what the site keeps.
Public by design
A claim writes domains/<name>.json to a public GitHub repository: the name, your GitHub login, the claim timestamp, any DNS records you set, and an optional display profile. Git history keeps every past version. That publicity is the registry’s integrity model, not a side effect.
Sign-in and the session cookie
Signing in runs through GitHub OAuth. The site stores a single signed, HttpOnly cookie holding your login and a few public profile facts, expiring after 24 hours. There is no account record on this side: the cookie plus GitHub is the whole identity. Sign out (or wait a day) and nothing about you remains on the server.
The claim-time country field
When a name is claimed, the request’s edge-inferred country (an ISO code like IN) is written into the record, and nothing more precise. It feeds the aggregate claim map on the stats page. It is never a city, never an IP address, written exactly once at the moment of the claim, and never refreshed or enriched afterwards. To remove it entirely, release the name (it goes back to the pool) and claim again.
What is never collected
No analytics scripts. No visitor fingerprinting. No advertising cookies. No location lookups on page views. Browsing this site leaves nothing behind but your own browser cache.
One exception to “nothing”: like any host, the deployment platform keeps standard request logs for abuse and outage handling. Those belong to the platform, not to this registry, and they are not used for the map or the stats.
Third parties the site talks to
GitHub’s API (your public profile fills the sign-in session and the profile card), live DNS resolvers (to answer the “did it work?” panel), and the hosting platform itself. Static-site deployments store your uploaded files with the platform’s blob storage, tied to your name. None of these receive anything beyond what is needed to answer your request.
Removing your data
Release the name on the manage page and the record (country field included) is deleted from the registry. Git history on the public repo keeps past versions of records, as it must for a registry whose integrity is its history; truly sensitive data should never go into a record in the first place.