Privacy notice

1. In brief

2. What we hold

2.1 Server logs

Requesting a page necessarily tells our hosting provider your IP address, your user agent, the URL you asked for and the time. This is the ordinary technical record of delivering a web page, and we use it only to serve the site and to identify abuse — traffic floods, upload abuse, scripted hammering of the RPC. It is not used to build a profile of you.

2.2 Cookies, local storage, and your consent choice

Every cookie and stored value is listed by name, lifetime and contents in the cookie notice, which counts them from the code rather than from a sentence — this notice deliberately does not carry a second copy of that number. Most are strictly necessary; the referral cookie and your interface preferences are not, and nothing outside the necessary category is written until you allow it. None of them carries an advertising identifier and none is readable by another site.

Your consent choice is itself recorded in a cookie, hood_consent, on your own device — what you allowed, when, and which version of the cookie notice you were shown. We deliberately keep no server-side copy of it: a consent log would be a new record about you, created at the moment you refuse, held for people who refused most of all. It would also be the only thing on this site tying a browsing session to a stored row for somebody who never signs in. The cookie travels with your requests, which is all we need to honour it.

The consequence, stated because it cuts both ways: we cannot produce a history of your consent choices, for you or for a regulator. What exists is the current record on your device, which you can read yourself in Cookies & storage in the footer.

2.3 Your account, if you sign in

Browsing this site creates no account. Signing in does, and signing in means proving you hold a wallet by signing a message — never a password, and never anything we could use to move your funds. From that point we hold a record keyed to your wallet address containing only what you put in it: a display name if you set one, a profile picture if you upload one, an @handle, a bio, a motto, a website and a banner choice if you set them, whether your profile is public and which of its sections you show, private labels you have written against other wallets, and your alert preferences.

Your public profile. Your account has a public profile page and a profile card shown when someone points at your name on the leaderboards. It is private by default. While private, it shows only your wallet address in shortened form and the Light or Dark allegiance derived from your on-chain activity — facts already visible on the public blockchain. If you switch your profile to public, it also shows the display name, avatar and @handle you chose, and any of these sections you individually switch on: motto, bio, badges, the date you joined, bands, your verified X account and website, your launches, prediction markets you created, your season standing, showcased items, your public activity (launches, settlements and claims — never trades or stakes), and your holdings of tokens launched on The Hood. Every section is off until you turn it on, and you can turn any of it off at any time in Account → Profile. The effect is immediate on our pages, though copies others have already made are outside our control.

We never publish your full wallet address on a profile, never link it to a block explorer, and never show your private wallet labels. A profile is found by a random identifier, never by your address; a handle, while your profile is public, becomes a web address (/u/your-handle) and shares one set of names with referral links.

A signed-in session is carried in a cookie that identifies the session and nothing else. It is strictly necessary — the site cannot know it is you without it — and it ends when you sign out. A profile picture you upload is stored by us and served from our own domain rather than pasted from somewhere else, which is why it survives and why nobody else can swap it later.

Everything in this record is optional except the address, and the erase button on your settings page clears it. It does not reach everything on this page — what it does and does not remove is set out in full in section 8, and the difference matters.

2.4 Your connected X account

Connecting X is optional. It is required only to mint a referral code or to hold a KOL rank, and the reason is that a wallet costs nothing to create — without it, one person with a script holds as many referral codes as they have addresses.

We ask X for read-only access and store four things:

• X’s own account identifier — a number, not your handle. This is the identity we key on, because a handle can be renamed and the freed name claimed by somebody else.
• Your handle, as a display cache, refreshed when we re-check.
• Whether the account carries a live X Premium badge, and when we last asked. A badge is a subscription and lapses, so we re-read it daily rather than recording it once.

We do not receive or store your posts, your followers, your email address or your password, and the access we are granted cannot post, follow, like or message as you. We do not keep the token X issues: it is used once to read the profile and discarded, and the daily re-check uses an application credential that identifies this platform rather than you.

What reaches the public blockchain is a true or false against your wallet address, and nothing else. No handle, no account identifier and no other X data is ever written to a public ledger.

The pairing is permanent. A wallet and an X account are bound to each other once connected: it cannot be moved, changed or removed. That is a deliberate restriction rather than a limitation — your referral name and your KOL standing are both tied to the handle, and allowing the link to move would carry them to a different one. To use a different X account, connect it to a different wallet.

2.5 Referral records

If you mint a referral code we record the code, the name attached to it, and which wallets were attributed to it and when. If you arrive through somebody else’s link we record which code brought you, once and permanently — that binding is what decides who is paid, so it cannot be rewritten afterwards, by you or by us.

These rows are about more than one person, which is why erasing your account does not delete them: they record who referred somebody else and what that person is owed. Section 8 says so in the place it matters.

2.6 Your watchlist

Starring a launch or a prediction market records one row against your account: what you starred, which chain it is on, and when. Starring the same thing twice is the same state rather than two rows, and un-starring deletes it. It is read to render your own watchlist and for nothing else — it is not used to profile you, it is not shared, and it is not published anywhere on the site.

2.7 Comments you post on a prediction market

A comment is public on this site and is the one thing here you write for other people to read. It is stored against your account with your wallet address, the market it is about, what you wrote and when.

It also records the position you held at the moment you posted — which side and how much — and that snapshot is kept permanently alongside the comment and shown with it. That is deliberate and is stated here rather than left to be found: a live read of your position says what you hold now, and somebody who talks a side up and then sells out of it leaves no trace in a live read. The figure recorded when you wrote the sentence is the only one that can ever be checked against it.

So a comment is a public, durable statement tied to your address and to what you stood to gain when you made it. Erasing your profile does not remove it, and neither does clearing your watchlist. Section 8 says exactly what that button does and does not reach, and how to have a comment taken down.

2.8 Reading measurement on the blog

If you allow the reading-measurement category — and only then — we measure, on a blog article, how long you actively spend reading it, how far down you get, and whether you left within a few seconds. The message sent when you leave carries the article’s name and those three figures and no identifier of any kind: no cookie, no account, no fingerprint, nothing joining one article to the next.

What is kept is a daily counter per article, not a record of you. Your reading is added into totals for that article and that day — how many sessions, how many fell into each time band, how many reached the end, how many left at once — and the individual measurement is discarded in the same operation. There is no row anywhere holding your reading, which means there is nothing about it to show you, export or delete: section 8’s rights have no subject here, because no personal data survives the aggregation. It is used to rank articles by demand and decide which one the blog page features.

As of 21-09-2026 this measurement is built and not yet switched on, so nothing is being measured at all. When it is switched on, the cookie notice is revised and your consent is asked for again rather than carried over. Full detail: section 5 of the cookie notice.

2.9 What we still do not do

We run no third-party analytics — the measurement in 2.8 is our own code writing to our own database, and nothing about it leaves this site. We embed no pixels, use no consent-management vendor, and load no fonts, scripts or stylesheets from a third-party CDN. There is no advertising identifier, no cross-site tracking, and no profile built from your behaviour. Every cookie here is set by this site and none of them is used to follow you; the cookie notice lists each one with its name, lifetime and contents.

3. Problem reports

The site has a Report a problem button. Pressing it lets you record what your browser is doing while you reproduce a fault, read the recording, and send it to us. It is the only thing on this site that collects anything about your visit, and it never happens unless you make it happen.

3.1 It is voluntary, and consented to one incident at a time

There is no standing permission and no setting to leave on. Every report is a separate, deliberate act with two gates: nothing is recorded until you press Start, and nothing is sent until you have read the recording and pressed Send. Between those two you can discard it, and closing the panel discards it. The recording lives in your browser’s memory until you send it, and vanishes if you do not.

Until you press Start, the recorder is not running. It is not idling, not buffering, and not installed — the code that watches network requests is not attached to your page at all.

3.2 What a report contains

• Network requests made by this page while you were recording — the method, the address, the status, how long it took, and the request and response bodies.
• Console output, JavaScript errors and their stack traces, and moves between pages within the site.
• The page you were on, your browser’s user-agent string, and the start and stop times of the recording.
• Anything you type into the note — an optional sentence describing what you were trying to do.
• Your wallet address, if you are signed in when you send it. It is taken from your session, so a report can be answered. Send it while signed out and it is anonymous, and the reference number is then the only handle anyone has on it — including you.

It is not a session recording in the sense that phrase usually carries: it does not capture your screen, your keystrokes, your mouse, or the contents of the page. Nothing reconstructs what you were looking at.

3.3 What is removed, in your browser, before anything is sent

Redaction happens on your device, before the report is transmitted — not on our server when it arrives. That distinction is the whole of it: a secret stripped after transmission has already been transmitted. What must not be stored is never sent.

These are removed and replaced with the word “redacted”:

• Sign-in signatures and the challenge nonces that go with them. That pair is a credential — anyone holding it could sign in as you.
• Session tokens, passwords, API keys, authorization values, JWTs, one-time codes and card numbers, wherever they appear, including inside request and response bodies.
• Anything shaped like a private key or a seed phrase. Nothing here ever handles one — your wallet extension does, and this page cannot read it — but the rule is absolute regardless.
• Email addresses.

Request and response headers are not captured at all, in either direction, so an authorization header or a cookie cannot be in a report whatever else happens.

3.4 What is deliberately kept, and why

Wallet addresses, balances and trade amounts are kept. We would rather say so than imply a protection that does not exist:

• Every one of those values is already public. They live on a public chain that anyone can read with a block explorer, permanently, with or without us — which is the subject of section 5 and was true long before this feature existed.
• Removing them would make the report useless. A failure here is a chain read that reverted or a quote that came back wrong, and both of those are addresses and amounts. A recording with them stripped cannot be told apart from a recording of something else, and asking you to send one would be dishonest.
• There is no way to remove only yours. Your wallet, the token, the curve and the factory are the same shape; a rule that removed some addresses and left others would read as a stronger promise than it could keep.

So the protection is that you see it first. The review screen shows the exact payload — not a summary of it, the thing itself — and it is not sent until you press the button.

3.5 How long a report is kept, and how to have one deleted

Reports are kept for 12 months from the day they are sent, and are deleted after that. One that is still being worked on is kept until it is closed, and then falls under the same 12 months.

To have one deleted sooner, write to privacy@thehood.markets and quote the reference number shown when it was sent. It is deleted outright — not marked hidden. If you sent it while signed in, quoting your wallet address is enough; if you sent it anonymously the reference is the only way to identify it, which is why the panel says to keep it.

Reports are read by the protocol owner and by nobody else. They are not shared with any third party, and there is no analytics or support product behind the button — the report is stored in our own database and read in our own admin panel.

4. Your wallet address

Connecting a wallet — which is not the same as signing in — grants this site permission to read your address. That happens in your browser. Connecting alone stores nothing: we do not record it, do not link it to an identity and do not keep a list of which addresses have visited.

Signing in is the point at which that changes, and it is a deliberate act rather than a side effect of connecting. From then on your address is the key your account record is stored under, along with anything you put in it, your watchlist, your comments and your referral records — sections 2.3 to 2.7. Nothing there identifies you beyond the address itself, and everything in it except the address is something you chose to add.

There is a second case that does not need you to sign in, and stating it is the point of this paragraph. If we withhold a wallet from the public leaderboards, we store that wallet address together with which of the two grounds applied, the reason we recorded, and the date — see section 12 of the terms, which also sets out your right to appeal. The record is kept after an exclusion is lifted, so that an appeal can be answered from what actually happened. It is read by us and by nobody else, it is not shared with any third party, and it affects visibility on this website only — never your funds, your tokens, your trades or your referral earnings.

Reads that concern only your own account — your balance, a simulated trade, waiting for a receipt — are sent through your wallet’s RPC connection rather than ours, deliberately, so your activity does not accumulate at our endpoint. When no wallet is installed they fall back to the public Robinhood Chain endpoint.

Your wallet extension is its own program with its own privacy policy. We cannot read its storage and it does not report to us.

5. What is public and permanent

These are consequences of the technology, not choices we make, and none of them is reversible.

• On-chain activity. Every launch, buy, sell, graduation and fee claim is recorded on Robinhood Chain against your address, permanently, and is readable by anyone with a block explorer. Addresses are pseudonymous, not anonymous: if your address is ever linked to you — by an exchange, a public post, an ENS-style name or chain analysis — the whole history becomes attributable.
• Project metadata. The name, symbol, description and links you enter when launching are written on chain and cannot be edited or removed afterwards.
• Uploaded artwork. Uploading needs a signed-in account. Each image is resized on our server — a logo to at most 512×512 pixels, a banner to at most 1500×500 — and re-encoded before anything is stored; the original file is never kept, and embedded metadata such as camera details and GPS location is removed. The resized copy is pinned to IPFS via a pinning provider. IPFS is a public, content-addressed network: anyone can fetch the file, and it cannot be deleted — unpinning stops us serving it, but any node that copied it keeps serving it forever. Do not upload anything containing personal data or an image you may want withdrawn.

6. Who else is involved

Three categories of provider necessarily see traffic:

• Our hosting provider — receives your request in order to return the page, and therefore sees your IP address.
• The RPC endpoint for Robinhood Chain — sees our server’s reads for server-rendered pages, not yours. For account-scoped reads your own wallet chooses the endpoint.
• The IPFS pinning provider and public gateways — receive uploaded artwork, and a gateway sees the request when your browser loads an image.

Each has its own privacy policy. We do not send any of them information about you beyond what the request itself requires.

7. Sharing and selling — what we do not do

• We do not sell your personal data.
• We do not share it with advertising or behavioural-targeting networks.
• We do not profile you, fingerprint you, or attempt to identify you across sites or visits.
• We do not link a wallet address to an identity, or keep a record of which addresses have visited. What we hold against an address is what you put there by signing in and using the site — a profile, a watchlist, comments, referral records — and none of it is joined to a name, an email or anything off this platform.

This is less a promise than a consequence of sections 2 and 3: apart from what you deliberately created and a report you deliberately sent, there is nothing here to sell, share or profile.

In the terms the US state statutes use: we do not sell personal information, and we do not share it for cross-context behavioural advertising, as California, Virginia, Colorado, Connecticut, Utah and the states that followed them define those words. We have not done so in the preceding twelve months. We do not process personal information for targeted advertising or for profiling that produces legal or similarly significant effects, and we do not knowingly collect or sell the personal information of anyone under 16 — see section 10.

The referral cookie is named here rather than folded in, because it is the one thing on this site that exists to attribute a visitor to a third party — the closest activity we have to what those statutes are drafted around. It is opt-in, it holds the referrer’s code and nothing about you, no third party is told anything when it is set, and switching the category off in Cookies & storage deletes it.

We honour the Global Privacy Control signal as an opt-out, everywhere and for every optional category, whether or not the statute that made it binding applies to you. Section 6 of the cookie notice says what it does and how to see that we received it.

8. Your rights

Depending on where you live, the rights below are yours under the GDPR, the UK GDPR, or the US state privacy statutes. Write to privacy@thehood.markets. We will not ask you to create an account to exercise one, and we will never treat you differently for exercising one — no price, no feature, no rank, no payout and no referral rate on this platform depends on whether you allowed a cookie or asked us to delete something.

The right-hand column is the part worth reading. It says what we can actually do, which for several of these is less than the right implies — and a notice that claims a right it cannot honour is worse than one that admits the limit.

A problem report you chose to send is deleted outright on request — quote its reference number — and so is a server log line.

An authorised agent may act for you where a statute allows it; we will ask for evidence of the authorisation and, where the law permits, for you to confirm it directly. We verify a request against whatever it concerns — control of the wallet for an account record, the reference number for a report — and if we cannot verify it we say so rather than acting on the word of whoever wrote in.

8.1 What the erase button on your settings page actually does

Stated as a list rather than as a reassurance, because the gap between the two columns is the whole of what somebody pressing it needs to know.

The account row itself is not deleted, and that is a consequence of the records it is attached to rather than a preference: deleting it would take a referral attribution with it, and an attribution decides who is paid. What it is left holding after an erase is your wallet address and nothing you put there.

To have a comment removed, write to privacy@thehood.markets quoting the market and roughly when you posted it. We do not commit to a fixed response time rather than promise one we have not staffed.

Be aware of the limit, because it is absolute: we can delete a server log entry. We cannot delete a blockchain record or an IPFS file, and neither can anyone else. No law, request or court order changes that — the data is replicated across machines nobody controls. Treat every on-chain action as published the moment you sign it.

Our lawful basis for the little we do process is legitimate interest: delivering the site and keeping it available.

9. Retention

• Server logs — kept only as long as they are useful for delivery and abuse prevention, and rotated by the hosting provider.
• Problem reports — 12 months from the day they are sent, or until the fault is closed and 12 months have passed, whichever is later. Deleted sooner on request; see section 3.5.
• Leaderboard exclusions — kept indefinitely, including after an exclusion has been lifted. The record is what an appeal is answered from, and deleting it would leave a wallet that was cleared with no evidence that it was. Section 4.
• Your account record — for as long as the account exists. Erasing it empties it; section 8.1 lists exactly what that reaches.
• Market comments — kept indefinitely, with the position snapshot stored alongside each one. They are public statements other people have read and replied around, and a record of what somebody held when they made a claim is worth nothing if it can be removed once the claim looks bad. Removed on request; section 8.1.
• Watchlist rows — until you un-star the thing, which deletes the row.
• Referral records — kept indefinitely, because they decide what somebody else is owed. Section 2.5.

We keep no other records of what you do here.

10. Children

The site is not intended for anyone under 18 and we do not knowingly process their data. If you believe a minor has used it, tell us at privacy@thehood.markets.

11. Changes to this notice

If this notice changes, the date at the top of the page changes with it. A change that introduced any tracking would also change the cookie notice and the notice on the site, before it took effect.

12. Contact

privacy@thehood.markets

The Hood’s contracts are immutable, audited by Claude Fable 5. Nothing on this site is financial, investment, legal or tax advice.