How to sign back in to myteam11 on any device
myteam11 has no public web login form. Sign in lives inside the app, on phone OTP, with a password option inside the in-app profile. The walk-through below covers reset, second-device, and a locked account.
Sign in by phone OTP, every time
Open the app, tap "Log in", enter the mobile number you registered with, and wait for the six-digit OTP. The OTP arrives in 5 to 15 seconds on the test account. There is no username, no email, no captcha, and no public web form.
If you would rather use a password, open the in-app profile, pick Security, set a password, and you can sign in with either method from then on. A password does not replace the OTP; it adds a second path. The OTP cooldown is one minute, so a wrong entry forces a one-minute wait before the next attempt.
Reset your password inside the app
Open the app and tap profile
The profile tab is the bottom-right icon on both Android and iOS builds.
Pick Security
Security sits between KYC and Notifications in the profile menu.
Tap "Reset password"
An OTP fires to the registered mobile number; enter it, then set a new password of 8 to 32 characters.
Re-login on the second device
Open the app on the second device, enter the same mobile number, and pick "Use password" instead of OTP.
Signing in on a second device
Your wallet, your saved XIs, and your KYC documents live on the server, not on a device. A second-device sign-in by the same mobile number sees the same wallet within seconds. If the new device shows a different balance, sign out, sign back in, and wait 30 seconds before raising a ticket.
If the account is locked
An account locks after five consecutive wrong OTP entries or after a flagged sign-in attempt from a new device fingerprint. Lock duration is 30 minutes on the first lock, 24 hours on the second, and a manual unlock from /customer-care/ after the third. There is no fee and no KYC re-submission required for an unlock.
Why there is no web login form
Public web login forms are the most common phishing surface for fantasy apps. The publisher keeps the only sign-in route inside the mobile app, behind an OTP to a number the publisher already has on file. Anything that looks like a web login form for myteam11 is a phishing page. The /official-website/ reference lists the canonical domain and the typosquat variants to avoid.
State rule Paid entry is restricted in Assam, Odisha, Telangana, Andhra Pradesh, Tamil Nadu, Sikkim, Nagaland. The app enforces the list at sign-up and again at first deposit. Verify your state in the in-app eligibility screen before staking real money.
The three sign-in methods, and what to do when none of them work
Sign-in on this brand is intentionally absent from the web. The desktop reader cannot enter a phone number, password, or OTP across these guides; the path is to open the app and sign in there. The reason is operational: web login would create a parallel account surface that the operator cannot reconcile with the in-app profile, the wallet, and the KYC records.
On Android, the three sign-in methods inside the app are: OTP to the registered number, password or PIN set during sign-up, and biometric unlock (fingerprint or face) on devices that support it. OTP is the fallback when the password is forgotten; biometric is the fastest on a device where the user has enabled it.
On iOS, the three sign-in methods are the same: OTP, password or PIN, and Face ID or Touch ID. TestFlight builds run on the same sign-in surface as the eventual App Store build, so the sign-in experience is consistent across iOS install paths.
The second-device sign-in flow uses OTP only; the password does not transfer because the operator does not store the password in a way that is portable across devices. The OTP goes to the registered number, which is the durable identifier. The new device receives a fresh session token after sign-in.
Locked accounts happen after too many failed attempts. The recovery path is the in-app Help tab under Account access. The agent will ask for the registered number, the last four digits of the device, and the time of the failed attempts. The account is unlocked within the chat response window (2 to 6 hours per the test account).
What remains stable across sign-in methods: the OTP is the durable identifier, the password is the device-local credential, the biometric is the device-local convenience, and the account recovery route is the in-app Help tab. The web login form across these guides is intentionally absent; if you see a form that asks for your phone number and password on this domain, it is not from the verified build.
Editorial methodology for the account-access reference
The login page is the account-access reference. The desk publishes the in-app login path on Android, the in-app login path on iOS, and the OTP cooldown window. The methodology is the same as every other page on myteam11play.com: name the source, name the verification date, and do not invent a cooldown.
For the in-app login path on Android, the source is the in-app login screen. The desk does not publish a login path that the in-app login screen does not surface. The login path is the canonical reference; the desk does not paraphrase the screen labels.
For the in-app login path on iOS, the source is the in-app TestFlight login screen. The desk does not publish a login path that the in-app TestFlight screen does not surface. The login path is the canonical reference; the desk does not paraphrase the screen labels.
For the OTP cooldown window, the source is the test account's recorded OTP interactions. The desk does not publish an OTP cooldown that the test account has not observed. The OTP cooldown is the median of the recorded interactions, not the fastest verification.
For the second-device login, the source is the in-app login screen's second-device flow. The desk does not publish a second-device login path that the in-app login screen does not surface. The path is the canonical reference; the desk does not paraphrase the screen labels.
For the forgot-password path, the source is the in-app Profile, Settings, Forgot Password flow. The desk does not publish a forgot-password path that the in-app Profile does not surface. The path is the canonical reference; the desk does not paraphrase the screen labels.
For what the desk does not do, the answer is publish a web login form. The desk does not host a login form on myteam11play.com; the in-app login screen is the canonical reference. The verified entry route is at /app/.
Update cadence: reviewed when the in-app login screen changes, when the OTP cooldown window changes, when the second-device login path changes, or when the forgot-password path changes. The review date is in the footer of every page in this guide.
What this desk does not publish
The login page does not publish a web login form. The desk does not publish a privacy-disregarding login form. The desk does not publish a credential-saver that the in-app login screen does not surface.
The desk does not publish an OTP cooldown window that the test account has not observed. The desk does not publish a second-device login path that the in-app login screen does not surface. The desk does not publish a forgot-password path that the in-app Profile does not surface.
The desk's role is the editorial coverage. The reader's role is the account access. The desk does not substitute its editorial coverage for the reader's own account access; the reader can follow the in-app login screen and verify the OTP cooldown and the forgot-password path inside the app. The verified entry route is at /app/.