Snapshot evidence for the brand app shows three published deposit thresholds and the bonus sums that unlock for each. We break down what the data does and does not say.
The staged source explicitly lists 15 VIP ranks, daily guaranteed amounts and the cashback matrix per family. Here is what is verifiable from the snapshot.
The same snapshot carries two reward values. We explain how we treat that conflict in the published facts.
How the news desk works
Every article on this product profile is built from the staged sponsor public data snapshot. Numbers come straight from the published CSV or JSON rows. Where the snapshot does not publish a value, the article says so in plain language rather than guessing. Each article opens with the verified event, names the source row it relies on, and ends with a concrete next step a shortlisting visitor can act on.
How an article is updated
The desk re-pulls the snapshot on a fixed cadence. When the publisher changes a number, an article is updated with the new value and the change is reflected in the date at the top of the article. When a number is dropped from the snapshot, the article transitions to ‘Not published’ rather than showing a stale figure.
What the desk will not do
The desk will not invent offers, will not borrow wording from a third-party publisher’s headline, will not use loaded language to make a small change sound like a big one, and will not borrow a quotation from a social post that cannot be independently sourced. Every claim in an article is linked to a row in the staged snapshot.
Editorial coverage areas
The current seed coverage is three articles: welcome bonus tiers and the IN Rdifference between cap and effective value, the fifteen-rank VIP matrix and the auto-enrolment threshold, and the source conflict between two refer-and-earn totals published by the same snapshot. Future coverage will follow the same structure.
Submit a correction
If you spot a number that disagrees with the publisher’s onboarding screen, send a short message through /contact/. Include the article URL, the number and the source you have verified. The desk will publish a follow-up piece if the discrepancy stands.
Install Yono Games appDirect route. Sponsored affiliation.
The editorial desk re-pulls the snapshot on a fixed cadence. When the publisher changes a row, the article is updated and the date stamp moves.
On consistency
The desk does not contradict itself between articles. The welcome tiers, VIP matrix and refer-and-earn totals are the same numbers across articles; only the framing changes.
On submitting corrections
Send a correction through /contact/ with the article URL, the disputed number and the source you have verified. The desk reviews and publishes a follow-up if the discrepancy stands.
On what the desk will not do
The desk will not publish promotional superlatives, will not borrow quotes from social posts that cannot be independently sourced, and will not treat a small change as a big one.
A short visitor’s reading order
Read the three cards at the top of this route in any order. Each one is a self-contained snapshot-backed piece. After reading, open the relevant editorial coverage section below to see what the desk will not do and how to submit a correction.
What an audit-minded reader will look for here
Each card carries a date stamp, a headline and a standfirst. The headline states the verified event. The standfirst tells you what source row the article relies on. After the cards, the route explains the editorial discipline and the correction loop.
How a story reaches the desk
A story reaches the desk when a value in the staged snapshot changes, when the publisher retracts or adds a feature, or when a verification-friendly source surfaces a discrepancy. The desk then plans an article based on the snapshot row, drafts the headline, standfirst and outline, and publishes once the verification is complete.
Why the desk publishes corrections
Corrections are part of the discipline. A snapshot-backed editorial product earns its keep by telling readers which numbers are still right. The desk will publish a correction for any discrepancy a reader submits through /contact/ that the publisher’s onboarding screen confirms.
Why the desk publishes follow-ups
Follow-ups extend the original article rather than replace it. A follow-up carries a new date stamp and links to the original. Readers can compare both and decide which row to trust on the day they act.
A working visitor’s reading order
Open the card that matches your decision stage today. If you are about to claim a welcome bonus, read /news/welcome-bonus-2026-inr-tiers/. If you are about to be auto-enrolled in VIP, read /news/vip-15-levels-and-auto-enrol/. If you are about to refer a friend, read /news/refer-and-earn-source-conflict/.
Why this news hub exists
Verification products are only useful if they keep up with the source. The desk re-pulls the staged snapshot on a fixed cadence and publishes follow-up articles whenever a row changes. The hub is the public view of that work; it is not a news feed in the breaking-news sense.
Editorial archive and audit trail
Each card on this route links to an article that corresponds row-by-row to a row in the staged snapshot. The archive retains the snapshot so an audit-minded reader can match an article to its source. The hub never publishes anything not in the snapshot.
What we mean by ‘snapshot-backed’
Snapshot-backed means the article relies only on values the staged snapshot publishes. We do not borrow values from a third-party listing, a social post or an advert. When the snapshot is silent, the article is silent. That is the entire discipline.
What happens when the source changes
Articles are revised when the snapshot changes. Old date stamps stay visible so a reader can see which version was published when. Corrections are republished; they are not silently edited.
Beyond this article
Open /faq/ for the most common questions across installs, account, safety and support. Open /responsible-use/ for the principles that apply across studios and products.
A working visitor’s reading path
If you read three pieces, read the welcome bonus article first, because the table format is easier to compare at a glance. If you read two, read the VIP article second, because auto-enrolment affects what you can expect on the publisher’s first loyalty screen. If you read one, read whichever matches your immediate decision stage today.
Why corrections use follow-ups
Corrections are republished rather than silently edited. A silent edit would not show the reader that the article has changed. A follow-up carries a new date stamp so a reader can see when the article was last revised.
What happens to old articles
Articles are not deleted when they are revised. The editorial archive retains the prior version so a reader can match an old date stamp to a snapshot at that point in time. We do this so an audit-minded reader can defend a decision they made based on an old article.
How a reader follows the desk
A reader who wishes to follow the desk can subscribe to the RSS feed at /feed.xml or open a single article a week. The desk does not recommend opening the full archive on every visit. Read what matches your decision stage, then act on what the snapshot says.
Why the desk does not publish opinions
The desk publishes verification, not opinion. Where the desk has an opinion, it is labelled as such and tied to a verifiable source. Opinion without source is not published; verification without opinion is the editorial norm.
What the desk looks for in a story
A story reaches the desk when a value in the staged snapshot changes, when a new verification-friendly source surfaces a discrepancy, or when a reader submits a correction through /contact/. The desk re-pulls the snapshot on a fixed cadence and plans any follow-up article from a snapshot row.
Cookie preferences
Strictly necessary cookies keep core site features working. Optional analytics and marketing cookies are off by default. You can withdraw consent as easily as you give it.
