Quake Name — Cookie Notice
The Quake Registry uses exactly one thing that sets a cookie: Google Analytics, to count visits. This notice names those cookies, describes the browser storage used besides them, and tells you how to switch the analytics off — because a claim about tracking is only worth as much as your ability to check it and act on it.
Analytics is on, and you can turn it off
Google Analytics counts visits and shows which registry pages get read. It starts switched on. The control at the foot of this page switches it off, at any time, in either direction — that is the whole mechanism, and it is why you are not made to answer a pop-up before you can read anything.
Switching it off takes effect immediately rather than at the next reload, and deletes the analytics cookies already in your browser. Nothing else about the application changes; there is no part of it that requires being measured.
If your browser sends a Global Privacy Control signal, analytics stays off from the start unless you switch it on here yourself.
No advertising, and no profile of you
Google Signals and ad personalisation are switched off on this property. The measurements are not joined to advertising profiles, not used to build advertising audiences, and not shared for cross-context behavioural advertising. There is no advertising network and no remarketing pixel anywhere here.
The measurements are also never joined to your wallet address, your sign-in, your bids, or anything you own. What is counted is pages, not people.
The cookies analytics sets
Two, both first-party — set on this domain rather than by an outside site — and both present only while analytics is switched on:
- _ga — a random identifier for the browser, so that a second visit is not counted as a second visitor. It expires after two years.
- _ga_<stream> — the same, scoped to this specific property, plus session state. It expires after two years.
What else it uses: browser storage
Everything the application itself needs is kept in your browser's session and local storage, which — unlike cookies — is never transmitted to a server automatically. Seven keys, all strictly necessary:
- quake:tenant — the site configuration, cached for the tab
- quake:jwt, quake:jwt:pubkey, quake:jwt:role — your sign-in session, discarded when the tab closes
- quake:ack:<site>:<address> — which version of the disclosures you have accepted
- quake:consent and quake:consent:at — your analytics choice and when you made it. Kept even when you switch analytics off, because forgetting the choice would mean asking again and defaulting back on.
Requests the wallet component makes on load
Turning off a component's analytics is not the same as it making no requests, so: the Reown (WalletConnect) sign-in component fetches its configuration from api.web3modal.org and its fonts from fonts.reown.com when the page loads. Those carry your IP address, as every web request does. Its usage analytics — which would otherwise post to pulse.walletconnect.org — are switched off.
This is not a cookie and cannot be turned off without removing the ability to connect a wallet, which is the entire application. It is listed here because you cannot check what you have not been told about.
Storage set by the wallet component
If you connect a wallet or sign in with email or a social account, the Reown (WalletConnect) component that provides that flow stores its own state under keys beginning with "@appkit". That includes connection state, recently used email addresses, a social username, and cached identity and balance data. It is set by that component, governed by their policy, and it stays on your device.
Clearing site data in your browser removes all of it. Doing so signs you out and makes the disclosure acknowledgement appear again; it does not affect your wallet, your bids, or anything you own.
The registry website
The public registry site at quake.name is a separate, static site. It runs Google Analytics as well, reporting into the same account. This notice is published on both and describes both, so there is no second document with different terms in it.
One difference worth stating plainly: the switch described above is part of the application. The registry site has no equivalent control of its own yet, so declining there means using your browser's own cookie settings. Either way the choice is stored per site, so making it in one place does not carry it to the other.
Contact
Questions about any of this: privacy@quake.name.