Privacy Policy

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). We do not log, store, or persist them. The same applies to every other API call described below.
• 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. It is never stored on our servers.

You can disable the page-view beacon below. Browsers that send a Do Not Track header or the newer Global Privacy Control signal are honoured automatically.

What we do not do

• No cookies. The site sets zero cookies for tracking or any other purpose.
• 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 name, email, or any contact information.
• No data sold, traded, or shared with anyone for marketing purposes.
• No signature, transaction, or token approval is ever requested by this site. 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 two 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.
• 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).
• cloudflare-ipfs.com, ipfs.io — public IPFS gateways, used as image fallbacks if the canonical store is unavailable.
• api.dexscreener.com — NCT token price + pool data for the token widget.
• dexscreener.com — sandboxed iframe in the NCT section showing the live chart.
• hmvideo.servitor.live — community-hosted CDN serving the anthem video on the home page.
• static.cloudflareinsights.com — Cloudflare's privacy-first analytics. Cookieless; no cross-site tracking.
• No Google Fonts. The brand fonts (Playfair Display, Space Grotesk, 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 to 1 if 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-lived sessionStorage cache 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.

If you use the site on a shared device, you can clear all of it below in one click. None of these keys contain anything that would identify you to us if exfiltrated; they are convenience state only.

Your controls

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, eth_sendTransaction, or any other write operation. If you choose to name a Hashmask, you do so on the official rename interface, which is hosted by Suum Cuique and not by us; we link out to it via an explicit "Continue" modal.

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 store nothing on our servers that identifies you, there is no personal profile to access, correct, port, or delete. 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.