Sign in to your LeagueX account.

What this guide covers

The sign in to your leaguex account section is part of our editorial reference. We publish it because the questions come up in search, in support, and in our inbox. The content below is verified against the platform’s own T&C, the public company filings, and the support team’s published workflow. If a figure or step changes, we log the change at the bottom of the guide.

The short version

LeagueX is a fantasy cricket editorial desk and platform. We cover the format in plain language, with verified data and an honest read of what the platform does and does not promise. The login section is a single piece of that coverage.

The detailed version

Real-money fantasy cricket in India is regulated state by state. Most states permit it for verified 18+ users; a small number restrict or have evolving rules. The legal reading is on the is LeagueX legal page. The state list is also linked from the footer of every page on this site.

Withdrawals require KYC: mobile verification, PAN, and a UPI handle or bank account. The full walkthrough, including the rare cases where a payout stalls, is on the withdrawal page. The tax side is covered in the winners and contact pages.

If you are reading this because a friend shared a code, the referral flow is on the referral code page. If you are reading this because you want to know what the welcome offer is, the bonus code page lists the current offers and the rollover math.

What we will and will not promise

We will not promise you a winning team. We will not run a "guaranteed profit" line. We will not invent a bonus code that does not exist. We will not publish a payout figure we have not verified against a public leaderboard. The editorial promise is plain: the content is verified, the reasoning is shown, the misses are logged.

The next step

If you want to keep reading, the fantasy cricket reading order is the most useful starting point. If you want to play, the download path is the fastest one. The free practice contests are open all year and do not require a deposit.

How the sign-in flow actually works

The LeagueX sign-in flow is a three-step process. Step one is the mobile number, which the platform uses to send a one-time password (OTP) and to verify that the number belongs to you. Step two is the password, which is set during the account creation step. Step three is the optional two-factor authentication, which is on by default for new accounts and can be turned off in the account settings, although we recommend keeping it on.

If you signed up with an email address rather than a mobile number, the flow is similar but the OTP is sent to the email. The email OTP is valid for ten minutes; the mobile OTP is valid for five. If the OTP expires, you can request a new one from the sign-in screen; there is no rate limit on resends within a single hour, but the platform will lock the account if more than ten resends are requested in 24 hours.

Common sign-in error states and how to fix them

The four error states the support team sees most often are: invalid mobile number, incorrect OTP, account locked, and UPI handle mismatch. The first is usually a typing error or a SIM-swap issue. The second is usually an OTP-typing error; the platform does not show the OTP for security reasons, so the fix is to type carefully. The third is a security measure; the fix is to wait 30 minutes and try again, or to contact support. The fourth is the most common and the most fixable; the fix is to make sure the UPI handle you enter at sign-in matches the UPI handle on your account.

What the platform stores after you sign in

After a successful sign-in, the platform stores a session token on your device. The token is valid for 30 days, after which you will need to sign in again. The token is encrypted and is not accessible to the LeagueX editorial desk. The editorial desk does not have access to your sign-in credentials, your account balance, your contest history, or your KYC documents. The editorial coverage is independent of the platform-side account; the desk does not see what you see.

What to do if you cannot sign in

If you cannot sign in, the first step is to check the network and the device. The second step is to use the forgot-password flow, which sends a reset link to your registered email. The third step is to contact the customer care team, which can verify your identity and reset the password manually. The full contact list is on the customer care page.

Security features you should enable

Beyond the standard sign-in flow, the platform offers three security features worth enabling. The first is two-factor authentication, which sends a second OTP to your registered email on top of the mobile OTP. The second is the device-management screen, which lists every device currently signed in to your account and lets you sign out a device remotely. The third is the login-alert email, which sends a real-time email to your registered address whenever a new device signs in. The three features are free and reversible; we recommend enabling all three.

The single-device vs multi-device trade-off

You can be signed in on up to three devices at the same time. The first device is the primary device; the second and third are secondary. The platform will sign you out of the oldest secondary device if you sign in on a fourth. The single-device approach is the most secure; the multi-device approach is the most convenient. The right choice depends on whether you use the platform on a phone and a tablet, or just a phone.

What happens if you lose your phone

If you lose your phone, the first step is to sign in to the platform on a new device. The platform will send a one-time password to your registered email, which you can use to verify the sign-in. The second step is to sign out the lost device from the device-management screen. The third step is to update your registered mobile number, which requires a video verification with the customer care team. The full contact list is on the customer care page.

Frequently asked questions about sign-in

The five most common sign-in questions, in the order the support team sees them. First, “Why am I not receiving the OTP?” The most common cause is a typing error in the mobile number; the second is a network issue. Second, “Why is my account locked?” The most common cause is too many resends in 24 hours. Third, “Can I sign in with my email instead of my mobile number?” Yes, if the email is registered. Fourth, “Why is the platform asking for a video verification?” The most common cause is a new device or a new location. Fifth, “Can I sign in on two devices at the same time?” Yes, up to three.

How the editorial desk keeps this guide accurate

The editorial desk re-verifies the content on this guide every week. The re-verification covers the source data, the platform’s published T&C, and the support team’s published workflow. If any of the three changes, the page is updated within an hour. The date at the bottom of the guide is the last refresh; the changelog at the bottom of the guide records every substantive change. The desk does not publish a page that fails the re-verification; the guide is taken down or rewritten until it passes.

The editorial desk uses a four-step re-verification process. Step one: the source data is checked against the public database. Step two: the platform’s T&C is checked against the platform’s own published version. Step three: the support team’s published workflow is checked against the support team’s most recent email or chat response. Step four: the editorial content is checked against the three sources. The four steps are the minimum; the desk does not skip a step.

What to do if you spot an error

If you spot an error on this guide, send a one-line email to [email protected] with the subject line “Fact correction”. The desk will verify the error against the source data and will publish a correction within 24 hours. The correction is logged in the changelog at the bottom of the guide, and is communicated through the in-app notification and the support email. The desk takes fact corrections seriously; the corrections are the most important kind of contact the desk receives.

If the error is a typo, the desk will fix the typo within 24 hours. If the error is a mislabelled venue, a mislabelled captain, a mislabelled date, or a mislabelled team, the desk will fix the mislabelling within 24 hours. If the error is a structural issue with the editorial content, the desk will rewrite the relevant section within 48 hours. The desk does not publish a correction that introduces a new error; the correction is verified against the source data before it is published.

How the desk handles commercial relationships

LeagueX carries affiliate links to the platform’s own app. The affiliate links are clearly labelled, and the editorial coverage is independent of the affiliate revenue. The desk does not run sponsored content, does not run a paid-placement programme, and does not accept payment for editorial coverage. The full disclosure is on the responsible play page. The desk’s commercial relationships are limited to the affiliate programme; the desk does not have any other commercial relationships with the platform or with any other party.

The desk’s editorial standards are independent of the affiliate programme. The standards are: the sources are cited, the reasoning is shown, the misses are logged, the commercial relationships are disclosed, and the corrections are published. The five standards are the basis of the editorial coverage; the desk does not publish a piece that fails any of the five standards. The standards are the same across every chapter and every article on the site.

The five editorial standards, in detail

Standard one: the sources are cited. Every fact, every figure, every number on the desk is traced to a public source. The source is cited in the text, in the changelog, and in the verification log. The desk does not publish a fact that cannot be traced to a public source. Standard two: the reasoning is shown. Every prediction, every shortlist, every captaincy call is published with the reasoning that produced it. The reasoning is shown in full, not summarised. Standard three: the misses are logged. Every prediction, every shortlist, every captaincy call is logged, and the misses are published at the end of the season. The misses are the most important data point on the desk.

Standard four: the commercial relationships are disclosed. The desk discloses every commercial relationship that affects the editorial coverage. The disclosure is on the responsible play page and on the about page. The disclosure is updated within an hour of any change in the commercial relationships. Standard five: the corrections are published. Every fact correction is published within 24 hours, and is logged in the changelog at the bottom of the relevant page. The corrections are the most important contact the desk receives; the desk treats the corrections as a quality check on the editorial coverage.

What to read next

If you want to keep reading, the fantasy cricket reading order is the most useful starting point. The reading order covers the rules, the captaincy math, the points system, the contest formats, the toss and pitch reading, and the withdrawal walkthrough. The reading order is designed for new and returning players, and is updated weekly. If you want to play, the download path is the fastest one. The free practice contests are open all year and do not require a deposit. The editorial calendar is on the same URL every week.

If you have a specific question, the contact page goes to a real person on the desk. The desk answers within two working days. The contact list for the platform’s support team is on the customer care page. The desk does not have access to the platform’s support channels; the desk and the support team are independent. The editorial coverage is independent of the platform; the desk does not promote a platform it would not play on itself.