Register
Learn guide

Understand Broker Permissions and Data Access

When you connect a broker to QuantPower, you allow it to read your trading account and place orders for you. You connect with your own broker API key, your funds stay with your broker, and you sign in to your broker every trading day. This guide to algo trading security explains what a broker connection can and cannot do, how the login works, what data is used and how to keep your account safe.

QuantPower Research · Updated 16 Nov 2026 · 17 min read

Security in algo trading has two halves. One is the broker's side: what its API allows, how sessions start and end, and what the exchange's rules require of every API order. The other is the platform's side: how your keys are stored, how your own login is protected, and what stops an order from going out when something is wrong. A trader needs to understand both, because a weakness in either is a weakness in the whole chain. This guide covers each in turn, then sets out warning signs of an unsafe service, a monthly security routine and what to do if something looks wrong. Never share your broker password, a one-time code or your API secret with anyone, including anyone who says they are from support.

What a broker connection allows

Diagram of what a connected platform can and cannot do with your broker account (illustration)

A connection uses your broker's API, the official interface brokers provide for apps and platforms. The broker decides what the API can do.

A connected platform canA connected platform cannot
See your funds and marginWithdraw money from your account
See your holdings and positionsChange your bank account, address or nominee
See your orders and tradesTransfer shares to another demat account
Place, modify and cancel ordersKeep trading after your broker session ends
Receive market prices for your strategiesSee the password you type on your broker's own sign-in page

Money leaves a trading account only to the bank account registered with your broker, and only when you ask your broker for a withdrawal. A connected platform cannot move it anywhere. The real risk from a connection is therefore unwanted trades, not stolen cash, and the controls below are built around preventing and stopping them.

A short history of trading-account security in India

Online trading in India began around 2000, when brokers started offering internet trading under SEBI's rules for the service. For years, a password was the main protection. As online and mobile trading grew, exchanges and brokers added second factors at login, and today a two-step sign-in is normal for every broker app.

Three later steps shaped how algo trading is secured today. In April 2022, CERT-In, India's computer emergency response team, issued directions requiring organisations, including market intermediaries, to report cyber incidents within six hours and keep logs.1 In August 2024, SEBI issued its Cybersecurity and Cyber Resilience Framework for regulated entities, setting out how brokers and other intermediaries must protect their systems.2 And SEBI's circular of 4 February 2025 on retail algorithmic trading, with NSE's implementation standards of 5 May 2025, set the rules for API access: sign-in with two factors, sessions that end every day, and API orders only from a static IP registered with the broker.3 4 The framework applies to every broker from 1 April 2026.

Each step closed a gap. A password alone can be guessed or stolen; a second factor makes a stolen password useless on its own. A session that never ends gives a stolen token a long life; a daily session limits it to a day. And an API that accepts orders from anywhere invites misuse; a registered static IP means an order from an unknown computer is refused at the broker.

How the connection works

QuantPower uses one connect page for every broker. The steps depend on how your broker signs in, but the outline is the same:5

  1. Open Brokers and pick your broker. Many brokers connect through a single trading system they share, called XTS; others have their own connection.
  2. Whitelist the static IPs. The Brokers screen shows the two static IP addresses that come with your account. Register them in your broker's API console, so that the broker accepts orders that come from them.
  3. Enter your keys, or sign in on the broker's page. For most brokers you enter your client code, API key and API secret from the broker's developer page. For Zerodha, Upstox and Fyers, you tap Sign in, log in on the broker's own page and come back.
  4. Confirm. The app asks for your tap, then sends the keys once over an encrypted connection.
  5. See the result. The row shows "signed in", when the session ends and your static IPs.

What is stored, and how

ItemWhat happens to it
Broker passwordNever sent to QuantPower for redirect sign-in brokers: you type it on the broker's own page
API key and secretSent once, stored encrypted, never shown again on any screen
Client codeStored, and shown masked
The day's session tokenKept for that day's session; ends when the broker ends the session
Your QuantPower passwordNever visible to staff; a reset ends every session of your account

Secrets in the support desk's records are shown masked, and the fields that hold them can be written but not read.

The daily sign-in

Brokers end an API session at the end of the day or sooner, and QuantPower follows each broker's own rule:

Broker typeDaily step
XTS brokers"Log in again" in the app uses your saved key
Zerodha, Upstox, FyersSign in on the broker's own page each day
DhanPaste a new token when the old one ends
ShoonyaSign in with a code you type that day

While a connection needs signing in, the row says "Sign-in needed". A live algo cannot be switched on while its broker is signed out, and a later entry is refused with the reason. Nothing signs you in on your behalf.

Static IPs and order tagging

SEBI's framework ties every API order to your API key and to a static IP registered with your broker, and tags algo orders so the exchange can trace them.3

  • Static IP. Every QuantPower account gets 2 static IPs free, a primary and a backup. Your orders leave through a forwarding proxy that uses them. If the proxy is down, orders are held; they are never sent from another address. Whichever broker you trade with, these are free from QuantPower. No subscription. No questions asked.
  • Order rate. An algo you build yourself can run without exchange registration only while it stays under 10 orders a second. QuantPower caps each broker connection at 10 orders a second and 250 a minute, lower where the broker's own limit is lower.
  • Algo identifier. Each order from a registered strategy carries an exchange identifier, so the exchange can trace it to the strategy, the broker and your account.

These rules make it hard for anyone to trade your account from an unknown computer, or to run a fast algo on it that the exchange has not registered. Our guide to SEBI rules for option trading covers the framework in full.

Protecting your QuantPower login

Your broker protects your trading account; your QuantPower login protects your strategies, your keys and your ability to place orders through them. QuantPower protects it in layers:

LayerHow it works
Sign-up codesA code by e-mail or SMS lasts 10 minutes and stops working after 5 wrong tries
LoginA username and password, or a 6-digit code sent to your e-mail; the e-mail route gives the same answer whether or not an account exists, and sends at most one code a minute
Second factorAn authenticator app (time-based codes) or, where available, a code by SMS. With a second factor, login is two steps; the second step lasts 5 minutes and stops after 5 wrong codes
Sensitive actionsExit all positions, setting the kill switch, confirming an order an AI app prepared and connecting an AI app all ask for the second factor again. Five wrong answers lock that action for 15 minutes
Session cookiesSet by the server and unreadable by page code; the access cookie lasts 30 minutes and is refreshed silently; the refresh cookie changes every time it is used
Stolen-cookie checkIf a used refresh cookie is shown again, the server treats it as theft and ends the session
Forged requestsEvery change request must carry a header that a form on another website cannot add
DevicesUp to 3 signed-in devices by default; a fourth sign-in removes the oldest. Settings, Security, Devices lists them, and you can log one or all of them out
Password resetEnds every session of the account at once

Set up an authenticator app as your second factor. It works without mobile signal, and its codes cannot be redirected the way an SMS can. Test a new device on a quiet day, not just before the market opens, so that a sign-in problem never stands between you and an open position.

What data QuantPower uses and why

DataUsed for
Profile and client IDShowing which account a strategy trades on
Funds and marginChecking margin before orders go out
PositionsPosition monitoring, Smart Exit and the daily loss limit
Orders and tradesThe order book, algo cards and performance reports
HoldingsPortfolio views, pledging and stock SIPs
PricesCharts, the option chain, scanners and your strategies' rules

Your broker decides which data its API shares. The connection gives no access to your bank account or to other demat accounts. When a broker does not answer, risk checks refuse orders rather than assume anything: "no answer" is never read as "no positions". Our QuantPower security page explains how the platform itself is protected.

Safety switches above every strategy

Security is not only about who can log in. It is also about what stops orders when something goes wrong:

  • Kill switch. Stops trading in the segments you choose until each segment's next session, cancels open orders there and stops the running algos in them. Setting it needs the second factor.
  • Daily loss limit. Once the day's loss reaches it, new orders are refused.
  • Maximum orders a day. An optional cap that catches a runaway strategy.
  • Smart Exit. A target, a stop-loss and a trailing step for the whole account; on a hit it stops the algos and squares off.
  • Exit all. Stops the running algos first, then squares off. It needs your tap and the second factor.

The loss figure for these rules combines every connected broker, so a loss at one broker is not hidden from the rules at another.

What support staff can and cannot see

A platform's own staff are part of its security. On QuantPower, the admin area is open only to staff, its login is throttled, and admin actions are written to a log.

Staff canStaff cannot
Find your account by name, mobile, e-mail, username or client ID, to help youSee your API secret: secret fields are masked and can be written but not read
See your login history and connected brokers, with secrets maskedSee your QuantPower password or your broker password
Block access to an account, which ends every session at once and records who did it and whyPlace orders in your account from the admin area
Use an AI draft for a support reply, which they edit before sendingLet that AI draft see any key, secret, password, e-mail address or phone number

If anyone claiming to be from support asks for a password, a one-time code or an API secret, it is not support. End the conversation and report it.

How scams reach traders

Most account losses do not come from clever attacks on systems. They come from a person being persuaded to hand something over. The common patterns:

  • Fake support. A message or call says your account will be blocked unless you "verify" by sharing a code. No genuine broker or platform asks for one.
  • Tip groups. A Telegram or WhatsApp group shares a few winning calls, then offers to "run your account" if you share your API key or session token. Anyone with those can trade your account until the session ends.
  • Look-alike sites. A page that looks like your broker's sign-in page, reached from a link in a message. Type your broker's address yourself, or use its app.
  • Screen-sharing requests. Someone asks you to install a remote-access app "to help with the setup". Once installed, they can see your codes as they arrive.
  • Guaranteed-return algos. Any promise of a fixed return is a red flag, and under SEBI's rules a broker may not even mention an algo's returns.

The defence is the same in every case: never share a secret, never sign in from a link you did not ask for, and when in doubt, stop and call your broker on the number printed on its own website.

Families and shared devices

Many households share a laptop or a tablet. A few habits keep each account separate:

  • One account per person, each with its own password and second factor. Never trade someone else's account from your login, or yours from theirs.
  • Log out on shared devices, and check Settings, Security, Devices afterwards.
  • Separate browser profiles, so that saved passwords and cookies do not mix.
  • Static IPs per account. Each QuantPower account has its own two static IPs, registered with its own broker account. Some brokers allow family members to share a registered IP under their rules; check your broker's terms before relying on that.

AI apps and your account

If you connect your own AI app, such as Claude or ChatGPT, through Connect AI, it receives a revocable token with only the permissions you tick. It can read your account and market data, backtest your rules and save an algo switched off. It cannot place, change or cancel an order, switch an algo on, or confirm its own suggestions. If you allow it to prepare an order, the order appears as a card in your app, lasts 15 minutes, and goes out only when you confirm it with your tap and the second factor. A token lasts a year and can be revoked in the app at once.

Two-factor authentication at your broker

Every broker login needs a second factor, usually a six-digit code from an authenticator app or a one-time password sent to your phone.

  • Use an authenticator app if your broker supports one. It works without mobile signal.
  • Keep your phone's clock on automatic time, because authenticator codes depend on it.
  • Never share your broker password, a one-time code or an authenticator code. No genuine support team needs one to help you.
  • Never share the setup key or QR code for your authenticator. Anyone who has it can generate your codes.
  • Keep a backup of your authenticator, or your broker's recovery steps, somewhere safe and offline.

Worked example: following one order through the checks

You switch on a Nifty short straddle algo, live, at 9:15 am, with an entry at 9:20. At 9:20 the algo sends two sell orders. This is what each passes through before it reaches the exchange:

CheckWhat is checkedIf it fails
Your sessionYour QuantPower login is validNothing is sent; you are asked to sign in
Broker sessionThe broker is signed in for todayThe entry is refused with "sign in to your broker"
InstrumentContract, lot size and tick size are validThe order is refused with the reason
Account rulesKill switch, daily loss limit, order cap, ban listThe order is refused; a square-off is never blocked
Static IPThe order leaves through the proxy on your registered IPIf the proxy is down, the order is held, never sent elsewhere
RateWithin 10 a second and 250 a minute for this brokerThe order waits its turn
BrokerThe broker's own risk checks, margin and API rulesThe broker rejects it and the algo shows the reason
ExchangePrice band, freeze quantity, trading hoursThe exchange rejects it

Two orders, eight layers of checks, and a record of each step on the algo card. A manual order also needs your tap, which is bound to your session and to that exact order, works once and expires in 60 seconds; an algo you switched on does not, because you authorised it when you switched it on.

How to revoke access

You can end a platform's access at any time.

  1. Disconnect in QuantPower: remove the broker in Brokers. Algos on that connection stop placing orders.
  2. Revoke at the broker: delete the API key or regenerate its secret in your broker's API console, and remove the static IPs if you no longer need them. Most brokers also list connected apps in their account settings.
  3. Change your passwords and reset your second factor if you think someone else has your details.
  4. Log out other devices from Settings, Security, Devices.

Before you disconnect, close any positions an algo is managing or decide how you will manage them. Once access ends, QuantPower can no longer exit them for you.

Warning signs

These are signs that an automation service is unsafe or not following the rules:

  • It asks for your broker password, a one-time code or your authenticator setup key.
  • It promises a fixed daily or monthly return. SEBI bars brokers from referring to algo performance and from working with platforms that do.6
  • It asks you to transfer money to it, or to hand over control of your account so it can trade for you.
  • It sells ready-made strategies with hidden logic and has no SEBI research analyst registration.
  • Its orders do not go through your own broker account.
  • Someone in a Telegram or WhatsApp group asks you to send your API key, API secret or session token.

Records: your best evidence

If something goes wrong, records settle the question. Your broker keeps an audit trail of API orders under SEBI's framework, and sends contract notes for every trading day. The exchange sends trade alerts to your registered phone and e-mail. On QuantPower, each algo has an activity log with one plain line for every entry, exit, re-entry, change and refusal, which you can copy for a day, and the order book shows each order's status and the broker's message. Keep these for any dispute: the time, the order ID and the exact message are what a broker or SEBI will ask for.

Common mistakes

  • Pasting an API secret into a chat to "get help". Treat it like a password; regenerate it if you ever did.
  • Using SMS as the only second factor when an authenticator app is available.
  • Leaving old API keys active at the broker after you stopped using a service.
  • Ignoring exchange trade alerts. NSE and BSE send alerts of trades to your registered phone and e-mail; read them.
  • Sharing one login between family members. Each person should have their own account and second factor.
  • Never checking the Devices list. A device you do not recognise is the first sign of trouble.

A monthly security routine

  1. Review the API keys and connected apps at each broker; remove any you do not use.
  2. Open Settings, Security, Devices in QuantPower and log out any device you do not recognise.
  3. Check the AI apps connected through Connect AI and revoke any you no longer use.
  4. Confirm your second factor works and your recovery steps are stored safely.
  5. Compare your broker's contract notes for the month with your own records.
  6. Check that your daily loss limit and Smart Exit settings still match your account size.

If something looks wrong

  1. Log in to your broker's app and check orders and positions there.
  2. Cancel unwanted orders and close unwanted positions directly with your broker, or use the kill switch in QuantPower.
  3. Disconnect the platform, change your broker password and regenerate your API secret.
  4. Contact your broker and QuantPower support with the time, order IDs and screenshots, never your password or codes.
  5. If your broker does not resolve the complaint, raise it with SEBI through the SCORES portal.

Under SEBI's framework, your broker handles complaints about algo orders placed through its systems. You can reach QuantPower at [email protected], by phone on +91 97111 30044, or through our contact page. Our guide to troubleshooting algo trading covers problems that are not security issues, such as expired sessions and rejected orders.

Where trading security is going

The direction is towards fewer secrets in fewer places. Redirect sign-in, where you sign in on the broker's own page and the platform never sees your password, is spreading. Static IPs tie orders to known machines. Daily sessions limit the damage a stolen token can do. And as AI apps connect to trading accounts, the safe pattern is becoming standard: the AI may read and prepare, and only the account holder, with a second factor, can confirm. The trader's part does not change: keep secrets secret, use an authenticator, and check the account regularly. Regulators are moving the same way, asking brokers for stronger controls, faster incident reporting and clear records of every API order, so the habits that protect one trader also make the whole system easier to trust.

Before you connect

Check the broker connection requirements for your broker: API access, segments, the static IP whitelist and the daily sign-in. Then run your first strategies in a forward test, with test money, before any real order goes out.

Start with 500 free tokens

Connect your broker, build a strategy and test it on paper before a single live order goes out.

Frequently asked questions

Can QuantPower withdraw money from my trading account?

No. Broker APIs do not allow withdrawals. Money leaves your trading account only for your registered bank account, when you request it from your broker.

Does QuantPower see my broker password?

Not for Zerodha, Upstox and Fyers: you type it on the broker's own page. For other brokers you enter an API key and secret from the broker's developer page, which are stored encrypted and never shown again; your broker login password is not part of them.

Why do I have to sign in to my broker every day?

SEBI's framework requires brokers to end every API session before the next trading day. The daily sign-in also limits how long a stolen token could be used.

What happens to my positions if I disconnect?

They stay open in your broker account. QuantPower can no longer manage or exit them, so close them or manage them in your broker's app.

What happens if the static IP proxy is down?

Orders are held, not sent from another address. The algo card shows the reason, and the orders go only when the proxy is back on your registered IPs.

Can an AI app connected to my account place orders?

No. A connected AI app can read your account, backtest and save algos switched off. At most it can prepare an order card, which goes out only when you confirm it with your tap and the second factor.

Should I use an authenticator app or SMS codes?

An authenticator app, where you have the choice. Its codes are generated on your phone, work without mobile signal and cannot be redirected to another SIM, as an SMS sometimes can. Keep a safe backup of the setup or your recovery steps, so that a lost phone does not lock you out.

References

  1. CERT-In, directions under section 70B of the Information Technology Act on reporting cyber incidents, 28 April 2022 (cert-in.org.in)
  2. SEBI, Cybersecurity and Cyber Resilience Framework for SEBI regulated entities, 20 August 2024 (sebi.gov.in)
  3. SEBI, circular on safer participation of retail investors in algorithmic trading, 4 February 2025, in force for every broker from 1 April 2026 (sebi.gov.in)
  4. NSE, implementation standards for retail algo trading, 5 May 2025 (nseindia.com)
  5. QuantPower: broker connection, sign-in, sessions, static IPs, order checks and safety switches, from the app's code, checked 12 November 2026
  6. SEBI, circular barring brokers from referring to past or expected performance of an algorithm, 2 September 2022 (sebi.gov.in)
Trading involves substantial risk. This page is for information and is not investment advice.