What the snapshot shows
The public content snapshot used to build this product profile lists three welcome-bonus tiers. Each tier pairs a minimum deposit, a bonus-up-to amount, a Gullak cash amount and one fantasy voucher.
The numbers, taken from the source
Tier one starts at ₹100 minimum deposit and unlocks up to ₹71 bonus and ₹82 Gullak. Tier two starts at ₹500 and unlocks up to ₹251 bonus and ₹252 Gullak. Tier three starts at ₹1,000 and unlocks up to ₹401 bonus and ₹402 Gullak. Every figure above comes from the snapshot row, not from memory.
Why the bonus is bounded
The snapshot phrases each bonus as ‘up to’. The cap is the maximum the publisher credits under this offer; the actual credit depends on the deposit and the conditions in the publisher’s onboarding screen. Treat the rows as maximums, not promises.
What we do not publish on the welcome bonus route
We do not list promo codes. The snapshot does not publish one, and inventing a code would mislead a visitor. Welcome tiers stay bound to the deposit thresholds shown above and become effective in the publisher’s onboarding flow.
Safe checks before tapping Install App
Open the publisher’s rewards page from the install destination, not from this domain. Confirm the offer title and the deposit condition match what you expected. If a code box is left empty, the offer is destination-applied. If a code is requested before you have visited the publisher’s page, stop and use /contact/.
What this article is not
This is not a marketing brief. We have not invented offers, sign-up bonuses, payout cycles or comparisons with other publishers. The aim of the article is to read the staged snapshot exactly as it was published, name what is and is not in it, and let a shortlisting visitor decide what to do next. Where the source is silent, the article is silent.
What we recommend doing next
Open the publisher’s onboarding screen from the install destination at /Login/playnow. Confirm the welcome tier, the VIP thresholds and the refer-and-earn total on the publisher’s own screen. If a number disagrees with what this article shows, the publisher’s screen is the source of record on the day you act. Report the gap through /contact/ so the editorial team can publish a correction in a follow-up piece.
Where the snapshot came from
The values in this article come from a single staged snapshot of the publisher’s public content. The snapshot was captured at a fixed timestamp and we publish a copy of the same payload to the editorial archive. Each value in the table maps directly to a row in the snapshot; we do not interpolate or estimate.
Why the caps are not promises
Bonus caps mark the maximum a tier can credit. The actual credit depends on three things: the deposit you make on the day, your state eligibility under the publisher’s onboarding rules, and any code or affiliate uplift that activates in the publisher’s flow. We do not invent a value for any of those three; we ask you to verify each on the publisher’s screen.
Why we publish row by row
Marketing tables often hide which value is the cap and which is the effective average. We publish row by row so audit-minded visitors can match the cap to the row, the row to the snapshot, and the snapshot to the publisher’s own onboarding text.
What the snapshot does not say
The snapshot does not publish a settlement speed, does not publish a code, does not publish a KYC rule by state, and does not publish the precise moment on which a tier becomes available on a given day. None of those values lives in this article.
How the editorial team will follow up
If the publisher amends the snapshot to add a row, the team will publish a follow-up article. If the publisher removes a row, the team will publish a correction. If the publisher republishes the snapshot with a new bonus number, the team will republish the article with the new number on the same date.
What an audit-minded reader can do next
Open the publisher’s onboarding screen from /Login/playnow. Compare the welcome-tier table on the publisher’s screen with the table in this article. If a number disagrees, the publisher’s screen is the source of record on the day you act. Submit the disagreement through /contact/ and the desk will publish a follow-up correction.
Why we do not rank welcome tiers
Ranking welcome tiers implies a value judgement across publishers and across products. We verify a single publisher’s snapshot; we do not rank. Visitors who want a rank can compare snapshots themselves using the staged archive.
Where this article ends
The article ends with the verify-then-ask loop: open the install destination, confirm the tier and condition on the publisher’s screen, submit any disagreement through /contact/ and watch for the desk’s follow-up. That loop is the only honest way to keep this kind of verification useful for shortlisting visitors.