Privacy policy

[Company legal name] (“we”, “us”) runs QuantReplay and is responsible for the personal data it handles (the “controller”, in GDPR terms). This policy covers the website and the app.

QuantReplay runs on a server we operate, reached through Cloudflare. Everything described below as stored “on the server” is stored as files on it.

You sign in with Google or with your email and a password. From Google we receive your name, email address, profile picture and a stable account identifier. With a password we keep your email and the password only as a salted scrypt hash: we can’t read it. We keep these with the dates you signed up and last signed in, and we use your email for sign-up links, password resets and billing notices, sent through Cloudflare’s email service. Your bots, conversations, backtests, replay sessions, connected accounts and deployments are kept under your account, and other customers can’t see them.

Your plan is billed through Stripe. Your card details go to Stripe and never reach us. We keep your Stripe customer and subscription identifiers, your plan’s status, the trial and renewal dates and whether a payment failed, so the app knows your plan. Stripe’s privacy policy covers what Stripe holds. We also keep a daily total of what your Quinn use cost, to apply the daily allowance.

We only collect what you put into the service and what it needs to run. All of it is stored on the server unless noted.

What you create

• Bots: each bot’s name and description, its files (such as bot.py and its settings), and when it was created and changed.
• Conversations with Quinn: your messages, Quinn’s replies and progress notes, and the steps it took (the files it read or wrote, the code it ran and the results), stored exactly as they were exchanged with Anthropic.
• Backtests and runs: a record of every Python run (what ran, its output, how long it took), backtest settings, results and reports, and pass-odds results.
• Replay sessions: the symbol, timeframe and point in time, the simulated account, your orders and trades with any journal notes, drawings, indicators, layout and bot overlays.

Connected accounts and deployments

• Connection credentials: webhook URLs and tokens, custom webhook header values, Tradovate sign-in details (a username, password, client ID and API secret, or OAuth access tokens) and TopstepX API keys. They are encrypted before they are stored and are never shown back in full: the app displays a masked form, such as the last four characters.
• Account details: the label and firm you give an account, its connection type, account IDs and user names (stored unencrypted), and the result of the last connection test.
• Deployments: each deployment’s settings (bot, account, symbol, limits and alert choices, with the alert webhook URL encrypted), a frozen copy of the bot’s files, its state, an event log of orders, fills, guard decisions, alerts and errors, and the 1-minute bars it was fed.

Access and technical data

• The share password: when one is set, your browser sends it with every request. The server compares it with its setting and does not store or log it. Your browser may remember it until you close it.
• Logs: the server and the runner print operational logs (errors and deployment activity) on the computer that runs them. Messages from brokers and bridges are scrubbed of connection secrets before they are logged or stored.
• Network data: QuantReplay’s own code doesn’t record your IP address or browsing. Cloudflare, which delivers the shared link, processes your IP address and request details to do so.
• The live chart on our home page: when you scroll near it, your browser loads TradingView’s chart widget in a sandboxed frame from TradingView’s servers. From then on TradingView receives your IP address and browser details under its own privacy policy.

What we don’t collect

No names, email addresses, payment details, government IDs, location or contacts, and no analytics or advertising tracking. We’ll update this policy before accounts or billing add any of these.

• To provide the service: run your bots, backtests, simulations and replays, and keep your work between visits.
• To answer you through Quinn.
• To send your deployments’ orders and alerts where you direct them.
• To keep the service secure, find and fix problems, and prevent abuse.
• To comply with the law.

We don’t sell your data, use it for advertising, use your strategies to trade, or use your bots or conversations to train AI models.

If GDPR applies to you, our legal bases are: performing our contract with you (providing the service), our legitimate interests (security, preventing abuse and fixing problems), complying with legal obligations, and your consent where we ask for it.

Quinn runs on Anthropic’s Claude models through Anthropic’s API. When you chat with Quinn, we send Anthropic:

• Your message and the earlier messages of that conversation.
• A summary of the bot at the start of each turn: its name, its settings, its file list, and the headline results of its latest backtest and pass odds.
• The contents of files Quinn reads, and the output of code and backtests it runs.
• Your replay trades and their market context, when you ask Quinn to turn them into a bot.

Anthropic processes this to generate replies, as our service provider, under its commercial terms and privacy policy. [Counsel to confirm Anthropic’s current terms on training and retention, and our data processing agreement with it.]

Starting a new conversation deletes the stored conversation from the server. It doesn’t affect copies Anthropic keeps under its own retention policy. Don’t put personal information, passwords or API keys in chats or bot files.

When a deployment runs, the server sends data only to the route you chose for it:

• Order details: the contract, side, quantity, order type, prices, stop and target, our order ID and a short reason from your bot, together with the credentials that route needs.
• Native connections (Tradovate, TopstepX, experimental) also read your positions, open orders and fills to keep the deployment in sync.
• Alert webhooks you set up (Discord, Slack or similar) receive alert messages with the deployment’s name and what happened.
• Paper deployments send nothing outside the server.

Each provider handles that data under its own privacy policy. By default the server refuses to send webhooks to private or internal network addresses.

• Anthropic: your conversations with Quinn and the data above, to generate replies.
• Databento: only requests for market data (symbols and date ranges) made with our API key. No personal data about you.
• Your broker, bridge or webhook (Tradovate, ProjectX, TradersPost, PickMyTrade, custom webhooks): your orders and the credentials for that route, as described above.
• Alert services you configure: alert messages.
• Cloudflare: all traffic to the shared link passes through Cloudflare’s network.
• TradingView: your IP address and browser details, when its chart widget loads on our home page.
• [Hosting provider], if the service moves off our own computer, and [Payment processor], once paid plans launch, which would receive your payment details directly.
• Authorities, when the law requires it, or to protect our rights, users or the public.
• A buyer or successor, if our business is sold or merged, under this policy.

We don’t sell personal information or share it for cross-context behavioral advertising, as California law defines those terms.

QuantReplay sets one cookie, qy-theme, which remembers whether you chose the light, dark or system theme. It is first-party, lasts one year and holds nothing else.

Your browser’s local storage keeps interface preferences on your device: the theme, whether the sidebar is collapsed, Bot Studio’s layout (panel width, last tab, Quinn’s mode, the account chosen per bot), chart toolbar choices (favorite timeframes, drawing tools), replay account and settings, and how the deployments pages are arranged. These never leave your browser.

We set no analytics or advertising cookies. Cloudflare may set strictly necessary security cookies under its own policy, and TradingView’s chart widget on our home page may set its own cookies or storage inside its frame under TradingView’s policy. You can clear cookies and local storage in your browser at any time; the app then falls back to its defaults.

Nothing expires automatically yet. Data stays on the server until it is deleted:

• Bots, with their files, runs, reports and conversation: until the bot is deleted.
• A conversation with Quinn: until a new conversation is started or the bot is deleted.
• Replay sessions: until deleted.
• Connected accounts and their credentials: until the account is deleted.
• Deployments, with their frozen bot copy, event log and bars: until the stopped deployment is deleted. Deleting a bot doesn’t delete the copies its deployments keep.
• Logs on the server computer: [retention period to be decided].
• Backups: [backup policy to be decided].

Third parties keep what they receive under their own policies.

You can delete what you create in the app:

• Delete a bot to remove its files, runs, reports and conversation.
• Start a new conversation in Bot Studio to delete the current one.
• Delete a replay session, or a connected account (once no running deployment uses it).
• Delete a deployment once it is stopped, to remove its settings, bot copy, event log and bars.

Deletion is permanent and can’t be undone. To ask us to delete everything, or anything you can’t delete yourself, write to [Privacy contact email].

• Credentials are sealed with AES-256-GCM. The key comes from a server secret or a random key file that only the server’s user can read. The app stores a masked form beside each credential, so lists and screens never decrypt it, and the API never returns a credential in full.
• Each credential is sent only to the route it belongs to, and connection secrets are scrubbed from messages before they are logged.
• Bot code runs in a separate process. On Linux it runs without network access and with resource limits; on systems without those tools, such as macOS, the isolation is weaker.
• The shared link is served over HTTPS through Cloudflare and can require a password.

No system is completely secure. During the preview the service runs on a single computer, and anyone with access to its files and key could read stored credentials. Use API keys and webhook URLs you can revoke, and revoke them if you suspect a problem. If a breach affects your data, we’ll tell you as the law requires.

You can ask us to access, export, correct or delete your personal data, or to stop processing it. Bots are plain files, so we can give you a copy of everything you created. Write to [Privacy contact email]; we’ll verify the request and answer within the time the law sets (usually 30 to 45 days).

EEA and UK (GDPR)

You have the rights of access, rectification, erasure, restriction, data portability and objection, and you can withdraw consent at any time. You can also complain to your local data protection authority. [EU or UK representative, if required].

California and other US states

You have the right to know what we collect and how we use it, and to delete and correct it. We don’t sell or share personal information, so there is nothing to opt out of. Account credentials count as sensitive personal information; we use them only to provide the service. You can use an authorized agent, and we won’t treat you differently for using your rights. Residents of other states with privacy laws have similar rights.

QuantReplay is for adults (18 or older) and isn’t directed at children. We don’t knowingly collect children’s data. If you think a child has given us personal data, write to [Privacy contact email] and we’ll delete it.

The server is located in [country where the server runs]. Anthropic, Cloudflare, Databento, TradingView and the brokers and bridges you use may process data in the United States and other countries. Where the law requires it, we rely on safeguards such as the European Commission’s standard contractual clauses for those transfers. [Counsel to confirm the transfer mechanism.]

We’ll update this policy as QuantReplay changes, in particular before user accounts or billing launch. We’ll change the date at the top and, for material changes, tell you in the app or by email (once accounts exist) before they take effect. Our terms of service (draft) cover the rest of how the service works.

[Company legal name], [Registered address]. Email: [Contact email].

Privacy requests: [Privacy contact email].