Privacy Policy
Last updated: 6 July 2026
This policy explains what happens to data when you use the website at ethernames.com and its subdomains (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, 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 privacy@dinosat.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, contact privacy@dinosat.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. 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.
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, is not transmitted to us, and 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.
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.
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. It forwards the query to upstream node providers (currently QuickNode and Alchemy), caches results for immutable block ranges, and keeps limited operational logs for security and reliability. We do not use this data 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.
- 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.
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. Our upstream providers are reached through that service, which forwards your request but not your IP address, as described in Section 4;
- the WalletConnect (Reown) relay, if you choose to connect a wallet that way;
- IPFS gateways, 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 subdomain action) and every value you store through the Protocol, including your address, names, records, content hashes, and avatars, 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.
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. Operational and security logs at the hosting and query-service layers are kept only as long as needed for those purposes and are then discarded or rotated in the ordinary course. 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). For the limited operational data we process, contact privacy@dinosat.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
privacy@dinosat.com