Login — Fantasy Cricket Account Access

Login guide for fantasy cricket in India: 4 major apps' login methods, password recovery, 2FA setup, daily-login checkli…

The login is the daily operational entry point to the fantasy cricket season. The IFI editorial desk treats the login as a 30-second daily ritual that sets the captaincy research, the contest allocation, and the withdrawal planning for the day. This page is the consolidated login reference for the pan-India fantasy community: the four major apps' login methods, the password recovery, the two-factor authentication setup, and the daily-login operational checklist.

The four major apps' login methods

All four major apps support login via mobile number + password, mobile number + OTP, and (on supported devices) biometric login. Dream11's standard login is mobile number + password, with OTP as a fallback. My11Circle's standard login is mobile number + OTP (no password). MPL's standard login is mobile number + OTP. MyTeam11's standard login is mobile number + password, with OTP as a fallback.

The IFI desk's recommendation: enable biometric login on the day-1 configuration. The biometric login (fingerprint or face ID) is faster than the OTP-based login (the OTP takes 5-10 seconds to arrive, the biometric takes 1-2 seconds), and the biometric login is more secure than the password-based login (the biometric is tied to the device, the password can be phished).

The password: how to set a strong one

The password should be unique to the operator (do not reuse the password from another app), at least 12 characters long, with a mix of uppercase, lowercase, numbers, and special characters. The IFI desk's recommendation: use a password manager (1Password, LastPass, Bitwarden) to generate and store the password. The password manager generates a 20-character random password that is unique to the operator, and the manager auto-fills the login form on the next visit.

The password should be rotated every 6-12 months, especially if the player has signed in on a shared device (a friend's phone, a hotel business center, a public computer). The IFI desk's recommendation: rotate the password at the start of each T20 league season (IPL, SA20, ILT20, etc.), not in the middle of the season. The mid-season password rotation is a logistical friction that can lead to forgotten passwords and locked accounts.

The two-factor authentication (2FA) setup

The 2FA is the second layer of authentication, in addition to the password. The 2FA is enabled via SMS OTP or authenticator app. The IFI desk's recommendation: enable the 2FA via authenticator app (Google Authenticator, Microsoft Authenticator, Authy). The authenticator app is faster (the OTP is generated locally on the device, no SMS roundtrip), more secure (the OTP is not vulnerable to SIM-swap attacks), and works offline (the OTP is generated without a network connection).

The 2FA is enabled in the operator's settings (Settings → Security → Two-Factor Authentication). The setup process is: enter the password, scan the QR code with the authenticator app, enter the OTP from the authenticator app, confirm the 2FA is enabled. The setup takes 2-3 minutes. The IFI desk's recommendation: enable the 2FA on day 1 of the signup, before the first deposit. The 2FA is the primary defense against unauthorized access.

The password recovery: when the password is forgotten

If the password is forgotten, the recovery is via the OTP sent to the mobile number registered with the operator. The player enters the mobile number, the operator sends an OTP, the player enters the OTP, the operator allows the player to set a new password. The recovery takes 1-2 minutes. The IFI desk's recommendation: ensure the mobile number registered with the operator is the current mobile number, not a number that has been changed. A changed mobile number is the most common reason for a failed password recovery.

If the 2FA is enabled and the authenticator app is lost (the device is reset, the app is reinstalled), the recovery is via the operator's customer support. The player contacts customer support, verifies their identity (via PAN, Aadhaar, and bank account details), and the customer support resets the 2FA. The recovery takes 1-3 business days. The IFI desk's recommendation: store the 2FA recovery codes in a secure location (a password manager, a printed copy in a safe) at the time of the 2FA setup. The recovery codes are the fallback for the authenticator app.

The daily-login operational checklist

The IFI desk's daily-login operational checklist is a 30-second ritual that sets the day: (1) open the app, (2) check the captaincy research published on the previous day, (3) check the contest slate for the day, (4) check the withdrawal queue depth if a withdrawal is planned, (5) check the bonus balance if a bonus is being redeemed. The checklist takes 30 seconds and sets the day's operational priorities.

For the player who plays on multiple apps, the checklist is repeated for each app. The multi-app daily login takes 2-3 minutes total. The IFI desk's recommendation: do the daily login at the same time every day (typically 9 am, before the day's work starts) to build the habit. The daily login is the operational foundation of the season.

The login on a shared device

If the player signs in on a shared device (a friend's phone, a hotel business center, a public computer), the IFI desk's rule: log out after the session, do not save the password on the device, do not enable biometric login on the shared device. The shared-device login is a security risk; the player's account can be accessed by the next user of the device. The IFI desk's recommendation: use the personal device for the daily login, and reserve the shared device for the emergency login only.

The operator's "Remember me" option should be unchecked on the shared device. The "Remember me" option stores a session token on the device, which allows the next user of the device to access the player's account without the password. The IFI desk's recommendation: always uncheck "Remember me" on a shared device, and always log out after the session.

The login and the contest timing

The login is the prerequisite for the contest entry, and the contest entry is locked before the toss. The IFI desk's rule: log in 30 minutes before the contest entry deadline, not 5 minutes before. The 30-minute buffer allows for the OTP delivery, the 2FA verification, the team-creation, and the captaincy lock without the time pressure. The 5-minute buffer is a recipe for missed contest entries and operator-flagged late submissions.

For the player who is logging in for the first time on a new device, the IFI desk's recommendation: log in 24 hours before the first contest entry, not 30 minutes. The first-time login on a new device triggers the operator's security checks (the device fingerprint, the IP address, the geo-location), and the security checks can take 5-10 minutes to clear. The 24-hour buffer allows the security checks to clear before the contest entry deadline.

Final word: the login is the operational entry point

The login is the daily operational entry point to the fantasy season. The 30-second daily-login ritual, the strong password, the 2FA via authenticator app, the biometric login, the shared-device caution, and the 30-minute contest buffer are the operational foundation. The IFI desk's editor in chief logs in to all four apps at 9 am every match day during the IPL season. The login is the entry point; the contest is the work; the season is the compounding. Filed fresh from Mumbai, filed for Bharat, filed for the pan-India fantasy community.

The IFI desk's editorial note: filed fresh this week

The IFI editorial desk files this note fresh each week from the Mumbai, Bengaluru, and Kolkata press boxes. The note covers the venue read, the form read, the match-up read, the ownership analysis, and the responsible play reminder. The note is the editorial foundation of the desk's pan-India coverage; the note is the data layer of the pan-India fantasy community's captaincy decision.

For the desi reader who is locked into the contest budget for the week, the note is the closest thing to a personal consultation with the desk's editor in chief. The note includes the captaincy overlay for the 3 most-watched matches of the week, the differential path for the 5 highest-edge plays, the contest allocation for the 4 major apps, and the responsible play reminder for the pan-India fantasy community. The note is the editorial home of the weekly fantasy cricket work.

What the desk's India correspondents are seeing this week

The three India correspondents — based at Wankhede, Chinnaswamy, and Eden Gardens — file 200-word match reports for every contest. The reports cover the venue's bounce, the dew timing, the boundary carrier, the captain's body language at the toss, the outfield's grass cover, the umpire's strike rate. The reports are the data layer of the pan-India fantasy community's venue reads; the reports are the editorial foundation of the IFI desk's coverage.

For the desi reader who watches the match from a Kolkata tea stall, a Bengaluru IT park, a Jaipur paan shop, a Hyderabad biryani joint, a Lucknow kebab corner, or a Delhi metro seat, the reports are the closest thing to being at the ground. The reports are aggregated into the captaincy overlay on the captain picks page; the reports are the editorial home of the pan-India fantasy community.

The desk's responsible play reminder

The IFI desk's editor in chief reminds the pan-India fantasy community of the responsible play framework on every page of the site. The framework requires: 18+ only, KYC mandatory, state eligibility confirmed, self-exclusion tools used when the warning signs are present, no using the contest as a primary income source, no chasing losses, no playing under the influence. The framework is the editorial floor of the pan-India fantasy community; the framework is the data layer of the responsible play understanding; the framework is the application layer of the desk's commitment to the community.

For the desi reader who is reading this page on a phone in a crowded market, in a quiet office, in a college classroom, or on a train, the reminder is the editorial trust layer. The reminder is the foundation of the desk's commitment; the reminder is the application layer of the responsible play understanding; the reminder is the editorial home of the pan-India fantasy community's responsible play.