Privacy
What is not collected
No email address, no device token, no account, no password. Notifications are polled by your browser rather than pushed, because pushing would require an address to push to.
How ownership is stored
Allocations, listings, offers, watchlists and notifications are keyed by a hash of your address, never by the address itself. The tables cannot be read as a list of who holds what — not by an operator, and not by anyone who obtains a copy.
What a wallet session is
One signed cookie, zb_wallet, holding your address and an expiry. It grants no spending power and carries no viewing key. Losing it exposes nothing beyond the address; deleting it ends the session. It is the only cookie this site sets by itself — the support widget sets its own, and only from the moment you open it.
What your browser keeps
Four preferences in local storage, none of which leaves your device: zb_market_panel (whether the market column is shown), zb_notifs, zb_price (ZEC or dollars) and zb_motion (reduced animation). Clearing site data removes them and costs you nothing but the settings.
What is public
The catalog: which items exist, their traits, their hashes, and the transactions that issued them. Sales that settle through this venue are published as amounts and times, with no party on either side.
What you choose to reveal
A profile is opt-in and per item: a handle, a display name, a bio and a link, plus whichever items you put on display. An item you do not put on display is indistinguishable from an item nobody owns.
Product analytics
Page views and a fixed list of named events go to Vercel Analytics from your browser. The events carry the shape of what happened and nothing else — a collection slug, which is public, and a count. Never an address, never a price, not even a price bracket: a stream of "this address bought that item for that much" would rebuild the ownership graph on somebody else's server, which is the linkage this venue exists to prevent. Blocking analytics breaks nothing here; the calls fail silently by design.
Asking for help
Support is ours: the help articles, the automatic replies and the conversation itself are served by this site and stored in its own database, and no third party is involved in any of it. Nothing is loaded and no cookie is set until you open Support. Reading articles sets nothing at all. When you send a message while a wallet is connected, the conversation is kept with that address, so you find it again from any device you connect it on, and whoever answers can see which wallet is asking — that is how a payment gets looked up. When no wallet is connected, sending your first message sets one cookie holding a random key, and the conversation is kept against a hash of that key rather than anything about you; connecting a wallet later in the same browser moves the conversation to the wallet, unless that wallet already has one. We do not ask for a name or an email, and replies are not sent anywhere: they wait in the window for the next time you open it. Send what answers the question and no more — a transaction id is enough to trace a payment, and being shielded it discloses neither the amount nor the other party to whoever reads the conversation later.
Server logs and rate limits
Requests reach the site through a host that sees your IP address. Unauthenticated requests are counted per IP over a short window so that one caller cannot exhaust the venue; signed-in ones are counted per address instead. These counters live in memory and are not a history of what you looked at.
Who else touches it
Vercel hosts the site and receives the analytics described above. A managed Postgres database stores the catalog and the hashed tables. Pinata pins creator uploads to IPFS, where they are public and permanent by design. A ZEC price is fetched from Kraken, falling back to CoinGecko, by the server rather than your browser, and those requests carry nothing about you.
How long things last
What is on chain is there forever and outside anyone's reach, including ours. Pinned artwork is meant to persist and can be copied by anyone. The database keeps catalog and market rows for as long as the venue runs, because a market with a disappearing history cannot be audited. Rate-limit counters expire within minutes.
Your rights, and their limit
In the EU you may ask what is held about you, ask for it corrected or erased, object to processing, and complain to a supervisory authority. The honest limit: addresses are stored as one-way hashes, so we cannot look you up and cannot tell your rows from anyone else's unless you prove control of the address first — the same proof used to connect a wallet. Nothing on chain can be erased by us on request or otherwise.
Children
This venue is not for anyone under eighteen, and nothing here is directed at children.
Changes
This page can change. The date at the top is the version, and it moves only when the words do.
Ownership is private by default. Prices are known only to the parties involved.
