Security & privacy
Your strategy stays yours.
TrainBard is built so the strategies you test and the results you generate stay close to you. This page describes what that means in practice.
Data flow
How a backtest moves through TrainBard.
When you run a batch, the script and its inputs go to the engine, the engine runs the combinations, and results stream back to your browser. The session ends when you close the tab.
No cloud result history. Your scripts stay in your browser.
What we don't store
Not kept on our side.
TrainBard does not store your Pine Script code or retain a cloud history of your batch results. Your strategies are not saved after a session ends.
- Your scripts are not persisted after the session
- No persistent batch result history
- No retention of result tables for later browsing
- No sharing surface for other users to discover your strategies
What stays local
Yours to keep.
You can export the work that matters to you. CSV, JSON, and image exports are produced in your browser and saved to your machine.
- CSV and JSON exports of result tables
- Chart and view exports as image files
- Your own copy of any script you wrote in the editor
- Anything you choose to paste back into TradingView
Account & operations
What may still exist.
A few things have to exist for TrainBard to function as a service. We try to be specific so you can decide what is acceptable.
- · Account information. If you sign in, basic identity and plan information is kept so we can authenticate you and apply plan limits.
- · Billing data. Paid plans are handled securely through Stripe. We retain the records required to manage subscriptions, refunds, and tax.
- · Operational logs. Standard server logs may include request metadata such as timestamps and error traces. They are not designed as a strategy archive.
- · Aggregate usage. We may track aggregate usage to size capacity and improve performance.
If a specific guarantee matters for your use case, reach out at [email protected]. We would rather answer plainly than over-promise.
Closing the tab
What to expect when you leave.
Closing the workspace is meant to feel like closing a notebook. Anything you wanted to keep should already be exported. Anything you did not export will not be waiting for you in a cloud history.
If a long batch is still running, finishing the run is best done with the tab open. We do not page through unfinished work for you in the background.
Questions
Still want to ask something specific?
Reach out at [email protected] if a security or privacy detail will affect how you use TrainBard.