Privacy

What is stored about you

Your account: name, email address, a hashed password, when the account was created, and whether it is an administrator or disabled. Sessions are stored so you stay signed in.

Your workspace: the strategies, files, datasets, backtests, charts, analyses and agent conversations you create. These are stored until you delete them or the account is removed.

Your spending: one row for every model call made on your behalf, holding the time, the model, the token counts and the cost in US dollars, plus a record of every change an administrator makes to your allowance and why. This is how the credit system works and it is kept for accounting.

What is sent to a model provider

The agent runs on a third-party language model. To answer a turn, your messages, the relevant contents of your workspace, and the results of the tools it calls are sent to that provider over an encrypted connection.

That means your strategy code and your questions leave this server. If you have code you cannot share with a third party, do not put it in a workspace.

What is not sent anywhere

Strategy and analysis code runs in a container with no network access at all. It cannot reach this server, the internet, or anything else on the machine. The code and the price data arrive on standard input and the result leaves on standard output.

Passwords are never stored in a form anybody can read, including the operator.

Analytics

If whoever operates this deployment has switched product analytics on, the browser records which screens are opened and which actions are taken, so that the product can be improved. Content is deliberately excluded: file contents, prompts, model answers and workspace names do not leave the browser in an analytics event.

Analytics keeps nothing on your device: no analytics cookie is set and nothing is written to local storage, so the identifier lasts as long as the tab does. Session recording and autocapture are off, not merely masked, and a Do Not Track header is honoured.

If analytics is switched off, which is the default, nothing is collected and no third-party analytics code is loaded at all.

Cookies

One cookie, for your session, so that you stay signed in between requests. It is set by this server, marked HttpOnly so page scripts cannot read it, and marked Secure when the service is served over HTTPS.

That is the only cookie. There are no advertising or analytics cookies and no advertising trackers, which is why this service asks you to accept nothing.

Who can see your work

Members of your workspace, according to their role. An administrator of this deployment can see accounts, what they have spent and their allowances, and can raise an allowance, set a password, disable an account or delete one. Administrators have no route into the contents of your workspace.

Whoever runs the server has access to the database it is stored in, as is true of any hosted software.

Your choices

You can delete strategies, datasets, backtests, analyses and conversations from inside the workspace at any time. A record of what a deleted conversation cost survives it, because the accounting has to add up; it no longer names the conversation.

To have your account deleted, or to ask what is held about you, write to whoever operates this deployment. Deleting an account removes it along with its workspaces and everything in them, its sessions, its settings, and its spending history, and a workspace shared with somebody else is left with them rather than removed.

Security

Sessions are signed, opaque and stored server-side so they can be revoked. Requests are checked against the host and origin they claim to come from. Sign-in and sign-up are rate limited. Model-written code is contained as described above.

No system is perfectly secure. If you find a vulnerability, please report it to whoever operates this deployment rather than demonstrating it against other people's accounts.

Who operates this

This deployment has not named an operator. It is running from the Atlantive source with the operator identity left unset, which means these pages describe the software rather than a service anybody is offering you.

If you were given access to this by someone, they are the operator, and questions go to them.