Your data and your keys
Security & privacy
BearBreaker is designed to keep control where it belongs: with you. Here is how the system protects your information.
Your keys stay on your machine
BearBreaker runs locally. Alpaca API keys are stored in your own environment file, never on a server I control.
No cloud database for trading data
Your TCB ledger, order history, and outcome journal live in local files on your machine. I cannot see them.
The website only stores email addresses
When you join the beta waitlist or send a contact message, the site stores only the information you submit. No trading data, no API keys, no portfolio details.
Direct brokerage communication
Orders and account reads go directly between your local instance and Alpaca. Nothing is routed through BearBreaker servers.
Single-instance lock
The system refuses to run two copies at once, preventing duplicate orders and conflicting state.
Source code is yours to audit
You receive the full script. You can read every line, change anything, and run it in a way you trust.
A note from Boxont
I run this system with my own capital. I built it so I never have to hand over API keys or portfolio data to a third-party dashboard. The same architecture protects your setup.