Privacy Policy

Last updated: 27 August 2026

This policy explains what happens to data when you use the website at ethernames.com, its subdomains, the gateway we operate at ipfs.cc, and the services behind them (together, the "Interface"), operated by Dinosat Inc. ("Dinosat", "we", "us"). The Interface is a mostly static, non-custodial website for interacting with Ethernames, an ownerless protocol on Ethereum (the "Protocol"). It is mostly pages served to your browser, plus a small service we operate that passes read-only blockchain queries to node providers, described in Section 4. We built it to collect as little as possible. It has no user accounts, no cookies, no analytics of our own, no advertising, and no trackers, and we do not sell or share your personal data.

1. Who is responsible

Dinosat Inc. is the controller for the limited processing described here. You can reach us about privacy at info@ethernames.com or by post at the address in the Contact section below. Dinosat is established in the Republic of Seychelles and has no establishment in the EEA or the UK. Given the limited nature of the processing described here, we have not appointed a representative under Article 27 of the GDPR or a Data Protection Officer. If you are in the EEA or the UK and have a privacy question, reach us at info@ethernames.com and we will respond as required by applicable law.

2. What we do not do

The Interface sets no cookies and uses no analytics, advertising, fingerprinting, or third-party tracking of our own. There are no accounts to create and no profile is built about you. We do not sell, rent, or trade personal data, and we run no advertising or marketing on it. One thing here is not ours: if you connect a wallet through WalletConnect, that SDK sends telemetry to Reown from your browser. Section 5 says what it sends, and connecting with a browser wallet avoids it entirely.

3. Data that stays in your browser

To function, the Interface stores a small amount of data in your browser's local storage. It stays on your device and is not sent to us, with the one exception below. It includes:

which wallet you last connected (so it can reconnect automatically);
your in-progress registrations, including the secret each one needs to be completed;
a cache of the names owned by addresses you have viewed, to avoid re-scanning the chain;
the referrer label from a referral link you arrived through, kept for 30 days, so that a registration can credit that referrer. Section 5 of the Terms explains what it does;
if you connect with WalletConnect, that SDK stores its own session, keys, and client id under its own names.

The exception is the registration secret. When you start a registration, the name you chose, your address, the referrer, and the secret are sent once to the query service in Section 4 as a read-only call, so that the contract itself computes the commitment hash rather than the browser reproducing it. That request reaches our worker and the node provider behind it. We do not store it, but it would not be accurate to say the secret never leaves your device.

You can clear this at any time through your browser. Note that discarding an in-progress registration also discards the secret needed to complete it, which cannot be recovered, and that clearing storage while a WalletConnect session is live will end that session.

4. Data processed when you use the Interface

Because the Interface talks to networks and infrastructure, some technical data is necessarily processed:

Hosting. The Interface is served from Cloudflare's network. Like any web server, the hosting layer processes your IP address, user agent, and basic request metadata to deliver the pages and to keep the service secure and reliable.
Blockchain reads. To keep our paid node-provider keys off the public Internet, read-only blockchain queries from your browser pass through a small service we operate at api.ethernames.com (a Cloudflare Worker). In handling those queries, that service processes your IP address and the request itself, which can include a wallet address you are looking up, such as when the Interface reads the names an address owns, and the name and secret behind a registration you are starting, as described in Section 3. It forwards the query to upstream node providers (currently QuickNode and Alchemy) and caches answers for block ranges that can no longer change, for up to seven days, keyed on the query rather than on you. It limits how many requests any one IP address may make, to stop a single caller using up the capacity we pay for. We do not use any of this to build a profile of you or to track you across sites. If that service is unavailable, your browser falls back to public RPC endpoints, which then see your IP address and requests directly.
The gateway. We operate a gateway at ipfs.cc that serves a name's website at name.ipfs.cc. It sees the visitor's IP address and the name asked for, resolves that name against the chain, and fetches the content from public IPFS gateways. It holds a name's pointer and its content in an edge cache for five minutes each, sets no cookies, and clears cookies on the domain on every response. It also keeps a list of names it will not serve.
Stats. The Interface reads a public, aggregate snapshot of Protocol statistics (total names, owners, and the like) from the same worker. That snapshot contains no personal data.
Email. If you write to us, we receive your address and whatever you put in the message, which for an abuse report or a rights request can include your name and evidence of your rights. We use it to deal with what you wrote about, and for nothing else.

5. Third parties your browser talks to

When you use the Interface, your browser communicates directly with third parties that we do not control. Each of them may see your IP address and the requests you make, under its own privacy policy:

your wallet software or extension;
Ethereum RPC and node providers: the public fallback endpoints, which your browser contacts directly and which see your IP address when the service we operate is unavailable. They are Allnodes, Tenderly, dRPC, CoW, and Pocket Network. Our paid providers are reached through the service we operate, which forwards your request but not your IP address, as described in Section 4;
the WalletConnect (Reown) SDK, if you choose to connect a wallet that way. It is Reown's code running in your browser from our page, and it reports to Reown's own endpoints: a relay for the wallet session, a verification frame, and a telemetry endpoint that receives our domain, your browser's user agent, a WalletConnect client id, and, on a successful connection, your wallet address. None of that reaches us, and none of it runs if you connect with a browser wallet instead;
the hosts that serve pictures. A name's avatar record can point at any website, and your browser loads the image straight from there, so that host sees your IP address and the page you were on, without you clicking anything. We do not proxy it. Artwork for NFT avatars and for the avatar picker comes from 4everland, Pinata, Rarible, ipfs.io, and a collection's own server, and the picker requests one image for each token your wallet holds;
IPFS gateways we do not run, when the Interface resolves or previews content that a name points to;
block explorers and other sites, when you follow an outbound link.

We are not responsible for how these third parties handle your data. Review their privacy policies if that matters to you.

6. Blockchain data is public and permanent

Any transaction you send (a registration, renewal, record change, transfer, or subname action) and every value you store through the Protocol, including your address, names, records, content hashes, avatars, and the referrer recorded against a registration, is public, permanent, and replicated across every Ethereum node. This data is written to a public ledger that no one, including us, can edit or erase. Blockchain addresses are pseudonymous but can be linked to your identity by you or by others. Do not put anything on-chain that you may later want removed.

That is true of the chain record. It is not true of this site: the pages we serve, the content our gateway serves, and our short-lived caches are copies of ours, and we can stop serving them. We separately operate ether.page, which serves a public, search-indexable page for every ethername from those same public chain records, under its own policy.

7. Why we may process this data (legal bases)

Where data-protection law such as the GDPR applies, we rely on our legitimate interests in operating, securing, and maintaining the Interface and in preventing abuse, and on taking steps at your request to let the Interface function when you choose to use it. We do not process personal data for marketing and do not rely on consent-based cookies, because we set none.

8. Retention

Data stored in your browser stays until you clear it. The operational and security logs at the hosting, query-service, and gateway layers are our providers' logs rather than a store of our own, so their retention is set by those providers, and a line in one can hold an IP address alongside the name or address that was requested. We do not use them to build a profile of anyone or to follow anyone across sites. Cached answers expire on the schedules in Section 4, and we can drop one sooner. Email you send us is kept as long as it takes to deal with what it is about. Data written to the blockchain or to IPFS networks is outside our control and is not something we can delete.

9. Your rights

Depending on where you live, you may have rights to access, correct, delete, restrict, or object to the processing of your personal data, and to data portability. Because of how the Interface is built, most data is either on your own device (which you control directly) or on a public blockchain (which no one can alter). Where we rely on our legitimate interests, you may object to that processing on grounds relating to your particular situation. We cannot change or delete anything written to the chain. What we do control is our own copies: a cached answer at our edge, content served through our gateway, and the pages we serve. Those we can stop serving. For the limited operational data we process, reach us at info@ethernames.com and we will respond as required by applicable law. You may also have the right to lodge a complaint with your local data-protection authority.

10. International transfers

The Interface is delivered over a global content-delivery network and interacts with service providers that may operate in various countries. As a result, technical data such as your IP address may be processed outside your country of residence. Where personal data is transferred out of the EEA or the UK, we rely on an adequacy decision where one applies, on appropriate safeguards such as the Standard Contractual Clauses (or the UK equivalent) operated by our providers, or on the transfer being necessary to provide the Interface you have requested.

11. Children

The Interface is not directed to, and may not be used by, anyone under 18 or the age of majority in their jurisdiction. We do not knowingly process the personal data of children.

12. Security

We serve the Interface over HTTPS with a strict content-security policy and related protections, and we keep our node-provider keys server-side rather than in the browser bundle. No system is perfectly secure, and the security of your keys and wallet is your responsibility.

13. Changes to this policy

We may update this policy from time to time. When we do, we will post the new version on this page and update the "Last updated" date above. Your continued use of the Interface after a change means you accept the updated policy.

14. Contact

Dinosat Inc.
Suite 9, Ansuya Estate, Royal Street
Victoria, Mahé, Republic of Seychelles
info@ethernames.com