Security starts with the boundary around the action.
Use the narrowest permission
Create a dedicated API key for the intended workflow and grant only the permissions it needs. Never share API secrets, passwords, seed phrases or two-factor codes with support.
Start in demo mode
Use Binance Futures Demo to test connection scope, rejection paths, limits, pause behaviour and the decision record before considering any live environment.
Keep control with the operator
A useful workflow exposes its current state, active limits and stop path. If credentials may have been exposed, revoke them immediately and create a new key through the exchange.
What Qantova does not guarantee
No software removes market, exchange, connectivity or execution risk. Qantova provides workflow and review tooling, not financial advice or a promise of performance.