ens.diamonds
DiscoverVaultsFavouritesPortfolioAbout
ens.diamonds

Pool ETH with friends to claim premium ENS names together. Escrowed onchain, owned by a multisig you all control.

Audited by OneDollarAudit
ExploreDiscoverVaultsFavouritesPortfolio
ProtocolEscrow contract ↗ENS app ↗Safe ↗Resolvio ↗
MoreAboutFeedback ↗TermsPrivacyRisks
© 2026 ens.diamonds · open-source
Built by Namespace NinjasNamespace
ens.diamonds
Terms·Privacy·Risks

Privacy Policy

Last updated: 20 July 2026

1. The short version

ens.diamonds has no user accounts. We never ask for your name, email address, or any identity document, and we run no advertising or cross-site tracking. What we process is your public wallet address, the vault data you create, and the minimum technical data needed to keep the site running. Everything below is the complete list, written from the actual code.

2. What we process

  • Wallet address. When you connect a wallet, the Interface sees your public address. If you sign in (Sign-In with Ethereum), your signature is verified and your address is kept in an encrypted session cookie in your browser.
  • Data you create. Favourited names, vault visibility settings, registration coordination data, and portfolio records are stored keyed by wallet address in a managed Redis database (Upstash), so they are there when you come back.
  • IP address, transiently. Your IP is used for per-minute rate limiting to protect the site from abuse. Rate-limit counters expire automatically within minutes and are not used for anything else.
  • Hosting logs. The site runs on Vercel, whose infrastructure keeps standard request logs (IP, URL, user agent) for a limited period, as any web host does.

The Interface currently runs no analytics and no error-tracking service. If that changes, this policy will be updated first.

3. Cookies

The site sets a single, strictly necessary, encrypted session cookie when you sign in with your wallet. It contains your session and nothing else, is never used for tracking, and is deleted when you sign out or when it expires. There are no advertising or third-party cookies, which is why there is no cookie banner.

4. Who else sees traffic

To work, the Interface talks to services we do not operate. When it does, those services see the technical data any web request carries (such as your IP address), and where relevant the addresses or names being looked up:

  • An Ethereum RPC provider, to read the blockchain and broadcast your transactions.
  • Resolvio, to resolve ENS names and avatars (and the euc.li avatar image gateway).
  • The Graph, to list expiring ENS names (queried from our servers, not your browser).
  • WalletConnect, only if you connect a wallet through it.
  • Vercel (hosting) and Upstash (database), as processors of the data described above.

Each operates under its own privacy policy. We do not sell or rent any data to anyone.

5. The blockchain is public

Deposits, withdrawals, vault participation, and ENS registrations happen on Ethereum, a public and permanent ledger. That data is visible to everyone, forever, and is replicated worldwide. Nobody, including us, can edit or delete it. If your wallet address is ever linked to your identity elsewhere, your on-chain history could be too. Please weigh that before transacting.

6. Retention

Session cookies expire on their own. Rate-limit counters expire within minutes. Favourites, visibility settings, and portfolio records are kept so the product works across visits, and removals you make in the Interface (such as unfavouriting a name) take effect immediately.

7. Your choices

You can use most of the site without connecting a wallet at all. You can disconnect your wallet and sign out at any time, use a fresh address to avoid linking activity, and clear the session cookie in your browser. For anything else concerning your data, reach the team in the Namespace Telegram group. Note that we cannot alter on-chain data (see section 5).

8. Children

The Interface is not directed at children and may not be used by anyone under the age of legal majority.

9. Changes

If this policy changes, the new version is published on this page with an updated date. Material changes, such as adding an analytics service, will be reflected here before they go live.