Privacy
What we hold, why, and for how long.
What we collect
Your email address and, if you give it, your name. A hash of your password — never the password itself. Your account numbers, broker server names, and the settings of each pipeline. The trading activity the engine copied for you, with its timings. Sign-in records: time, IP address and browser string, kept so you can spot a session you do not recognise.
Your broker password
It is encrypted in the same request that receives it, to a public key belonging to the engine machine that will run your terminal. Only that machine holds the matching private key. This website stores the sealed result and contains no code capable of opening it, so no employee, no support agent, no administrator and no copy of this database can read it back.
Why we hold it
To provide the service you asked for, to keep your account secure, to detect abuse, and to meet accounting and legal obligations. We do not sell personal data and we do not use it for advertising.
Cookies
One session cookie, so you stay signed in, and a short-lived cookie during two-factor setup. Both are strictly necessary for the site to work. There is no analytics, tracking or advertising cookie on this site, which is also why you are not being asked to accept anything.
Who else sees it
Our hosting provider stores the data at rest. Our email provider sees the address we send to and the content of that message. Payment, if you are on a paid plan, is handled by the payment processor, which sees what it needs to take the payment; we do not store card numbers.
How long
Trading events and balance history are pruned on the retention period set for this installation. Security and audit records are kept longer, because their whole value is being able to look back. When you close your account, personal data is removed on the schedule above except where an invoice or a legal obligation requires it to stay.
Your rights
You can ask for a copy of what we hold, correct it, or have it deleted. Closing your account from the Security page starts the deletion path yourself. For anything else, write to us.
Security
Passwords are hashed with a modern memory-hard function. Sessions live in the database and can be revoked from any device. Two-factor authentication is available and is required before any broker credential is accepted. Administrative actions are written to an append-only log.