Privacy

What we store, what it is used for, how long it is kept, and how to delete it. This page is written against the fields that actually exist in the code, not from a template.

Effective 2026-09-03

What we store

field by field, as in the database

Email address: Comes from GitHub / Google and is used to confirm that you are the same account as last time; one email can have only one account. We send no marketing email — the site sends no automated email at all. Your address is not public and never appears on the board or on your profile.
Display name and avatar URL: The display name and avatar URL from your third-party profile, used on the board, in the Trade Feed and on your public profile.
Third-party account ID and its creation date: The former is the sign-in credential itself (re-linking relies on it); the latter is used only for the anti-farming gate — a third-party account must be at least 30 days old. The only scopes requested on the GitHub side are read:user and user:email (public profile and email); no repository access and no private data.
Data produced on the site: Your handle, $HYPE balance, positions, fills, claim streak, plus the risk score and restriction flag used against farming. All of it hangs off an internal account ID and is stored separately from your email.
Session: One session cookie (HttpOnly, Secure, SameSite=Lax), valid for 30 days. The server-side session record carries the IP and User-Agent seen at sign-in — necessary signals for spotting bulk registration, not used to analyse your behaviour.
OAuth tokens: The access / refresh tokens returned by the provider at sign-in are stored server-side and used only to complete sign-in itself. We never act on your behalf with them, and we request no write scopes.
Delist / report requests: The ticker submitted at /delist, the contact email you enter, and the (optional) reason. This is one of two places where data reaches us from someone who need not have an account — the address is used to answer this one thing, and the reason text is seen only by whoever handles the request.
Ad bookings: The headline, one-liner and landing page submitted at /ads, a contact email, and our own order number. That is the second such place. The first three are published on the board — they are what the 30 days buy — and the address is used only to reach the buyer about that one booking. We never see your card: the payment happens entirely inside Waffo (below), and what comes back to us is a paid / not-paid flag plus an order id.

What it is used for

these three things only

To sign you in, and to let the board know whose row that is.
Anti-farming: the per-product daily cap, the distinct-holder threshold for the top ten, and a once-daily clustering sweep (over account age, IP, User-Agent and position shape). The rules are spelled out in Rules.
Reconciliation: the site-wide ledger has to balance every day (issued = sum of all accounts + sum of all market reserves + burned), which is why fills cannot be deleted.
That is all. No profiling, no targeted advertising, no selling data, and no handing your data to any third party beyond the infrastructure listed below. The site does sell ad rows (see Advertise), and everybody is shown the same ones: nothing you do here decides which ad appears, because none of your data ever reaches an advertiser. What an advertiser gets back is a click count.

Third parties

Cloudflare — the whole site runs on Cloudflare (Workers, D1, Durable Objects, KV), so every request you make necessarily passes through it.
Cloudflare Turnstile — the sign-in, listing, delist and advertise pages load a Cloudflare human-check script, which sees your IP. That is how it works; it sets no cross-site tracking cookie.
Waffo — reached only if you book an ad. It is the merchant of record for that payment, so the card details, billing address and tax handling all live on its side and never touch this site. No other page loads anything from it.
Beyond those, no third-party tracking scripts at all: no ad SDK, no analytics SDK, no social plugins. Paid rows are rendered by this site like every other row, so an ad here loads nothing from an ad network — a click is counted by our own redirect, and nothing besides the click is counted.
The site has exactly one session cookie and no tracking cookies — which is why you will not see a cookie consent banner here.

Retention · deletion

Session: Expires automatically after 30 days. Signing out invalidates it immediately.
Account and ledger: Kept for as long as the account exists. After deletion it is anonymised as described below.
Fills: Kept forever — the reconciliation identity is recomputed daily, and dropping a single fill would leave the site-wide ledger permanently off. After account deletion, though, those fills no longer map back to you.
Deleting your account: Write to support@saasdaq.net from the address you signed in with. We delete the email, display name, avatar and OAuth tokens, replace the handle with an anonymous identifier, and liquidate the positions; the fills stay behind in anonymised form.
This is currently a manual process — there is no self-service delete button yet. Rather than ship a button that punches a hole in the ledger, we would rather say so plainly.
Delisting a product: A product's owner (who need not be a user here, and need not sign in) can submit a removal request at /delist, handled unconditionally within 24 hours, no reason asked. The request itself is kept as a record that someone asked and that we acted.
Ad bookings: The booking row, its order number and the per-day click counts are kept after the 30 days end: they are the record of a payment, and an invoice we cannot reconstruct later is a problem for both sides. Display stops the moment the term does — nothing needs to be deleted for the row to disappear.