Privacy Policy
Last updated: November 2026
This website (thehashmasks.xyz) is a community-built interface for the Hashmasks NFT collection. We try to keep our data collection minimal and transparent. This page explains, as precisely as we can, what reaches our servers when you visit and what stays on your device.
What we collect
- Anonymous page-view counter. On every page load we fire a fire-and-forget GET request to our community-run Cloudflare Worker (
names.thehashmasks.xyz/beacon) with a single parameter — the page name (e.g.home,vitrine). The Worker increments a counter. No identifier links the request back to you on our side. - Network metadata reaches our infrastructure. Because the beacon is a real HTTP request, your IP address and User-Agent string are visible to the Worker at the network layer (the same is true of every external request your browser makes, and of every other API call described below). Cloudflare's request logs for our Workers keep each request for a few days, with its address (an owner lookup's address holds the wallet it asks about) and the IP it came from, so we can keep the services running; we don't copy them anywhere or use them for anything else. When a page of this site asks a Worker on your behalf (a mask page, a Vitrine's link preview), it passes your IP along so that Worker can apply its rate limits to you, so it is in those logs too.
- The museum's daily count. Once a day, the museum (
/museum) sends one request tonames.thehashmasks.xyzsaying only whether this browser had visited the museum before, and the Worker adds one to that day's count. So that a browser is counted once a day at most, the museum keeps the date of its last count in your browser's local storage (hm:museum:counted). - The museum's guestbook — only if you sign it. What you write, and the name you give (you can leave it out), is stored by
names.thehashmasks.xyzand shown to everyone in the museum, with the date. Links, web addresses, contact details and rude words are refused. So that nobody can sign it over and over, the Worker keeps a scrambled code made from your IP address and the day, for one day; your IP address itself isn't stored. To have an entry taken out, ask on our Discord. - The museum's holo card question — only if you answer it. On the holo card's panel the museum asks whether you would burn NCT for a holo card of your own Hashmask. Your answer (yes, maybe or no) is sent to
names.thehashmasks.xyzwith one more thing: whether a wallet you connected holds a Hashmask (never the wallet's address). The answers are counted, never shown. So that a visitor is counted once a day, the Worker keeps a scrambled code made from your IP address and the day, for one day, as for the guestbook; your IP address itself isn't stored. The museum remembers your answer in this browser (hm:museum:poll:holo-card). - Your wallet address — only when you connect. If you click "Connect Wallet" and approve in your wallet, we read your public Ethereum address from the browser and send it to the lookup APIs below in order to fetch your holdings, NCT balance, and any vault delegations. The answers about a wallet (its Hashmasks, its NCT) are kept by
market.thehashmasks.xyzfor up to a day so pages load fast, and to answer it asks its own data providers (Alchemy, OpenSea) about the address. - Tips — only if you send one. When you tip a mask's holder, the transaction's hash and the mask's number go to
market.thehashmasks.xyz, which reads the transfer from the blockchain and shows it — both addresses, their ENS names, the amount and the date — on the mask's page and on both wallets' Vitrines, for good. It is a public transfer on Ethereum either way.
You can disable the page-view beacon below, and the museum's count with it. Browsers that send a Do Not Track header or the newer Global Privacy Control signal are honoured automatically.
What we do not do
- No tracking cookies. One page behind a password sets one strictly necessary cookie, only after it is entered:
hm_card(the holographic card page). - No browser fingerprinting, session stitching, or cross-site identifiers.
- No third-party advertising or marketing trackers (no Facebook Pixel, Google Analytics, Hotjar, Mixpanel, Sentry, etc.).
- No personal data collected — we never ask for your email or any contact information. The museum's guestbook asks for a name, which you can leave out or make up.
- No data sold, traded, or shared with anyone for marketing purposes.
- No signature or token approval is ever requested by this site. The only transaction it can ask your wallet for is a tip you start yourself on a mask page: one plain transfer to the mask's holder, which you review first. Naming a mask happens on the official Hashmasks rename interface, which we link out to.
External services we contact
The site fetches data from these origins. Each receives your IP and User-Agent as a side-effect of the HTTP request. Each has its own privacy policy.
- Cloudflare — hosts the site (Pages) and our community Workers. Edge logs are operated by Cloudflare.
- market.thehashmasks.xyz — community-run Worker that serves sales, listings, holder lookups, mask metadata, NCT price proxy. Receives your wallet address on owner lookups.
- names.thehashmasks.xyz — community-run Worker that serves rename events, NCT activity, the page-view beacon, naming counts, and the museum's guestbook and daily count.
- hashmap.azurewebsites.net — the original Hashmasks mask metadata API (Azure-hosted). Used as a fallback when the local cache is empty.
- stats.thehashmasks.xyz — community Discord bot that also serves the floor-price / owner-count statistics shown on the homepage.
- hashmasksstore.blob.core.windows.net — Azure Blob Storage hosting the canonical mask artwork (.jpg + .png preview).
- api.dexscreener.com — NCT token price + pool data for the token widget.
- dexscreener.com — sandboxed iframe in the NCT section showing the live chart.
- video.thehashmasks.xyz — Cloudflare R2 bucket serving the anthem video on the home page.
- engage.thehashmasks.xyz — community-run Worker that serves the latest @TheHashmasks posts shown under "Latest on X" on the home page and in the museum.
- pbs.twimg.com (X Corp.) — the avatars and pictures of those posts, loaded from X's image host without telling X which page you're on.
- Your wallet's own network provider — when you tip, the tip dialog reads the mask's owner, your balance and the token prices through your wallet, which asks its own Ethereum node.
- No Google Fonts. The brand fonts (Clash Display, Geist, JetBrains Mono) are now served from our own origin, so Google never sees your IP for typography.
Local storage on your device
We use your browser's localStorage and sessionStorage to remember preferences and short-lived caches. Everything stays on your device and is never transmitted to us. We use the prefixes hm_ and hm: exclusively. The keys we may write are:
hm_wallet_user_disconnected— set to1if you explicitly clicked "Disconnect Wallet", so we don't silently reconnect on your next visit.hm_no_track— set if you opted out of the page-view beacon below.hm:vit:pin:<address>,hm:vit:flex:<address>,hm:vit:setExpanded:<address>,hm:vit:wishlist:<address>— per-wallet Vitrine UI preferences (pinned mask, flex slot, set expansion, wishlist toggles).hm:vit:vs:recent— up to 3 most-recent addresses you've compared in the Versus tool, so the suggestion chip remembers them.hm:vit:session:<address>,hm:vit:vs:<address>— short-livedsessionStoragecache of an owner-API response (cleared when you close the tab).hm:vitrine-bar-dismissed,hm:vit:otd:dismissed— flags so dismissed banners stay dismissed.hm:museum:flight-seen,hm:museum:tour-offered,hm:museum:music— in the museum: that its first-visit flight was shown, that its guided tour was offered, and whether you turned its music on.hm:museum:counted— the day the museum last counted this browser's visit (see the museum's daily count above).hm:museum:stamps— the museum's rooms you've visited and the day of each, for your stamp card, and its bonus stamps: after hours, and a sale or a naming you were there for (with that Hashmask's number, and the price or the name).hm:museum:poll:holo-card— your answer to the museum's holo card question and its day, so the panel shows it.hm:delegate-vault:<address>— the wallet linked on delegate.xyz that you chose to show for the wallet you connected;hm:delegate-not-now:<address>(sessionStorage) — the linked wallets you said "No thanks" to this session.hm_mask_back,hm_mask_steps(sessionStorage) — where a mask page's back link returns to.hm_nameplate_picker— the old nameplate design panel's settings, if you ever used it.hm:lab:active— the Lab's generation in progress (the Lab is closed for now). An olderhm:lab:testkeyis deleted by the site.
If you use the site on a shared device, you can clear all of it below in one click. Some keys and values are wallet addresses; they are convenience state only, and never sent to us.
Your controls
Anonymous page-view beacon
This counts how many people are visiting. Disabling it has no effect on functionality. We honour your browser's Do Not Track and Global Privacy Control signals automatically; this toggle is for fine-grained control if your browser doesn't send those.
Beacon enabled.
Clear all local data
Wipes every hm_ / hm: key from this browser's localStorage and sessionStorage. The site will start fresh on your next visit, as if you'd never been here. Your wallet, on-chain holdings, and on-chain naming history are NOT affected — those live on Ethereum and are outside the scope of any website button.
Currently stored on this device: 0 key(s).
Wallet connection
Connecting a wallet is read-only. We use the standard EIP-1193 / EIP-6963 wallet API to read your address — we never call personal_sign, eth_sign, signTypedData, or ask for a token approval. The one write is a tip you start yourself: the tip dialog asks your wallet for one eth_sendTransaction (a plain transfer to the mask's holder, after a review screen) and, if needed, to switch to Ethereum. If you choose to name a Hashmask or claim NCT, you do so on the official site, which is hosted by Suum Cuique and not by us; we link out to it, from the Vitrine through a "Continue" box, from the wallet panel directly.
Disconnecting from the site simply tells us not to reconnect automatically. The wallet itself remains "site-authorized" until you revoke that in your wallet extension's settings — that's a wallet-level permission we cannot revoke from outside.
Your rights
Because we collect no personal data and keep no profile of you, there is no personal profile to access, correct, port, or delete. What is public stays public: a tip or a guestbook entry is shown to everyone, and we can take one off the site if you ask. If you have questions, you can reach us via the community Discord.
Changes to this policy
If our data practices change, we will update this page with a new date at the top. There is no email list to notify; if you care, check back occasionally.