Security

Security

Last updated: 20 October 2026

SetYourPlan places the orders of your plans on your own Binance account, through an API key you create. This page explains what that key can do, what we do to limit it, and what to do if something looks wrong.

No system is perfectly secure. This page describes what we do; it is not a promise that nothing can go wrong.

What a connected key can and cannot do

• It can read your balances and orders, and place and cancel spot orders on your account. That is how your plans run.
• It cannot withdraw or transfer your funds, or trade futures, margin or options. We only accept keys with those permissions turned off, and Binance enforces them on its side.
• We do not place orders outside the plans you arm, cancel orders we did not place, or hold your money. We will never ask for your Binance password, your two-step codes, or a key that can withdraw.

A key that can trade can still lose money through trades. In December 2022, API keys leaked from another trading service were used to make victims' accounts buy thinly traded coins at inflated prices. No withdrawal was needed. The measures below are aimed at that kind of misuse.

Which keys we accept

• Before a key is saved, we read its permissions from Binance. Keys that can withdraw, transfer between accounts, or trade futures, margin, options or portfolio margin are refused. Spot trading must be on. (The Binance test network does not report permissions, so this check is skipped there; no real money is involved.)
• The key must be restricted to the IP addresses we reach Binance from (195.40.129.21). Binance then refuses the key from any other address. For now these addresses come from a proxy service. They are not ours alone: other customers of that service can send requests from them too.
• We read the key's permissions again about every 3 hours, and right before a plan buys if the last reading is older than that. If withdrawals or transfers have been turned on, the IP restriction is off, or Binance refuses the key, we email you once, show it on your dashboard and Exchange page, and send no new buys with that key until a later check passes: a waiting plan skips the breakout and waits for a new one, and a second buy that is not on Binance yet is skipped. Selling, targets and emergency stops are never paused by this. (A self-generated key works on Binance even without an IP restriction, which is why we keep checking.)
• Two kinds of key work. A system-generated key comes with a secret key from Binance. A self-generated Ed25519 key is a key pair you create yourself: Binance only ever gets the public half, and you give us the private half. Binance recommends Ed25519 keys. We store and protect both kinds the same way.

How keys are stored

• Your secret key or private key is sealed the moment you submit it. The website holds only the key that locks it; the key that opens it exists only on the order engine, a separate service. A breach of the website alone does not reveal usable exchange keys.
• We never show a secret or private key back to you, or to anyone, after you paste it.
• Removing the key under Exchange erases our sealed copy. Deleting it on Binance cuts access at once, without us.

Liquid pairs only

Plans can only use USDT spot pairs that traded at least 20M USDT on Binance in the last 24 hours. The plan card checks this, and the engine checks it again right before it sends a buy order: the entry, and each part of a second buy at the moment it is sent. If the pair is below the line when the entry is due, nothing is bought and the plan ends without a trade. If it falls below the line after the entry, a second buy that has not been sent yet is skipped and the position goes on as planned. A second buy that already rests on Binance is not checked again: Binance fills it at its price. Selling is never blocked by this rule.

Why: a thin market is easy to push around; a liquid one is not. The rule keeps our engine away from the kind of coin used in the 2022 misuse described above, and keeps your fills close to the price on your card.

These rules cover the orders our engine places. Someone holding a stolen key could try to use it directly. The IP restriction is the main barrier: Binance refuses the key from any address that is not on its list. While our addresses are shared, it does not keep out the proxy service's other customers. If our own servers were ever compromised, these rules could be bypassed. That is why you can always cut access by deleting the key on Binance.

Orders we did not place

While you have an active plan, the engine reads the open orders on that plan's pair regularly. We aim for about every 3 minutes; with many accounts connected, the gap can be longer. An order counts as ours only if its Binance order number is one the engine recorded when it placed the order; an order whose name merely looks like ours does not count. If the engine finds an order it did not place, it records it in your Activity log and alarms you once about that order, even if you turned trade emails off. It does not cancel the order, because it may be yours.

Limits: this check sees only orders that are still open, and only on pairs where you have an active plan. An order that fills at once, or one on another pair, does not show up in it; the account watch below may still see what it bought. Binance's own order and trade history shows everything.

Coins your plans did not buy

Whether or not you have a plan, the engine regularly reads the balances on your connected key and compares them with its last reading. We aim for about every 5 minutes; with many accounts connected, the gap can be longer. If a coin appears that was not there, or a holding grows by more than 50%, and your plans here did not trade that coin since the last reading, you get an alarm. Nothing is sold or cancelled.

Limits: a coin bought and sold again between two readings is not seen, and your own deposits, converts, airdrops or Earn redemptions show up too (the alarm says so). The first reading after you connect a key is only the starting point.

How alarms reach you

Everything one check finds comes in one email. After 6 alarm emails in a day, the rest come in one summary a day. If you also trade by hand or with another app on this Binance account, you can choose the daily summary for all alarms in Settings. Your Activity log shows every alarm at once either way.

Protection that rests on Binance

• As soon as a buy fills, each target is sent to Binance together with your emergency stop as one order (an OCO). It rests on Binance, so it can execute even if our servers are down.
• A second buy rests on Binance as an OTOCO order: when it fills, Binance itself places its target and emergency stop.
• The candle-close stop, time stop and trailing stop are watched by our engine and need it running. We can stop all new orders from our side at once; orders already resting on Binance stay there.

Your account here

• Two-step login with an authenticator app is required before you can connect a live key.
• Repeated wrong passwords and codes are slowed down. Logging out or changing your password ends every session.
• Your Activity log lists every key change, every decision the engine made and every order it sent.