What Tradeus stores in your browser

No cookies of ours, one pixel that only runs if you accept it — and the list of what is there.

Tradeus writes no cookies of its own and uses no analytics service and no session replay. There is one advertising pixel, from Whop, who sell the subscription — it tells them that a sales page was opened, so an advertisement we paid for can be matched to a sale. It does not load unless you accept it on the banner, and it never loads on the pages behind your sign-in. From 29 October 2026 that changes outside the EU/EEA, the United Kingdom, Switzerland and Canada: there it will run by default, and every public page will carry a link to switch it off — the privacy policy announces it in full. If you came from one of our Google ads, the click identifier Google put on the link is kept in the tab too; once you have an account it is kept with it for 90 days. Google Ads is told whether the click became an account or a trial, and no script of Google's runs on the site.

Declining is the same size button as accepting, in the same colour, and the site is identical either way — nothing is withheld, nothing is nagged. Ignoring the question is also a no. If your browser sends a Global Privacy Control signal you are not asked at all, because you have already answered.

What the banner asks for is more than a page count, and it says so. Along with the visit, Whop's script sends a fingerprint of your browser — a hash of screen size, time zone, language, fonts and the way text and graphics are drawn — which is how it recognises a visit when cookies are refused. That one cannot be switched off from our side. Five other things it can do by default can be, and are: reading the fields of any form on the page, taking a name or an email out of the link you followed, rewriting outbound links, timing how long you stay, and measuring your graphics hardware. The cookies page lists what is left, row by row.

What is kept in your browser's own storage is your sign-in token, a cached copy of your own account so the app opens without a splash screen, the result of a broker login while you are being redirected back from it, and — if you arrived on somebody's referral or discount link — the code from that link, until you close the tab. If you followed one of our own links, the label of that link is kept too, and if you picked a plan before signing in, which one — so the checkout opens on it when you are back, for at most half an hour. Those last ones go when the tab closes; the sign-in token and the cached account stay until you sign out. If you use the Pass Simulator, the rules you typed into it are kept as well, so the form is filled in when you come back — those stay after you sign out, until you clear them on the cookies page.

Five tallies are kept on our side and none of them is about you: how many visits arrived on a given campaign link, how many from a given country, how many from a given website, how many times each page was read, and how many visitors got as far as the prices (and had them on screen), the sign-in and the choice of Google or Discord — and, where the pixel question is asked, how many answered it yes and how many no. They are counters, not records — no row per visitor, no identifier, no address, nothing finer than the date, and nothing can follow you from one page to the next. On a quiet day a count of one can still be one person, so they are treated with the same care as everything else we hold. The country is read from the network by our hosting provider and never taken from your device, and a referring website is cut down to its name before it is counted, so the page you were on and anything you searched for are discarded rather than stored. These counters skip a browser that is signed in on the page it is reading, and anything from a test copy of the site. Two things are kept with your account instead: the label of our own link you arrived on, if any, and — when you open the checkout — each step of it with its time (opened, the withdrawal box, Whop's form shown, a payment error's short code, Whop's own page opened instead, completed, or back out), so a purchase that got stuck can be found and fixed — and when an account is created or a checkout is opened, fails or completes, we are told in a private channel of our own with the account's number and the plan, never a name or an address. Those steps are deleted after 180 days, or with the account.

One thing leaves your browser without being stored anywhere: the live connection that delivers positions and fills without polling. Your sign-in token is sent once when it opens, in the handshake rather than in the connection's address — addresses are what servers and the networks between them write into their logs, and a token that stays valid for months does not belong there.

The checkout is the exception, because it is not ours: when you open it, Whop's checkout script runs on this page and keeps its own entries here — two cookies and a device identifier for its fraud checks. Every entry is listed individually — what it is for, how long it lasts, the exact name it has in your browser's developer tools so you can check us, and a button that deletes all of them — on Cookies and local storage. That page also sets out exactly which single thing a consent banner is asked for, and why nothing else here needs one.

Also in Everyday use