One value is written
to your browser. That is all.

This is a static site. It consists of hand-written HTML documents, one stylesheet and a small set of plain JavaScript files, served as files. There is no application server, no database, no session, no account system and no logging endpoint belonging to this project. Nothing you do here is observed by it.

That statement is unusual enough that it should not be taken on trust, so it is worth saying how to verify it. Open your browser's developer tools, select the network panel, and reload any page in this facility. The request list will contain documents and assets from this site's own origin and nothing else — no analytics beacon, no font host, no tag manager, no pixel, no third-party anything. Then disconnect from the network and continue using the site: every instrument keeps working, because every calculation happens in your browser.

The absence is deliberate and it is structural rather than a matter of restraint. There is nowhere for data to go, because nothing was built to receive it.

Two forms exist in this facility: the enquiry form on the contact record and the development register on the early-access record. Both behave identically with respect to your data.

When you submit, a script running in your browser checks that the required fields are present, that the email field has a plausible structure, and that the message meets its minimum length. It marks any failing field as invalid, writes an error message into the text slot beneath it, and moves focus to the first problem. If everything passes, it displays a confirmation with a locally generated reference number and clears the form.

At no point is a network request made. There is no endpoint, no email relay, no form service, no webhook and no storage. The reference number is generated from your own clock and is recorded nowhere — it is a demonstration of the intended intake behaviour, not a receipt. When you navigate away or reload, everything you typed is gone.

Both forms state this at the point of use, in a panel adjacent to the fields, rather than only here. You should still avoid entering anything sensitive, on the general principle that a form which does nothing is a strange place to put information you care about.

Most legal frameworks classify special categories of personal data — health, biometrics, political opinion — and trading records are not among them. That is a description of the law rather than of the risk, and the two diverge here.

A complete trade history discloses, in aggregate, your account size and its trajectory, your income from the activity, your risk appetite, the hours you work, the instruments and brokers you use, your methodology in reconstructible detail, and the periods during which you were losing. Taken together that is a financial and behavioural profile of unusual precision, and it is precisely the kind of dataset whose commercial value creates pressure to use it for something other than what the person uploading it intended.

The intended position is therefore stricter than the law requires: uploaded trading data is treated as confidential to the account that uploaded it, used only to produce that account's analysis, and never aggregated into anything published or shared. A published statistic derived from users' trade records — however anonymised — would be a breach of that principle even where it would be lawful, and the intent is not to produce one.