Privacy policy

Who we are

Traderunner operates Traderunner and is the controller of the personal data described here. You can reach us at support@traderunner.dev.

What we collect

Only what the product needs to work. There is no advertising, no data broker, and no third-party analytics anywhere in this application.

• Your email address — to create the account, to send the link you sign in with, and to send you notices about your account and your agents. There is no password, so we never hold one.
• What you build — agents, workflows, tools, skills, and the settings and limits attached to them, including anything you type into the composer or an agent’s chat.
• What your agents did — run transcripts, orders, fills, positions and portfolio history, including the reasoning a model produced for a decision.
• Brokerage credentials — only if you connect a brokerage. Encrypted at rest; see the section on brokerage credentials.
• Billing details — if you subscribe: your billing address, and a record of what you bought. Your card goes to Stripe and we never see it.
• Records of consent — when you accepted these documents, which version, and when you acknowledged the risk of going live.
• Basic technical data — the ordinary request information a web server and a database receive in order to respond, including IP address, browser, and the time of the request.

How we use it, and on what basis

To run the product: to wake your agents, evaluate your conditions, place the orders you authorised, show you what happened, and meter your usage against your plan. Basis: performing our contract with you.

To bill you, keep accounts, and meet tax and record-keeping obligations. Basis: our contract, and our legal obligations.

To keep the Service working and safe: to debug failures, prevent abuse, enforce limits, and protect other users and ourselves. Basis: our legitimate interest in running a service that works and is not misused.

To contact you about your account, your agents, and changes to the Service or to these documents. Basis: our contract. We do not send marketing email you did not ask for, and if we ever do, you can stop it with one click.

Where the law requires consent for something, we ask for it, and you can withdraw it.

What we never do

• We do not sell your data, and we do not share it with advertisers or data brokers. Under US state privacy laws, we do not "sell" or "share" personal information and we do not use it for targeted advertising.
• We do not use your agents, transcripts, positions or performance to train models, ours or anyone else's.
• We do not put analytics or advertising trackers in the application.
• We do not read your data to trade alongside you, and we do not look at your account to see whether what you built is a good idea.
• We do not make decisions about you by automated means that have legal or similarly significant effects on you. Your agents make decisions about your trades because you told them to; that is your automation, not ours.

Where models come into it

When a judgement step runs, the content of that step, your instructions, the market context it was given, and any skill attached to it, is sent to the model you chose for that step.

Every model request goes through OpenRouter, which routes it to the provider that serves that model and returns the answer. The provider receives the contents of that request.

We do not send your brokerage credentials, your balances, or your account identity to any model provider. A model never sees a credential: agents call named tools, and the platform executes those tools server-side.

Model providers have their own terms and retention policies for requests routed to them. Choosing a model is choosing whose policy applies to that step.

Brokerage credentials

If you connect a brokerage, the tokens are encrypted at rest with AES-256-GCM. The key is held as a platform secret, not in the database and not in the repository, so a copy of the database is not a copy of your access.

The tokens are used only to place and reconcile the orders your agents make. No model and no prompt ever sees them, and they never travel with anything you publish. You can revoke them at any time from the Service or from your brokerage.

Who else receives data

Traderunner uses the following services to operate Traderunner. Each receives only what its function requires, under a contract that limits what it may do with it.

• Supabase — Database, authentication and file storage, in the United States. Holds your account, agents, portfolios, fills and run history.
• Vercel — Hosting and delivery for the web application.
• Cloudflare — Runs the execution engine that wakes agents and places orders.
• OpenRouter — Routes every model request to the provider you chose for that step, and returns the answer.
• Model providers — Anthropic, OpenAI, Google, xAI, Perplexity, DeepSeek, Z.ai and Qwen receive the contents of a judgement step when that step runs on their model, via OpenRouter.
• Resend — Sends the emails we send you: the sign-in link, and notices about your account and your agents.
• Stripe — Processes payments. Receives your email, your billing address and your card; we never see the card.
• Yahoo Finance — Market quotes and historical bars. Receives the ticker symbols your agents look at, never your identity.
• Robinhood — Executes live orders, when you have connected a brokerage account and switched an agent to live.

We will disclose data if the law requires it, to a regulator or court with authority to ask, or where we reasonably believe it is necessary to protect the Service, our users, or ourselves. If we are acquired, your data may move to the acquirer under this policy.

Where it is stored, and international transfers

The Service is operated from the United States and your data is stored there. If you use it from outside the United States, including from the European Economic Area, the United Kingdom or Switzerland, your data is transferred to the United States and to the countries where our suppliers operate.

Where the law requires a legal mechanism for that transfer, we rely on the European Commission’s Standard Contractual Clauses, the UK Addendum to them, or an adequacy decision, as applicable, together with the technical measures described here. Write to us for a copy of the clauses.

Your account is separate from everyone else’s

Every row of every table is scoped to your user and enforced by row-level security in the database itself, rather than by a check in application code that a bug could skip. Another account cannot read your agents, positions or history.

Nothing you build is visible to anyone until you publish it. Publishing shares the workflow and the record it has built, never your credentials, your book, or your balances.

Cookies

First-party and functional only. There is no consent banner because there is nothing to consent to: no advertising cookies, no cross-site tracking, and no analytics package.

• Session — Keeps you signed in after you follow the link in your email. Set by Supabase authentication.
• tw-theme — Remembers whether you chose light, dark, or system.
• tw-book — Remembers which portfolio you were last looking at.

How long it is kept

Account data, agents and trading history are kept while your account is open, because a track record with holes in it is not a track record.

Run transcripts are kept while your account is open so a decision can be audited after the fact.

When you close your account, from Settings or by writing to us, we stop every agent and revoke every brokerage connection immediately, and we delete your personal data within 30 days, except what we must keep for tax, accounting, fraud-prevention or legal reasons, which we keep only as long as that reason requires, and except anything you published that other people have already copied, which remains in their accounts as their copy.

Records of consent and billing are kept for as long as the law requires us to keep them.

Your rights

Wherever you live, you can ask us to tell you what personal data we hold about you, correct it, give you a copy of it in a portable form, delete it, restrict or object to how we use it, and withdraw any consent you gave. You can export your data and close your account from Settings, or write to us and we will act within the time the applicable law allows, and in any case within 30 days.

If you are in the European Economic Area, the United Kingdom or Switzerland, you also have the right to complain to your data-protection authority. We would rather you wrote to us first.

If you are in a US state with a privacy law, you have the rights that law gives you, including the right not to be discriminated against for exercising them, and, where the law provides it, the right to appeal a decision we make about a request by writing to us.

We may need to verify your identity before acting on a request; we will do that by sending a link to the email on your account.

Children

Traderunner is not for anyone under 18, and we do not knowingly collect data from children. If you believe a child has created an account, tell us and we will remove it.

Security

Data is encrypted in transit and at rest. Brokerage credentials and tool secrets are encrypted separately with a key held outside the database. Access is scoped per user at the database level. No system is perfectly secure, and we do not promise this one is; if we learn of a breach affecting you, we will tell you and any regulator the law requires, without undue delay.

Changes

We may update this policy. The effective date at the top always reflects the current version, and we will give notice of a material change before it takes effect. The current version is 3.