How-to Kite app logout TOTP battery optimisation background app device lock

How to fix Kite logging out when switching apps

From WebNotes, a public knowledge base. Last updated . Reading time ~9 min.

The Kite app logs you out when you switch to another app, such as an authenticator app to copy a time-based one-time password (TOTP), because your device is in power-saving mode or is preventing Kite from running in the background; the operating system kills the backgrounded app and drops your session. Per Zerodha’s own support article, this is a power-management behaviour, not a deliberate security lock that triggers on app switch. The fix is to stop the OS from suspending Kite: turn off power saving, exempt Kite from battery optimisation, or sidestep the switch entirely by using device-lock biometric login instead of TOTP.

This guide explains the real cause, the exact Android and iOS battery settings to change, the background-running exemption, the app-data reset of last resort, and the cleanest structural fix, which is to switch your second factor so you never have to leave Kite to read a code. The fixes take under five minutes and cost nothing.

Conflict-of-interest disclosure. This guide is published by the WebNotes Editorial Team for informational purposes and is written independently. WebNotes operates a Zerodha account-opening referral programme, disclosed on the pages that carry the referral link; this guide does not carry it and earns no referral commission from the procedure described here.

Step-by-step procedure

The numbered box at the top of this guide gives the sequence. The detail below expands the cause, the per-OS battery settings, and the structural workaround.

1. Recognise the cause

The logout looks like a security lock, but it is the OS reclaiming memory. When Kite loses focus, an aggressive power saver or a background restriction can terminate the process, and a terminated process loses its session. Zerodha states plainly that the app “logs out when you switch to another app or minimise it because your device is in power-saving mode or is preventing the application from running in the background.” Treat it as a battery setting to fix, not a Kite bug to report. The same root cause is why a backgrounded Kite sometimes shows a blank screen or stale data on return.

2. Turn off power saving on Android

On Android, open Phone settings, then Battery, and either change the power plan to performance or turn off power-saving mode. Power-saving and “adaptive battery” profiles suspend apps that lose focus, which is exactly what drops the Kite session when you tab over to Google Authenticator, Authy, or Microsoft Authenticator. With the profile set to performance, the OS leaves Kite alive in the background for the few seconds you need to copy a code.

3. Turn off Low Power Mode on iOS

On iOS, open Settings, then Battery, and turn off Low Power Mode. Low Power Mode pauses background activity to save charge, and a paused Kite session can be torn down when you switch to your authenticator. With Low Power Mode off, iOS keeps Kite resident long enough to survive a brief switch. Re-enable Low Power Mode later if you want; just expect the logout to return while it is on.

4. Allow Kite to run in the background

Beyond the global power mode, exempt Kite specifically. On Android, find Kite in the battery settings and set it to Not optimised, and allow it to run in the background and keep running when the screen is off. On iOS, enable Background App Refresh for Kite. This per-app exemption is the durable fix, because it survives even when a system-wide battery saver kicks in at low charge. Avoid third-party app-killer or “RAM cleaner” utilities, which undo this by force-stopping Kite.

5. Clear the app data if it persists

If Kite still logs out on switch after the battery changes, clear the Kite application data from your phone settings, then reopen and log in fresh. This clears a corrupted local cache that can confuse the session state. It removes only the local app state and logs you out; your account, holdings, funds, and orders are on Zerodha’s servers and are not touched. After clearing, run the normal login again.

6. Avoid the switch with device-lock login

The cleanest fix removes the app switch altogether. If you authenticate with device-lock biometric login instead of TOTP, the second factor is a fingerprint or Face ID prompt inside the Kite login flow, so you never leave Kite to copy a code, and there is nothing to switch to. Switch the factor under How to enable device lock on Kite , or change it under How to reset 2FA at Zerodha . For traders on a single phone, this is the structural answer; the battery settings are the fix if you want to keep TOTP.

Why TOTP on the same phone creates the friction

The logout bites hardest in one workflow: you trade and hold your authenticator on the same phone. To log in you enter your password, then you must read a TOTP that lives in a separate app, so you switch away, and the power saver kills Kite while you are gone. When you switch back, the session is dead and you start over. The Kite app code framework offers TOTP and device lock as the two second-factor choices; TOTP is the one that forces an app switch on a single device, and device lock is the one that does not. Compare them in Kite app code: TOTP versus SMS OTP .

If you keep TOTP, two habits reduce the pain even before the battery fix lands. Read or copy the code in the authenticator just before you start the Kite login, so the switch is as brief as possible. Or run the authenticator on a second device, a tablet or a desktop authenticator, so reading the code never backgrounds Kite at all. Authy, for instance, syncs tokens across devices, so you can read the code on a desktop while logging in on the phone.

The five-minute login window interaction

There is a second timer at play. You must enter your 2FA within five minutes of entering your login credentials. If a power saver kills Kite mid-switch and you fumble back in, you can blow past that five-minute window, at which point the login itself expires and you restart from your password regardless of the session question. So the battery fix and the five-minute limit compound: the slower the switch, the more likely both fail. Fixing the background behaviour, or removing the switch with device lock, addresses both at once.

How this differs from the daily regulatory logout

Do not confuse this app-switch logout with the daily forced logout that every Kite user sees. Under SEBI’s framework, Zerodha logs all users out at the end of each trading day, so a fresh login each morning is normal and unrelated to your battery settings. That is the risk-disclosure-on-every-login flow working as designed. The app-switch logout, by contrast, happens mid-session and repeatedly, and it is a power-management problem you can fix on your phone. If your “logout” is once a day at session end, nothing here applies; if it is every time you reach for your authenticator, this guide is the fix.

See also

External references

References

  1. Zerodha support, Why does the Kite app log out when I switch to another app? (power-saving and background-restriction cause; Android and iOS battery fixes; as of 20 June 2026).
  2. Zerodha support, How do I log in to the Kite app? (five-minute window to enter 2FA; as of 20 June 2026).
  3. SEBI, Cyber Security and Cyber Resilience framework for Stock Brokers and Depository Participants (end-of-day forced logout and two-factor authentication).

WebNotes Editorial Team prepares factual how-to guides based on publicly available regulatory documents and broker disclosures. WebNotes is not affiliated with Zerodha Broking Limited. Procedures are subject to change; verify current requirements at support.zerodha.com before acting.

Related articles

Frequently asked questions

Why does Kite log out when I switch to my authenticator app?
Because your device is in power-saving mode or is preventing Kite from running in the background. When you switch away to copy a TOTP, the operating system kills the backgrounded Kite app, which drops your session and logs you out.
Is the logout a security feature that blocks app switching?
No. Zerodha attributes the logout to power management and background-app restrictions, not to a deliberate security lock that triggers on app switch. Fixing the battery and background settings stops it.
How do I stop Kite logging out on Android?
Open Phone settings, Battery, and switch the power plan to performance or turn off power saving. Then set Kite’s battery optimisation to Not optimised and allow it to run in the background. Reopen Kite and log in.
How do I stop Kite logging out on iPhone?
Open Settings, Battery, and turn off Low Power Mode, which suspends backgrounded apps. Also allow Background App Refresh for Kite. With those off, Kite survives a brief switch to your authenticator app.
What is the cleanest way to avoid this entirely?
Use device-lock biometric login instead of TOTP. With a fingerprint or Face ID as your second factor, login authenticates inside Kite, so you never switch to an authenticator app to copy a code, and the logout never happens.
Could the five-minute login window also cause this?
Yes, indirectly. You must enter your 2FA within five minutes of your credentials. If switching apps and power saving delay you past that window, the login itself expires, so you have to start again from your password.
Will clearing app data delete my account or holdings?
No. Clearing the Kite app data only removes the locally cached app state and logs you out. Your account, holdings, funds, and orders live on Zerodha’s servers and are untouched. You log back in afterwards.

Reviewed and published by

WebNotes Editorial Team

The WebNotes Editorial Team covers Indian capital markets, payments infrastructure and retail investor procedures. Every article is fact-checked against primary sources, principally SEBI circulars and master directions, NPCI specifications and the official support documentation published by the intermediary in question. Drafts go through a second-pair-of-eyes review and a separate compliance read before publication, and revisions are tracked against the SEBI and NPCI rule changes referenced in the methodology section.

Last reviewed
Conflicts of interest
WebNotes is independent. No relationship with any broker, registrar or bank named in this article.