Security & privacy
Your strategy stays yours.
TrainBard does not store the strategies you test or a cloud history of the results you generate. This page explains what the service does keep.
Data flow
What happens when you run a batch.
When you run a batch, your script and its inputs go to the engine. The engine runs the combinations and streams the results back to your browser. The session ends when you close the tab.
No cloud result history. Your scripts stay in your browser.
What TrainBard doesn't store
Your strategy is not saved.
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
Keep the files you export.
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
Account and operational data.
TrainBard keeps a few kinds of data to run accounts, billing, and the backtest service.
- · 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, email [email protected]. We will answer plainly.
After you close the tab
Export anything you want to keep.
Anything you did not export will not be waiting for you in a cloud history.
A long batch needs the tab open until it finishes. TrainBard does not continue unfinished work in the background.
Questions
Have a specific question?
Email [email protected] if a security or privacy detail affects how you use TrainBard.