Connecting Binance Futures safely
Connecting an exchange is optional — signals work without it. But if you do connect one, key permissions matter more than anything else.
Permissions you need and do not need
- Enable Futures — required. Without it orders cannot be sent.
- Enable Reading — on by default for a new key, needed for balance and positions.
- Enable Withdrawals — never needed. Binance already requires a separate allowlist of addresses for withdrawals, but the safest option is simply not to grant the permission.
- Enable Spot & Margin Trading — not needed; the service works only with USDT-M futures.
About IP restriction
Binance lets you bind a key to a list of IP addresses, which improves security a lot. Note the mechanics though: requests to the exchange are sent from the TradeRadar server, not from your browser. So the allowlist must contain the server IP, not your home address — otherwise orders will be rejected with a permissions error.
If you would rather not deal with an allowlist, leave the key without an IP restriction — but then it is all the more important not to grant withdrawal rights.
How we store it
The key and secret are encrypted with AES-256-GCM and reach the database only in encrypted form. The interface shows the key masked — first and last four characters. The secret is never displayed and is never returned through the API.
On save the service first makes a test balance request to the exchange: an invalid key is not stored at all. The Disconnect button removes the record from the database entirely.
Start on testnet
The connection form has a testnet switch. Binance testnet is a full copy of futures with play money: orders, stops and liquidations behave identically, but there is nothing to lose. Run at least a few trades there before connecting a live key.
If something goes wrong
A key is revoked on the exchange side in one click, in the API management section. Do that immediately if you suspect a leak: disconnecting on our side is not enough — revoke it where it was issued.