Privacy
What Crossbook stores, where it stores it, and what it does not collect.
Written for a prototype. It is a plain description of how this build behaves, not a lawyer-drafted agreement, and it makes no jurisdiction-specific claims. This page reflects the build published in August 2026.
Summary
There is no account system and no backend that records what you do. Everything the interface remembers is stored in your own browser and stays there.
What is stored locally
The prototype writes to localStorage under keys namespaced to the product — currently a demo account (balances, orders, fills, activity), a wallet display state, and interface preferences such as chart timeframe and book grouping.
You can remove all of it at any time: Portfolio → Reset demo account, or clearing site data in your browser.
What is not collected
No name, email address or payment detail is requested, because there is nothing to sign up for. No private keys, seed phrases or signatures are read, requested or stored. No trading behaviour is sent anywhere, because orders are matched locally.
Wallet addresses
If you connect a browser wallet, its address may be read on your explicit action so it can be displayed in the header. It is kept in local storage for that purpose only, is not transmitted anywhere, and no signature or transaction is ever requested. See Security.
Third parties
Web fonts are served with the application. Where the prototype is hosted, the host may keep standard server logs (such as IP address and user agent) as part of serving the page; that is outside the application and is not linked to any account here.
Changes
If a future build introduces anything that changes the answers above — analytics, an account system, a server-side order record — this page would say so before that build ships.