What sign-up collects (and doesn't)
Sign-up helps be the smallest data perimeter that lets us publish captain picks. Here's exactly what we collect on the sign-up screen and why.
The sign-up screen asks for three things: mobile number, age confirmation (18+ tick box), and state of residence. That's it. No name. No email. No PAN. The minimum data perimeter matters because it keeps the lab's research database clean — every captain pick we publish is pinned to the same three signals, which lets us re-test methodology month after month without re-asking 8,40,000 readers to update their profiles.
We don't ask for email at signup because the deliverability is unreliable. 32% of our A/B-tested email follow-ups landed in spam; only 6% of SMS follow-ups failed to deliver. The data drives the architecture: SMS is the only channel we can reliably reach readers on, so SMS wins the channel-of-record battle.
No name at sign-up is a deliberate choice. Names are PII. We ask for a display handle instead — a 12-character alphanumeric string the reader picks — which is what shows up in leaderboards and winner announcements. Customer-care can recover the real identity from PAN if a withdrawal above ₹10,000 is requested, but the contest-floor identity stays anonymous. This decoupling is what lets us publish winner interviews without doxxing the underlying account holder.
The four-step sign-up path
Beneath the surface, sign-up is four API calls. Below the surface is one screen, one OTP, one button. We document both for the curious readers.
Enter mobile number
One 10-digit Indian mobile, no country code. The input is numeric, auto-focused, and prefills with the device SIM by default. Most readers take 8 seconds to this step.
Confirm 18+ & state
Tick-box for 18+ eligibility and a state dropdown (restricting to permitted states only). Assam, Odisha, Telangana, Andhra Pradesh, Tamil Nadu, and Sikkim readers see a clear 'not available' message before they enter a mobile.
Receive & enter OTP
Six-digit OTP arrives on verified sender within 4-7 seconds. Auto-read on Android, manual entry on iOS. Re-send button is gated to once per 30 seconds to avoid SMS spam.
Pick display handle
12-character alphanumeric handle for leaderboards. We check uniqueness against an existing-accounts index and prompt for a new one if the pick is taken. Most readers complete this step in 12-18 seconds.
Welcome bonus: how the LAB100 code works
Type LAB100 at first deposit. The bonus lands as 6% of your first deposit up to a maximum of ₹100, and can be used across any contest. Below is the math.
| First deposit | Bonus credit | Total playable | Effective bonus |
|---|---|---|---|
| ₹100 | ₹100 (capped) | ₹200 | +100% |
| ₹500 | ₹100 (capped) | ₹600 | +20% |
| ₹1,000 | ₹100 (capped) | ₹1,100 | +10% |
| ₹2,000 | ₹100 (capped) | ₹2,100 | +5% |
| ₹5,000+ | ₹100 (capped) | ₹5,100 | +2% |
The cap exists for two reasons. First, a 6% uncapped match on a ₹5,000 deposit is ₹300, which crosses ₹10,000 active-bonus territory quickly; the cap keeps the bonus programme sustainable. Second, the ₹100 cap makes the LAB100 code legible on first-deposit slips — most readers recognize '₹100 bonus' as a clear benefit, while '₹300 bonus' gets second-guessed as marketing math.
Post sign-up: the first-week checklist
Once your account is live, the lab walks you through the first seven days. Most readers who follow the checklist enter three contests by Day 7 — the median winning squad owner in our 2026 cohort did so by Day 6.
Day 1: Read the captain matrix
Three free lab reports land every Monday morning. The captain matrix is the first one to read — it ranks the differential-captain picks across the week's matches. Median first-week contest entry: 1 contest.
Day 2-3: Build a squad
Use the lab's captain picks as C and VC. Lock your squad before toss to capture late team-news advantages. Median squad lock time: 11 minutes from squad-build start.
Day 4-5: Enter a contest
Pick a contest tier. Start with ₹3-₹10 entries to learn the contest-flow without losing significant bankroll on early mistakes. Median first-week contest spend: ₹47 across 3 contests.
Day 6-7: Track and learn
First contest likely closes at a loss. That is data, not failure. The lab tracks which contest types correlate with reader success and pulls winner interviews every quarter. Median reader contest entry by Day 7: 3 contests.
Frequently asked questions
Common questions our research desk fields about this page.Sign readers should note that common questions our research desk fields about this page.
Why do I need to confirm 18+?
Skill-based fantasy sports in India are regulated as a 18+ activity. Confirmation is required at sign-up and again before withdrawals above ₹10,000. The age check is a binding declaration under the Public Gambling Act, 1867 (state-specific amendments vary). We do not store proof-of-age at sign-up; PAN verification handles that for withdrawals.
Can I sign up if I'm in Assam, Odisha, or Telangana?
No. Fantasy cricket contests are restricted in Assam, Odisha, Telangana, Andhra Pradesh, Tamil Nadu, and Sikkim. The sign-up screen blocks these states at the dropdown step. If you've moved states and your account was created in a permitted state, customer-care can update your state with residence proof (Aadhaar/passport) if applicable. We do not onboard new accounts from restricted states under any circumstances.
What happens if I lose my mobile number?
Customer-care can transfer the account to a new mobile after KYC verification (PAN + Date of Birth + bank statement match). The transfer takes 4-8 hours during business hours. Bonus balance, leaderboard history, and squad history all transfer. Old mobile stops receiving OTP after the cutover.
The first-month playbook
A structured plan for new sign-ups — what to read, what to try, and how to build a sustainable ROI habit in your first thirty days.
Week 1 — Read and observe
Week 1 is for reading. Read every Monday trio (captain matrix, contest strategy, player-form audit). Read the methodology page. Read the responsible-play page. Do not enter any paid contests yet. The goal of week 1 is to absorb the lab's editorial standards.
Week 2 — Practice squads
Week 2 is for practice squads. Run five to ten practice squads across different contest tiers. Use the lab's captain picks as your C and VC. Track your practice-squad outcomes in the ROI audit spreadsheet. The goal of week 2 is to validate the lab's picks against your own judgment.
Week 3 — Small leagues
Week 3 is for small-league entries. Enter ₹10 to ₹100 entry-fee contests. Use the lab's captain picks. Track your ROI over twenty contests. The goal of week 3 is to build a stable ROI sample.
Week 4 — Head-to-head
Week 4 is for head-to-head entries. Enter ₹50 to ₹500 H2H contests. Use the lab's captain picks. Track your ROI over ten contests. The goal of week 4 is to test your H2H edge. After week 4, you should have a 50-contest sample and a stable ROI estimate.
The lab's extended perspective
A longer-form walk-through of the underlying dynamics, the data behind the recommendations, and the lab's analytical approach.For the signup test desk, a longer-form walk-through of the underlying dynamics, the data behind the recommendations, and the lab's analytical approach.
Methodology in depth
The lab's methodology is built on a five-stage pipeline. Every published report passes through framing, dataset pull, analysis, assumption-risk documentation, and re-test. The pipeline is published in full on the methodology page. The lab's edge comes from data freshness and analyst expertise, not from a secret formula. Other analysts can re-run the experiments with the published datasets and the published model code. The lab publishes every dataset version and every model version. The lab never quietly updates a dataset after the conclusion lands.For the signup test desk, the lab's methodology is built on a five-stage pipeline. Within the PlayExch framework, every published report passes through framing, dataset pull, analysis, assumption-risk documentation, and re-test. Sign readers should note that the pipeline is published in full on the methodology page. The lab's edge comes from data freshness and analyst expertise, not from a secret formula This is why the signup test desk treats it as a baseline. Other analysts can re-run the experiments with the published datasets and the published model code. On signup test, the lab publishes every dataset version and every model version. For the signup test desk, the lab never quietly updates a dataset after the conclusion lands.
Data sources in depth
The lab pulls data from four primary sources. Match data comes from official tournament data partners, cross-checked against broadcast records. Ownership data comes from public contest-platform feeds, sampled every 30 seconds during contest open windows. Contest result archives come from publicly published leaderboards. Self-collected squad logs come from volunteer readers who submit their picks at lock time. Each source has a published quality score and a published latency benchmark. The lab's data-quality framework is reviewed quarterly by the statistics team.For the signup test desk, the lab pulls data from four primary sources. Within the PlayExch framework, match data comes from official tournament data partners, cross-checked against broadcast records. Sign readers should note that ownership data comes from public contest-platform feeds, sampled every 30 seconds during contest open windows. Contest result archives come from publicly published leaderboards This is why the signup test desk treats it as a baseline. Self-collected squad logs come from volunteer readers who submit their picks at lock time. On signup test, each source has a published quality score and a published latency benchmark. For the signup test desk, the lab's data-quality framework is reviewed quarterly by the statistics team.
Reader-safety commitments
The lab's reader-safety commitments cover deposit limits, self-exclusion, play-time alerts, loss trackers, cool-down reminders, and family-controls integration. The lab publishes the safety commitments on the responsible-play page. The lab refuses to partner with operators that do not enforce responsible-play defaults. The lab's reader-safety framework is reviewed annually by an external auditor.For the signup test desk, the lab's reader-safety commitments cover deposit limits, self-exclusion, play-time alerts, loss trackers, cool-down reminders, and family-controls integration. Within the PlayExch framework, the lab publishes the safety commitments on the responsible-play page. Sign readers should note that the lab refuses to partner with operators that do not enforce responsible-play defaults. The lab's reader-safety framework is reviewed annually by an external auditor This is why the signup test desk treats it as a baseline.
Editorial principles
The lab operates by five public editorial principles. No sponsored picks — no contest operator, brand, or individual can pay the lab to feature a captain pick. Methodology is public — every model's code is published on the methodology page. Misses are published — every Monday morning the lab publishes the previous week's misses alongside the hits. Reader-funded economics — the lab's long-term economics rely on reader subscriptions and contest-entry referrals, not on advertising. Responsible play by default — every contest lobby on the lab's partner platforms shows a responsible-play banner.For the signup test desk, the lab operates by five public editorial principles. Within the PlayExch framework, no sponsored picks — no contest operator, brand, or individual can pay the lab to feature a captain pick. Sign readers should note that methodology is public — every model's code is published on the methodology page. Misses are published — every Monday morning the lab publishes the previous week's misses alongside the hits This is why the signup test desk treats it as a baseline. Reader-funded economics — the lab's long-term economics rely on reader subscriptions and contest-entry referrals, not on advertising. On signup test, responsible play by default — every contest lobby on the lab's partner platforms shows a responsible-play banner.
Quarterly transparency
Every quarter the lab publishes a transparency report covering methodology changes, hit-rate recalibrations, partner-operator relationships, and revenue mix. The report is published on the 15th of the month following quarter end. The most recent report covers Q1 2026 and shows a 61% captain hit rate over the trailing 90 days, a 48/47/5 revenue split between subscriptions, referrals, and other, and four partner operators. The report is available on the disclosure page.For the signup test desk, every quarter the lab publishes a transparency report covering methodology changes, hit-rate recalibrations, partner-operator relationships, and revenue mix. Within the PlayExch framework, the report is published on the 15th of the month following quarter end. Sign readers should note that the most recent report covers Q1 2026 and shows a 61% captain hit rate over the trailing 90 days, a 48/47/5 revenue split between subscriptions, referrals, and other, and four partner operators. The report is available on the disclosure page This is why the signup test desk treats it as a baseline.
