Brand SERP · OperatorWho owns Zupee is a question the desk answers from public filings, not from marketing copy. The operator behind Zupee is named in Ministry of Corporate Affairs filings and is publicly identifiable. This page walks through the parent entity, the regulatory frame, and what the desk asks readers to verify themselves.
Zupee is operated by a private limited company incorporated in India. The corporate identity is verifiable through the MCA portal. The operator name is published on the operator product and on the official-website.
Name. The parent entity is named on the operator product T&C page.
CIN. The corporate identification number is on the MCA portal.
Registered address. Public on the MCA portal and in annual filings.
The MCA portal at mca.gov.in hosts the operator filings. Any reader can verify the corporate identity in a few minutes. The desk reads the latest annual return and the director list before publishing this page.
Zupee runs as a real-money skill gaming product. The regulatory frame is state-by-state. The state eligibility page walks through which states permit the product.
In every state, the operator defence rests on the skill-versus-chance distinction. The operator formats are designed around player judgement, not a house edge.
The operator owns the brand and the product. It does not own cricket, kabaddi, or any sport whose contests it surfaces. Contest fixtures are public sporting events, and the operator cannot and does not claim ownership of the underlying sport.
The brand surfaces across the operator product, the marketing channels, and a small set of help and corporate pages on the web. The operator also licenses brand usage to affiliate partners under specific terms.
1. Visit the MCA portal and confirm the operator corporate identity.
2. Visit the official-website and confirm the domain matches the operator published domain.
3. Read the terms and the privacy policy on the operator product, not on a third-party mirror.
Zupee के पीछे एक publicly filed Indian company है। MCA portal पर corporate identity verify की जा सकती है। Operator skill gaming frame में operate करता है और state rules के अनुसार product उपलब्ध कराता है।
Three habits the desk has internalised. First, treat the operator main site as the source of truth on the day you read. Second, treat the MCA master data as the verification source for registered office and director detail. Third, treat the press coverage as a secondary cross-reference, not a primary source.
Two things the desk treats as anchor facts. First, Zupee is operated by Zupee Games, an India-headquartered real-money skill-gaming company; this is verifiable on the operator main site. Second, the operator publicly lists identity information on its main site.
Three recurring ones. First, "is Zupee Indian?" Yes. Second, "is Zupee a public company?" No, Zupee is a private company. Third, "does Zupee pay tax on winnings?" Yes; TDS applies above the prevailing threshold.
Two checks. First, the operator main site lists its company disclosure. Cross-reference against the MCA master data for any registered office or director detail. Second, the operator published help section for the verifiable touchpoints.
For the trust review, see the review page. For the customer-care routes, see the customer care page. For the official domain verification, see the official website guide. For the verification habit, see the verification desk.
Three categories the operator typically publishes on its main site. First, company identity. Second, contact routes. Third, app-store and help URLs. The desk cross-references each; the operator published list is the source of truth on the day.
Three gaps. First, current ownership percentages if the company is private. Second, payout timing profile. Third, future product launches. The desk treats these as marketing signals, not verification material.
Two checks. First, the operator main site lists its company disclosure. Cross-reference against the published MCA master data for any registered office or director detail. Second, the operator published help section for the verifiable touchpoints.
Two recurring ones. First, "is Zupee a public company?" No, Zupee is a private real-money skill-gaming company. The desk does not publish a market-cap figure because there is no market cap to publish. Second, "does Zupee pay tax on winnings?" Yes. TDS applies above the prevailing threshold.
For the trust review, see the review page. For the customer-care routes, see the customer care page. For the official domain verification, see the official website guide. For the verification habit, see the verification desk.
Three habits the desk has internalised for the operator profile. First, treat the operator main site as the source of truth. Second, treat the MCA master data as the verification source for registered office and director detail. Third, treat the press coverage as a secondary cross-reference.
Two things the desk treats as anchor facts. First, Zupee is operated by Zupee Games. Second, the operator publicly lists identity information on its main site.
For the trust review, see the review page. For the verification habit, see the verification desk.
A private limited company incorporated in India. Verifiable on the MCA portal.
No. The operator is a privately held private limited company.
The operator runs as a skill gaming product under state-by-state rules.
India. The registered address is on the MCA portal.
No. Cricket fixtures are public sporting events.
Verify the corporate identity, the domain, and the published terms yourself.
Use the in-app Help & support entry or the email listed on the operator product.
The operator publishes a registered-company dossier on the help-centre footer. The dossier lists the legal entity name, the CIN, the registered office, the founders' names, and the operator's regulatory counsel. The desk cross-checks the dossier against the MCA registry, the GSTN registry, and the SEBI intermediary list. The cross-check is the desk's primary verification, and the cross-check is reproducible on a laptop. The MCA registry is the canonical source for the legal entity and the CIN. The GSTN registry is the canonical source for the state-by-state GST registration. The SEBI list is the canonical source for the skill-format eligibility.
The reader's habit is to open the three registries in three tabs and reconcile the operator's dossier against the registry data. The reconciliation is the difference between trusting the operator's marketing page and trusting the registry's published record. The facts page documents the desk's verification method.
The operator's published posture is a dual-format, regional, skill-based real-money-gaming platform. The dual-format part covers fantasy cricket and Ludo tournaments. The regional part covers the state-by-state eligibility list. The skill-based part covers the format-by-format skill-vs-chance split. The posture is the reason the operator publishes the points system, the Ludo tournament rules, and the responsible-play surface. The fantasy cricket guide and the Ludo tournaments guide cover the format-specific levellers.
The operating posture is the reason the operator's eligibility list is published in two columns rather than one. The skill-format column governs the formats the operator publishes as skill-based. The chance-format column governs the formats the operator publishes as chance-based. The reader's habit is to read both columns before the first deposit, and to confirm the format the reader intends to play is in the skill column of the reader's state. The is-legal page lists the state-by-state column.
The desk does not publish the operator's internal compliance memo. The desk does not publish the operator's internal KYC vendor list. The desk does not publish the operator's internal payout-rail SLA. The reasons are the operator's privacy and the desk's verification method. The desk's habit is to publish the verifiable data points and to publish the desk's verification method, and to let the reader re-run the desk's verification on the reader's own. The facts page documents the verification method.
The dossier is refreshed on a six-week cycle. The refresh is timed to the bonus-cycle refresh and the eligibility-list refresh. The reader's habit is to check the verification date on the dossier before the reader's first deposit, and to re-check the dossier before the reader's next deposit cycle. The review page documents the cross-check against the operator's published terms.
The terms page documents the operator's published terms, and the privacy page documents the operator's data-handling. The comparison page applies the operator dossier to the alternative operators.
