The login flow on a regulated Indian skill-game platform has four steps: enter the registered mobile or email, complete the password or OTP step, complete two-factor authentication and confirm the KYC status. Each step exists for a reason. The page walks each step and lists six security habits that protect the account from credential theft.
Enter the mobile number or email address used at sign-up. The platform matches the credential against the on-file record. A credential that does not match is rejected at the boundary, not at the password stage. This separation protects the platform against credential-stuffing attacks, where an attacker tries a leaked email-password pair against the platform.
Passwords should be at least eight characters, with at least one uppercase letter, one number and one symbol. One-time passwords are sent to the registered mobile and expire in five minutes. A one-time password should never be shared with anyone, including the platform's support team. Support will never ask for an OTP; if anyone asks, treat it as a scam.
Two-factor authentication adds a second factor (a code from an authenticator app, a hardware token or a one-time password to a different device). Enable it on every skill-game account that supports it. The second factor is the strongest defence against credential theft, because the attacker needs both the password and the second factor to gain access.
After login, the platform confirms KYC status. A complete KYC allows deposit and play. An incomplete KYC allows login and account inspection but blocks deposit and play. A pending KYC blocks withdrawal until the verification is complete. The status confirmation is the moment when the platform tells you what you can do next.
Confirm the credential with the platform's password reset flow. The reset email is sent only to the registered address; if the address has changed, contact support with the registered email and a recent transaction reference.
Check whether the registered mobile can receive SMS. Some mobile carriers throttle or block transactional SMS during certain hours. If the OTP does not arrive after three minutes, request a new code. The previous code expires automatically.
Most platforms lock the account after five failed attempts within fifteen minutes. The lock releases automatically after thirty minutes. A persistent lock requires contact with the platform's support email and a recent transaction reference.
If the authenticator app is reinstalled on a new device, the platform's recovery codes are the only path back. Save the recovery codes at two-factor setup. Without them, account recovery requires manual identity verification with the platform.
The reference on this page is organised so a reader can scan the headline and decide whether to read the section. Use it as a working document: bookmark the sections you need to revisit, treat the platform's own pages as the primary source and treat this desk as a structured way to navigate that source.
Every factual claim about licences, security, payments or responsible-play controls on this page is sourced to a public source: a platform's own published page, a regulator's register, a state gaming notice or a parliamentary bulletin. The reader can verify any claim against the named source.
This desk does not publish payout rates per format, sign-up bonuses, daily-login rewards, customer-care phone numbers, app-store ratings or ownership data not published on the platform itself. Where a number is required, the page points to the platform's own page where the number is published.
Editorial pages are revised at least quarterly to reflect regulatory changes. The last-revision date appears in the dateline at the top of the page. If the reader spots a factual error or a regulatory change the desk has missed, the contact page lists the editorial email.
The boundary exists because the desk is read-first. It does not accept wagers, run tables or hold player balances. It does not advertise bonus offers. It does not fabricate customer-care phone numbers or ownership claims. The boundary is the reason the desk can serve as a working reference rather than as a marketing channel.
Where this page references a platform, the desk uses the platform's published company name. Where the company name and the brand name differ, the desk names both. Where a brand token overlaps between skill-game and live-game products, the desk distinguishes them in the body copy rather than treating them as the same product.
Where a fact cannot be verified at the time of writing, the desk marks the cell as verification-needed. The reader is responsible for the final verification on the platform's own page or the relevant regulator's register. The desk does not omit a fact silently; it marks the gap and explains what to verify.
The desk reads editorial corrections, regulatory clarifications and platform updates by email. The desk does not respond to commercial enquiries, partnership pitches or SEO solicitations. The contact page lists the editorial email and the response window.
A publication format (masthead, dateline, byline, lede, body, sidebar, colophon) is the most familiar reading structure for an adult reader. It signals that the content is reviewed, dated and revised, not generated automatically. The format is a way of saying that the content has been thought about.
The rules ledger, the safety explainer and the responsible-play framework.
