Privacy

What is stored about you

This is the complete list, not a summary of a longer one. Most of it is visible on the linked account pages. The password hash can never be displayed; public test-network addresses appear only when those optional rails are configured and used. That specificity is what makes this page useful: you should not have to guess what is stored.

• Your email address

  Lower-cased. The only thing the sign-up form asks for besides a password.

  It identifies the account and it is how you sign in.

  Where you can see it: Settings

• Your password, as a hash

  A salted scrypt hash and its cost parameters. Never the password.

  To check a sign-in without being able to read what you typed.

  Where you can see it: Nowhere — it cannot be displayed

• The date the account was created

  One timestamp, written once.

  It is the only thing that answers “how long has this account existed”.

  Where you can see it: Settings

• Three wallets

  Spot and futures from sign-up, funding the first time something needs it. Internal identifiers, not blockchain addresses.

  Every balance, order and position is keyed to one of them.

  Where you can see it: Settings

• Ledger entries

  Every movement of simulated money, as signed amounts against a wallet: deposits, trade settlement, fees, reservations, funding, liquidations.

  A balance here is the sum of these entries. There is no stored balance to read instead.

  Where you can see it: Assets

• Orders

  Market, side, type, price, size, leverage, time in force, status, what the order reserved — and a dated entry for every status change it went through.

  To work the order, to show you what happened to it, and to release exactly what was reserved.

  Where you can see it: Orders

• Fills

  Price, quantity, fee and fee asset for each fill of each order.

  A fill is the record of the money actually moving. It is what a fee is charged on.

  Where you can see it: Orders → Fills

• Perpetual positions

  Symbol, side, size, entry price, leverage, margin posted, realised profit and loss — and a dated entry per change: opened, increased, reduced, closed, funded, liquidated.

  A position outlives the orders that built it, and funding and liquidation act on it directly.

  Where you can see it: The futures terminal

• Transfers and conversions

  Wallet-to-wallet transfers and spot conversions: the assets, the amount, the executed rate and the fee.

  So a receipt can never drift from what actually settled, and a double submission cannot run twice.

  Where you can see it: Assets

• Referral attribution and reward receipts

  Your stable referral code; an immutable inviter-to-invitee edge when a valid code was accepted at signup; and the campaign, evidence reference, amount and ledger transfer for each reward claimed.

  To stop attribution being reassigned, compute progress from settled activity, and prove that one campaign paid one account only once.

  Where you can see it: Rewards

• Watchlists, price alerts and notification preferences

  Starred spot and perpetual markets; alert symbol, direction, target and trigger state; and whether order updates, price-alert toasts and sounds are enabled.

  So these choices follow the signed-in account across browsers. Alerts are evaluated only while a binXbase tab is open.

  Where you can see it: Price alerts and market watchlists

• Test-network deposit and withdrawal addresses, when used

  A configured public deposit address can be assigned to the account, and a withdrawal request stores the public destination you enter. Private keys and recovery phrases are never collected or displayed.

  To attribute an incoming testnet deposit or send an enabled testnet payout to the requested destination.

  Where you can see it: Deposit and withdrawal history

Your password

Your password is stored only as a salted scrypt hash — a one-way derivation, deliberately slow to compute, with a random salt per account. The password itself is never written down, and nothing in this system can read it back or show it to you. Signing in re-derives the hash from what you typed and compares the two.

The practical consequence, said plainly rather than left implied: there is no password reset, because there is no way to send you an email. If you lose the password, the account is unreachable and the only route is a new one. Do not reuse a password you use anywhere else — this account holds nothing of value, but a reused password makes it a key to somewhere that does.

There is also no sign-in with Google, Apple or anyone else. Only the email-and-password form exists, so no third-party identity is ever linked to an account here and no identity provider is told you have one.

Cookies, and what your browser keeps

Reading this site sets no cookies. Not the home page, not a market, not a terminal, not this page. No cookie is written at all until you use the sign-in form, and what is written then is three, every one of them set by this site for its own use. None is a third-party cookie, none identifies you anywhere else, and none can be read by JavaScript on the page.

• Session token

  A signed token that says which account you are. It is what keeps you signed in from page to page.

  Lasts: Thirty days, renewed while you keep using the site — so an abandoned session expires thirty days after your last visit, not thirty days after sign-in.

• Request-forgery token

  A one-time value the sign-in and sign-out forms carry, so another site cannot make your browser sign you in or out behind your back.

  Lasts: Until you close the browser.

• Return-to address

  Remembers which page to send you back to after signing in.

  Lasts: Until you close the browser.

There is no advertising cookie, no analytics cookie and no consent management platform, which is why this site has no cookie banner. A banner would be asking your permission for something that does not happen.

What also stays in your browser

These are local-storage records, not cookies, so the browser does not attach them automatically to every request. The application can read them: some are browser-only conveniences, while signed-in workspace choices are an offline cache of data also stored with your account.

• Workspace cache and pending offline changes. Signed-in watchlists, price alerts and notification preferences are cached under that account’s identifier. A change made during an outage waits there and is sent when connectivity returns. Signed-out stars stay in a separate guest set and merge into the account after sign-in.

• The notification history behind the bell. Up to fifty recent events, each one a copy of something that already happened in your account. This browser-only history is keyed to the confirmed account, so another account using the same browser does not inherit it; notices raised while signed out stay only in the current tab. The authoritative record is your order history; this is a convenience sitting on top of it.

• Getting-started dismissal. Whether the account’s checklist was hidden on this device. The key includes the account identifier, so one person hiding it does not hide it for the next account using the same browser.

Clearing site data removes these local copies. After the next sign-in, account-synchronized watchlists, alerts and preferences are restored from the server; browser-only notification history, guest stars and checklist dismissal are not.

What is deliberately not collected

This is the strongest section on the page, and it is the one most worth checking. Each line is an absence that was verified in the product rather than assumed — the difference matters, because an unverified absence is just a promise.

• No analytics, of any kind. There is no page-view counter, no product analytics library, no heatmap and no session recording. Not a self-hosted one either. Nobody, including us, is counting your visits.

• No advertising and no tracking pixels. No ad network, no conversion tracking, no cross-site identifier, no beacon. Nothing on this site reports your visit anywhere.

• No fingerprinting. Nothing probes your fonts, canvas, audio stack or hardware to build an identifier out of your browser.

• No application profile built from your IP address or user agent. Product records do not store either value and no product feature is keyed to location or device fingerprint. Account-scoped safety limits do exist, but they use account or action identifiers rather than an IP profile.

• No location, contacts, camera, microphone or browser-push permission. The site does not call the browser Notification API and asks for no device permission. Notifications are in-app bell entries and toasts while the site is open; optional sound cues are synthesised locally. There is no background push, SMS or email delivery worker.

• No third-party asset ever loads in your browser. Typefaces, asset logos, icons, scripts and styles are all served from this site. Your browser is never asked to fetch a file from another company while you use it, so no other company sees you here.

• No email is ever sent to you. There is no mailing list, no marketing mail, no notification mail and no password-reset mail, because the product has no way to send mail at all.

• No identity documents or payment-card details. No identity check exists and no identity document is collected; no card or bank details exist because nothing takes fiat payment. Public blockchain addresses are handled only when you use the configured test-network deposit or withdrawal flows.

One honest caveat rather than a silent omission: any web server on the public internet — including whatever one is serving you this page — can keep an ordinary access log of the requests it receives. That is a property of how the web works and sits outside this application, which neither writes such a log nor reads one. Everything above describes the product itself.

Where data goes

Your account data is not sold, shared, syndicated or handed to a processor. There is no partner, no affiliate and no analytics vendor to hand it to.

Data does flow the other way, though, and a policy that did not name those flows would be hiding the interesting part. Four outside services make this product work. In every case this system makes the request, not your browser, and in every case the request carries nothing that identifies you — no email address, no account, no cookie, and not your IP address, because the connection is not yours.

The AI commentary, precisely

This is the one flow worth spelling out in full, because it is the only one a person sets off deliberately and the only one where the question “what did it send about me?” has a non-obvious answer.

When you press the button on the AI desk, your browser sends this site exactly one thing: the symbol you chose from the list. There is no free-text box on that page, so there is nothing else you could have typed.

This system then reads the same live figures the charts are already showing — the pair, the last price, the 24-hour open, high, low, change and quote volume, and up to 120 recent hourly candles as open, high, low, close and volume with UTC timestamps — and sends those, with the writing instructions the model is given, to Anthropic’s API. That is the entire request. No email address, no account identifier, no balance, no order, no position, no cookie and not your IP address goes with it, and your browser never talks to Anthropic directly: the reply streams back through this site.

The commentary itself is not stored. It exists in the panel you are looking at and is gone when you reload. If the deployment has no key configured, the feature reports that it is switched off and nothing is sent anywhere at all.

Links that leave the site

A market page can link out to a project’s own website or a block explorer. Those are ordinary links you choose to follow, and they are marked so that your browser sends no referrer — the destination is not told you arrived from here. Where you go after you leave is between you and them.

How long it stays

Nothing expires and nothing is deleted on a schedule. There is no job anywhere that removes an old order, a fill, a position or a ledger entry. That is a design decision rather than an oversight: the trading record is append-only, because a record of money that can be quietly rewritten afterwards is not a record.

So an account and its financial record stay for as long as this service runs. Alerts and watchlist rows remain until you delete or unstar them; notification preferences remain until you change them. Two other retention boundaries are visible to you:

• Your session. The signed-in token stops working thirty days after your last visit, on its own. Signing out clears it immediately in that browser.

• Anything your browser keeps. Offline account caches, guest stars, per-account notification history, the sound mirror and checklist dismissal last until you clear this site’s browser data. Account changes hide another account’s local notification history but do not erase its browser copy. Clearing site data does not delete the signed-in account’s server copy of watchlists, alerts or preferences.

What you can do about it today

Only the controls that exist are listed here. Where a right you would normally expect has no mechanism, it is named as missing rather than described as a process — a policy that promises a procedure nobody built is the worst thing this page could contain.

What does not exist

• Self-service deletion. There is no button that deletes an account, and signing out is not deletion. The trading record is deliberately built so entries cannot be removed in place, so erasing an account is a manual operation on the database — not a feature, and not something this page will pretend takes thirty days.

• Changing your email or resetting a forgotten password. Email changes do not exist because there is no verification-email channel. A signed-in user can change their password in Settings only after proving the current password; forgotten-password reset still does not exist.

• A formal access or portability request. There is nowhere to send one — no support address exists. The CSV export above and the pages listed with it are the whole of what can be handed to you, and they are already in your hands.

• A support desk. No inbox, no ticket queue, no chat. There is nowhere to write.

Which leaves one piece of practical advice, and it is the honest one: sign up with an address you are content to leave in a database indefinitely, use a password you use nowhere else, and treat the account as disposable. It holds no money and custodies nothing, so walking away from it costs you exactly nothing.

Who you are dealing with

binXbase — a crypto exchange and Web3-AI company, founded in 2026, serving a global audience. binXbase does not hold an exchange licence and is not supervised by a financial regulator, and nothing on this site is a regulated service. There is also no data protection officer, no support address and no self-service deletion — each of those absences is named in the sections above rather than dressed up as a process.

That has a consequence for this page that ought to be stated rather than buried. The rights a privacy policy usually recites — a formal request for access, a right to erasure, portability, a complaint to a supervisory authority — are exercised through published particulars: a controller’s registered details, an officer to write to, an authority named on the page. Those particulars are not published here yet, and this page will not imply a procedure nobody has built. When they can be stated in full, they will appear here rather than being hinted at.

The compensation this page is built on stands either way: hold almost nothing, and describe exactly what that “almost nothing” is. Decide what you put here on that basis. The terms say the matching thing about what the service is and what it is not, and how it works shows the mechanics.

Changes to this page

This page describes what the software does today, and it is written from the code rather than from a template. If the behaviour changes — a new outside service, a new stored field, a cookie that does something else, an analytics library — this page changes with it and the date at the top moves. The version on this page is always the current one.

There is no notification when it changes, because there is no mailing list to notify you on, and this page is not going to invent one.