News
PROG Act 2025 framework: what changed, why it matters and what to verify
The Ministry of Electronics and Information Technology's online real-money games framework is in force as of 2025. The post is a reader-facing summary of the public framework: what changed, what stayed the same, and which state-level questions remain open.
The framework sets the central rules for online real-money games in India, including rummy. Three requirements are the most relevant for the reader: a verification mechanism, a grievance officer, and a published responsible-gaming policy. State rules layer on top of the central framework.
What changed
The framework introduces a verification mechanism that platforms must apply before a real-money deposit is allowed. The mechanism is a KYC ladder, not a one-step check: the platform verifies a phone number, an email address, an identity document and a payment instrument before the deposit limit takes effect. The framework also requires a named grievance officer whose contact is published on the platform's site, and a published responsible-gaming policy that includes a self-exclusion pathway.
What stayed the same
Indian High Court rulings have held that 13-card rummy is predominantly a game of skill. The skill-game classification still matters for state-level rules on real-money stakes. The framework does not change the underlying skill-vs-chance classification; the framework changes the operational rules around real-money play.
Why it matters
For the reader, the framework means three practical changes at the platform level:
- Verification happens before the first real-money deposit, not at withdrawal time. The reader may be asked for a PAN copy at the first deposit.
- A grievance officer is named on the platform's site. The reader can address a written complaint to the grievance officer if the in-app support channel is not responsive.
- A self-exclusion pathway is published. The reader can enable a self-exclusion without contacting customer support.
What to verify
- The MeitY press release and the published framework document. The post is a summary; the source is the published framework.
- The current state-level rules for the state the reader is reading from. The /is-legal/ page summarises the public rules the desk has been able to verify.
- Whether the platform's published grievance officer and responsible-gaming policy are reachable. A published policy that is not reachable from the platform's footer is a red flag.
What the desk does not do
The desk summarises the public framework; the desk does not endorse any platform and does not rank operators. Where the framework requires a reader action, the post names the action; the desk does not help the reader complete the action.
PROG Act 2025: questions readers ask
Where is the source for the claim above?
Every claim on this site traces to a public source. The URL is in the same paragraph as the claim, or in the verification table at the top of the page. Where a source cannot be linked, the column says "verify before acting" rather than paraphrasing the source.
How does Spin avoid invented numbers?
The editorial standards document sets the rule: any number on the site traces to a public source in the same sentence, with a sample and a date. Where a number cannot be sourced, the column is omitted. The desk does not publish estimated or round-number figures without a source.
What is the next step after reading the PROG Act post?
Read the linked "next step" at the bottom of the page. The link is the desk's recommendation for the page the reader should read next; the link is internal and points to a canonical URL on spinappin.com. The desk does not link to external pages for next-step recommendations.
How can a reader correct an error on the page?
Send the URL and the paragraph number to the contact page. The desk reads reader mail within five working days; corrections are issued under the same byline on the same URL with a date stamp.
Is the page part of the news sitemap?
The news sitemap covers dated news posts only. the PROG Act post is a prog act 2025 page; it is on the main sitemap but not on the news sitemap. The main sitemap includes every canonical URL; the news sitemap is a subset.
Does the page use any tracking pixel or third-party script?
No. The site uses a single bundled stylesheet and a single small JavaScript file for the masthead hamburger and the chapter tabs. No analytics, no chat widget, no third-party tracking. The privacy notice names what is collected (HTTP request metadata) and what is not (personal data, document images, payment details).
What is the difference between the article and the canonical URL on the main sitemap?
There is no separate canonical URL; the page is itself the canonical. The main sitemap entry uses the trailing-slash form; the page is reachable from the same URL with or without a trailing slash. The canonical tag in the page head points to the trailing-slash form.
Where is the editorial colophon?
The editorial colophon is on the about page, the editorial standards page and the homepage. The colophon names the publisher, the editorial principles and the corrections process. The colophon is the audit trail; the page above is the editorial content.
What is the verification date on the page?
The "Last verified" date is in the page-head meta box on the page. The date is the audit trail for the page's content; the date is updated quarterly or sooner if a verifiable change is published.
What is the easiest way to send feedback to the desk?
The contact page lists the email address the desk reads. The desk replies within five working days. Reader feedback is read with discretion; the desk does not publish reader correspondence.
What to read next, and what to verify before acting
The desk's editorial scope is rules, formats, strategy boundaries, platform usability, payment and KYC, and responsible play. Each page in the editorial scope is a piece of the same picture; the picture is the reader's relationship with the game. The right next step is the page that fills the next gap in the picture; the wrong next step is the page the reader is comfortable with.
If you are new to the rules
Read the rules walkthrough at /how-to-play/. The walkthrough is a step-by-step guide to dealing, turn order, melds, joker rules, declaration and scoring, with a worked 13-card hand. The walkthrough is the place to start; the format comparison at /games/ is the place to go once the walkthrough is comfortable.
Before the first paid hand, verify the platform's T&Cs page and the responsible-gaming menu. The desk does not endorse any platform; the desk names the surfaces a reader should check before staking. The /safety/ page covers the KYC surfaces; the /responsible-play/ page covers the in-product controls.
If you already know the rules
Read the strategy guide at /strategy/. The guide is an honest strategy boundary statement: what a skilled player can shift, what stays variance, and the three decisions that move expected value most. The guide is the place to think about the decisions; the rules walkthrough is the place to think about the mechanics.
Once the strategy guide is comfortable, the format comparison at /games/ is the place to decide whether to try Pool 101, Pool 201 or Deals. The comparison is the place to read the format-by-format deltas in drop math, ceiling pressure and end-of-hand shape. The comparison is also the place to think about session length.
If you are choosing a platform
Read the platform reviews at /reviews/. The reviews page is the methodology, the verdict numerals, the platform grid and the "what we deliberately do not test" section. The reviews page is the place to read the criteria a reader should run on the first session; the /safety/ page is the place to read the KYC and withdrawal surfaces.
Before the first deposit, run the first-session check from the reviews page. The check has five items: where the responsible-gaming menu is, where the deposit limit is, what the practice-mode entry is, what the T&Cs page URL is, and what the withdrawal queue's expected time is. A platform that passes the five items is in a usable position for a small deposit; a platform that fails any item is a yellow flag.
If you are managing KYC or a withdrawal
Read the payments and KYC explainer at /safety/. The explainer covers the documents platforms typically ask for, what masking means, when UPI chargebacks work, and what to do when an operator holds funds. The explainer is the place to read the KYC surfaces; the /wallet-kyc/ page is the place to read the verification ladder in detail.
For a withdrawal that is held beyond the platform's T&Cs timeline, the escalation path is: in-app support ticket, written dispute to the platform's published dispute email, regulator or ADR named in the T&Cs. Throughout the escalation, do not add new funds to the platform. The escalation depends on what is already in custody.
If you are reading the newsroom
The newsroom at /news/ covers rule changes and platform updates, sourced when verifiable, silent when not. The newsroom does not publish payout numbers, does not name winners, and does not run operator announcements as news. Each post carries a verification date and a "what to verify" line so the reader can check the source.
The newsroom's editorial rules are documented in the /editorial-standards/ page. The rules are: source the change, distinguish rule change from marketing, and tell the reader what to verify. The rules are the audit trail for what reaches the newsroom; the absence of a post is itself a result.
If you need a single sentence
Read the rules first; play within your means. The rules are the basis for the format, the strategy, the platform review and the responsible-play reminder. The means are the session cap, the stake cap and the responsible-gaming menu. The two sentences together are the editorial scope of the site.